It IS installed and it DOES work. The driver is functioning fine. The XBCD Controller shows up in the controllers panel and receives input ... it's the config app that isn't playing nice.
Â
I'm not trying to be pushy ... I just get the feeling you aren't quite understanding me [img]<fileStore.core_Emoticons>/emoticons/sad.png[/img]/emoticons/sad@2x.png 2x" width="20" height="20" />
just because the device name is XBCD Controller driver (changed by the setup script) doesn't mean the driver installed by dpinst is the one being utilised by the controller.
Â
screenshot the Human interface devices section of device manager
Ah I see. There's two devices now, one which is a generic game controller, and another labeled XBCD. Both with the same ID.
Â
This is kinda confusing to me I admit. The entry for the controller in the "Devices and Printers" control panel section references BOTH the virtual bus controller that I installed XBCD to, and the generic HID.
Â
Why is it that I saw a change in the controller's behavior and button layout when I installed XBCD over the Microsoft drivers? I don't recall the generic device being present when I was using the microsoft drivers.
