VisualBoyAdvance-M

Via the wireless reciever? Never.

There was a file, many years ago, who claimed to be a beta driver called "XBCD Plus" for the X360 Wireless Controller.

As I said it was beta and for Vista, probably 32bit only.

Used to be hosted at the following address but of course the page is down now.

http://xbcdplus.truth.aonservers.com/down.html

Dunno if it was fake or not, never tried it since back then I didn't have a wireless controller.

Found the link on an old guide of a national forum I used long time ago, first post hasn't been updated yet so the link is still there lol

 

You also haven't replied me on why it's currently not possible to develop XBCD for X360 wireless controllers.

I mean, not that you "have" to reply to me lol, I'm just kindly asking if you could please do so, I'm curious to understand why is it so complicated.

Sorry if I sounded arrogant or demanding, as if it was probably more than clear enough, english is not my main language [img]<fileStore.core_Emoticons>/emoticons/smile.png[/img]/emoticons/smile@2x.png 2x" width="20" height="20" />

 

 

the x360ce dev, or atleast the guy who is continuing it anyway, is going to do a dinput to xinput wrapper some time in the future, might be what you need.

I'm ignorant with this stuff. Means he's gonna make a thing that converts Xinput into Dinput? Basically the opposite of what x360CE does now.

Is there a community anywhere concerning x360ce? I only found their google page which is not exactely particularly efficient to follow discussions on issues and other topics.

 

 

is that stick calibrated in devices and printers?

As I said in my previous post, in the "Devices and printers" menu I normally see 2 different peripherals: the wireless receiver and the wireless controller.

Tried to install Morii's wireless drivers many times on the controller, but no luck.

When I tried to install them on the Wireless Receiver, it instantly worked but when you do that it's like the receiver itself gets, sorta, recognized as the pad, and the Pad disappears from the list in "Devices and printers".

From the internal menu of the drivers everything seems to be working correctly, from the FFXI pad customization menu instead I finally see triggers as digital buttons 11 and 12, but the Xrotation/Yrotation doesn't work anymore for some reason.

 

It's strange because with the wired controller drivers from Morii (on my old PC) everything works perfectly.

 

Guess I'll try again later when I get back home, but it sounds like I'll have to just use the basic drivers and avoid using the triggers, sigh

You also haven't replied me on why it's currently not possible to develop XBCD for X360 wireless controllers.
I mean, not that you "have" to reply to me lol, I'm just kindly asking if you could please do so, I'm curious to understand why is it so complicated.

 

Well, part of it rests on my not being a hid/common class developer, so i don't understand the interface to make the drivers use it, its also not so easy to adapt the current driver code to use on wireless controls.

 

I'm ignorant with this stuff. Means he's gonna make a thing that converts Xinput into Dinput? Basically the opposite of what x360CE does now.

 

basically yeah.

I see. Thanks again Leon for your patience and pardon me if I sounded ungrateful/arrogant [img]<fileStore.core_Emoticons>/emoticons/smile.png[/img]/emoticons/smile@2x.png 2x" width="20" height="20" />

I can't get XBCD to work with x360ce. The image is faded out:

 

http://img163.imageshack.us/img163/7800/unavngivetww.png

 

What am i doing wrong? It see it as a joypad in win7 [img]<fileStore.core_Emoticons>/emoticons/sad.png[/img]/emoticons/sad@2x.png 2x" width="20" height="20" />

Please help?

Xinput Emulation
XBCD also now contains an Xinput emulator which there are 2 profiles available for use on the internet database.

Set XBCD to the Triggers on seperate axis profile or XBCD 360 emu profile in the XBCD Setup app and then start up the x360ce app.

 

On the Settings database tab, click refresh, then look for profiles with the following hash's

For Xbox Controllers, look for 41FF4C76 (This profile was created on an Xbox S Type, so will be named as such)

For Xbox 360 Controllers, look for 2F8C1B2D (This profile was created on a MadCats MLG Pro Circuit, so will be named as such)

<blockquote data-ipsquote="" class="ipsQuote" data-ipsquote-contentapp="forums" data-ipsquote-contenttype="forums" data-ipsquote-contentid="657" data-ipsquote-contentclass="forums_Topic"><div>Xinput Emulation
XBCD also now contains an Xinput emulator which there are 2 profiles available for use on the internet database.

Set XBCD to the Triggers on seperate axis profile or XBCD 360 emu profile in the XBCD Setup app and then start up the x360ce app.

 

On the Settings database tab, click refresh, then look for profiles with the following hash's

For Xbox Controllers, look for 41FF4C76 (This profile was created on an Xbox S Type, so will be named as such)

For Xbox 360 Controllers, look for 2F8C1B2D (This profile was created on a MadCats MLG Pro Circuit, so will be named as such)

</div></blockquote>
 

Thanks for the quick reply :)

Like this:

http://img163.imageshack.us/img163/6844/unavngivet02.png

(Last profil is is made by me)

Can't see the hash key to be correct?

 

Help much appreciated, so thanks again :)

Just received a new HORI ex2 turbo in the mail from amazon. With a base ID of USB\VID_24C6&PID_5500

Can confirm working properly by just replacing the ID in the inf of the HORI with this ID.

not rumble enabled, obviously.

<blockquote data-ipsquote="" class="ipsQuote" data-ipsquote-contentapp="forums" data-ipsquote-contenttype="forums" data-ipsquote-contentid="657" data-ipsquote-contentclass="forums_Topic"><div>

<blockquote data-ipsquote="" class="ipsQuote" data-ipsquote-contentapp="forums" data-ipsquote-contenttype="forums" data-ipsquote-contentid="657" data-ipsquote-contentclass="forums_Topic"><div>Xinput Emulation
XBCD also now contains an Xinput emulator which there are 2 profiles available for use on the internet database.

Set XBCD to the Triggers on seperate axis profile or XBCD 360 emu profile in the XBCD Setup app and then start up the x360ce app.

 

On the Settings database tab, click refresh, then look for profiles with the following hash's

For Xbox Controllers, look for 41FF4C76 (This profile was created on an Xbox S Type, so will be named as such)

For Xbox 360 Controllers, look for 2F8C1B2D (This profile was created on a MadCats MLG Pro Circuit, so will be named as such)

</div></blockquote>
 

Thanks for the quick reply :)

Like this:

http://img163.imageshack.us/img163/6844/unavngivet02.png

(Last profil is is made by me)

Can't see the hash key to be correct?

 

Help much appreciated, so thanks again :)

</div></blockquote>
 

ah, i was afraid that would be the case

 

the application uses the device name to pull valid profiles, so a profile created for the MLG will not appear for the other madcats controls, and 360 type pads seem to override the device name in the registry.

 

i'll create a new thread with setups that work on these pads.

Thank you, that would be nice [img]<fileStore.core_Emoticons>/emoticons/smile.png[/img]/emoticons/smile@2x.png 2x" width="20" height="20" />

 

Would you link to it when the thread is up and running?