XInput compatibility ramblings

[nefarius]

Might as well utilise discussions myself instead of content getting lost in Discord or the forums 😇

About

I haven't given up on my quest to also add native XInput compatibility to the project, meaning no need for additional proxy applications like DS4Windows or even emulators like ViGEm. Basically I'd love to utilise the stock Microsoft driver xinputhid.sys which plays a big part in the latest Xbox One Series X Controllers functionality. I deciphered a lot on it's functionality already, so much as that the device works with XInput compatibility, hooray! 🥳 Sadly though, I haven't yet managed to solve the doubled DI device issue that still persists despite the filter proxying my HID device:

So this is almost production-ready. I don't feel good releasing with this "flaw" as I don't want to depend on yet another piece of software like HidHide, just because of this missing piece. I believe it is possible, both wired and wireless 😎

Resources

• Amazon Lua Controller pulls off a similar trick (on BLE)
  • SDL contribution for said controller
• Xbox One Controller HID Report Descriptor Collections

Disassembly

JEB

Trace GUIDs:

• {E625F3D5-67C7-D739-23E9-7598B498AAD4}
• {3A91130C-1703-CF32-7FB8-FBDB6CBA3766}

[nefarius]

Success

Well, well, well, will you look at that 👀

[nefarius]

Device IDs notes

Some examples of Device Instance and Hardware IDs for comparison.

Xbox One Series X over BLE

Device Instance Path

BTHLEDEVICE\{00001812-0000-1000-8000-00805F9B34FB}_DEV_VID&02045E_PID&0B13_REV&0505_4416226B4811\B&12F4624B&0&0016

Hardware IDs

BTHLEDevice\{00001812-0000-1000-8000-00805f9b34fb}_Dev_VID&02045e_PID&0b13_REV&0505
BTHLEDevice\{00001812-0000-1000-8000-00805f9b34fb}_Dev_VID&02045e_PID&0b13
BTHLEDevice\{00001812-0000-1000-8000-00805f9b34fb}_LOCALMFG&000a

Device Instance Path

HID\{00001812-0000-1000-8000-00805F9B34FB}&DEV&VID_5E&PID_0B13&REV_0505&4416226B4811&IG_00\C&E161A18&1&0000

Hardware IDs

HID\{00001812-0000-1000-8000-00805f9b34fb}_Dev_VID&02045e_PID&0b13_REV&0505
HID\{00001812-0000-1000-8000-00805f9b34fb}_Dev_VID&02045e_PID&0b13
HID\{00001812-0000-1000-8000-00805f9b34fb}_LOCALMFG&000a
HID\VID_045E&UP:0001_U:0005
HID_DEVICE_SYSTEM_GAME
HID_DEVICE_UP:0001_U:0005
HID_DEVICE

DS3 over BthPS3

Device Instance Path

BTHPS3BUS\{53F88889-1AAF-4353-A047-556B69EC6DA6}\B&20A6250C&0&44D832809FCD

Hardware IDs

BTHPS3BUS\{53f88889-1aaf-4353-a047-556b69ec6da6}

Device Instance Path

HID\{53F88889-1AAF-4353-A047-556B69EC6DA6}&IG_00\C&25BB9512&4&0000

Hardware IDs

HID\{53f88889-1aaf-4353-a047-556b69ec6da6}&MOD_05
HID\VID_7331&UP:0001_U:0005
HID_DEVICE_SYSTEM_GAME
HID_DEVICE_UP:0001_U:0005
HID_DEVICE

DS3 over USB

Device Instance Path

USB\VID_054C&PID_0268\8&1203F332&0&3

USB\VID_054C&PID_0268&REV_0100
USB\VID_054C&PID_0268

Device Instance Path

HID\VID_054C&PID_0268\9&29F81D96&4&0000

Hardware IDs

HID\VID_054C&PID_0268&REV_0100
HID\VID_054C&PID_0268
HID\VID_054C&UP:0001_U:0005
HID_DEVICE_SYSTEM_GAME
HID_DEVICE_UP:0001_U:0005
HID_DEVICE

Xbox One Series X over Bluetooth Classic

Device Instance Path

BTHENUM\{00001124-0000-1000-8000-00805F9B34FB}_VID&0002045E_PID&0B13\A&579146A&0&441622797ACA_C00000000

Hardware IDs

BTHENUM\{00001124-0000-1000-8000-00805f9b34fb}_VID&0002045e_PID&0b13
BTHENUM\{00001124-0000-1000-8000-00805f9b34fb}_LOCALMFG&000a

[nefarius]

Identified the issue on wireless DI/XI detection problems; the MS driver stack properly formats the Device Instance ID for the game engines to parse an expected string format like so:

\\?\hid#{00001812-0000-1000-8000-00805f9b34fb}&dev&vid_5e&pid_0b13&rev_0505&4416226b4811&ig_00#c&e161a18&1&0000#{ec87f1e3-c13b-4100-b5f7-8b84d54260cb}

While BthPS3 in my latest attempt to mimic the BLE bus driver it ends up mangled in the HID PDO:

\\?\hid#{53f88889-1aaf-4353-a047-556b69ec6da6}_dev_vid&01054c_pid&0268_44d832809fcd&ig_01#c&2f83b887&0&0000#{ec87f1e3-c13b-4100-b5f7-8b84d54260cb}

I've reliably fixed this by updating BthPS3 🥳

[nefarius]

Behold, thy compatibility fix for BthPS3 is live for imminent Beta testing 👀