VisualBoyAdvance-M

Ok, I PMed you the ID and pass.

whe i try to inciate XBCD.exe i ge this error messange

 

"Error loading XBCDSU360.dll The specified module could not be found"

 

??

please use a version of the driver that is supported here.

 

XBCD360 is not.

Yes, the multi mappings share deadzones as well as amount of buttons and axis exposed to the system

 

changing these causes the device to reset which would cause the game currently utilising it to either crash or no longer receive information from the pad

So I would like a bit of assistance if possible. I have a bit of a goofy setup.

 

I'm using a Dual Shock 3 PS3 controller with the utility described here.

It exports the DS3 as a standard always present X360 wired controller with an ID of USB\VID_045E&PID_028E&REV_0114

 

I am able to successfully install and use the XBCD drivers for the virtual X360 pad just fine with the default configuration. It shows input through the game controllers window just fine.

 

The problem comes when I try to use the XBCD configuration Utility. The whole reason I want to use these drivers instead of the MS ones is being able to split the trigger input for DirectInput. However, upon opening the config utility it does not detect any pads, despite the pad functioning fine.

yeah, i don't know what the heck you're attempting, but theres no way i can support such an attempt

 

its true that the driver can support ps2 pads via a ps2 to xbox adapter, but that adapter changes the pads entire logic to that of an xbox pad

 

the ps3 controller already has a HID of its own, and im sure that xbcd is not even installing its driver on that pad (i doubt it would even work given the physical electrical differences).

yeah, i don't know what the heck you're attempting, but theres no way i can support such an attempt

 

its true that the pad can support ps2 pads via an ps2 to xbox adapter, but that adapter changes the pads entire logic to that of an xbox pad

 

the ps3 controller already has a HID of its own, and im sure that xbcd is not even installing its driver on that pad (i doubt it would even work given the physical electrical differences).

Perhaps you didn't quite understand what I posted. The driver DOES work because the utility emulates an X360 pad in device manager, precisely as you described for a PS2 adapter, but for a PS3 controller over bluetooth. Think of the custom bluetooth driver as a DS3 to X360 converter. The fact that it works gives me some hope. The utility normally works with the default microsoft drivers, so I figured I could replace those with this, since it's designed to replace the default MS drivers. My only issue is that the virtual device pad doesn't appear in the configuration utility. It DOES appear in device manager as "XBCD Xbox 360 Controller" and does work just fine, aside from the fact that I cannot configure it.

 

Is there some issue preventing a virtual pad from showing up in the config utility that doesn't affect actual pads? I can understand if that's the case, and wouldn't expect you to fix it. Since you say it does work for emulated PS2 to X360 adapters, I don;t see why it shouldn't work for this.

No, thats not how it works at all.

 

the Xinput dll included with scarlet crushes SCP filter is where the trickery occurs.

(very similarly to how X360CE works)

 

the PS3 pad is otherwise installed with the stock standard microsft HID driver so the actual hardware is still presenting a PS3 pad which is utilising the HID driver

 

what the SCP filter does is install a filter onto the ps3 hid driver that allows the xinput dll to start the control when it is initilised by copying it into a games folder and starting the control by sending a wake up command that the HID driver doesn't support by default.

 

The reason the XBCD control panel does not work, is because the driver is not actually installed. It didn't find a supported Xbox product id, since this is only presented to Xinput apps utilising Scarlet Crushes xinput wrapper (Xinput1_3.dll).

 

Edit - i just got a better understanding of what he/she is doing with the filter and im afraid theres still no way it'll work.

All he/she is doing is using a custom HID descriptor (JUST LIKE XBCD) to force apps to detect the pad as a Xbox pad

 

You absolutely cannot install XBCD because it also uses a virtual HID driver.

Well then, any suggestions how I might be able to separate the triggers using some other method?

 

... I still don't get why you're saying I can't install it when I already have installed it and used it to play games just fine >_>

Completing the setup and the dpinst phase does not mean the driver is installed.

 

the setup phase just places the files and creates the necessary registry information for the supported controls, while the dpinst phase will complete regardless of whether the available control is supported or not.

 

in this case, dpinst just adds the driver to the windows driver store for whenever you finally connect a supported device.