araghon007
windows 7 compatibility?
Any form to run this in windows 7? i try in win 10 and can do work fine with some games....so now i do some soldering work in impulse motors to put them with normal motor, like some force feedback but only soldering in same side, works even with epsxe emulator. i hope this can be compatible in the future in win7 beacuse i play in shit pc.
This converts normal XInput into Windows.Gaming.Input. That simply isn't there on W7 (in fact, I'm not even sure it was available in the first W10 builds).
If you want something "better for xbox one controllers" that works there, you'd better try to find something that maps onto the raw input api.
Well, I have tested it and it doesn't work. I actually forgot that the wireless dongle only works on Windows 8 and up, but even through USB cable it didn't work. First there's a crash when the configurator tries to get HID devices (one of the handles is null, and I haven't checked for that) and second, setting the HID report fails, no matter what report ID I use. I'll try looking into that a bit later then.
Did you isntall the directx redist? You only have the old ass 2005 xinput 9.1.0 version otherwise.
This isn't about XInput, but rather the driver side of things. If anyone managed to use the wireless dongle with Windows 7 (or 8.1) please let me know.
https://old.reddit.com/r/pcgamingtechsupport/comments/8byd8c/guide_how_to_make_xbox_one_controller_work_on/ https://www.touslesdrivers.com/index.php?v_page=23&v_code=52816 ?
Tried that, only getting error 10 on the dongle, and over cable I still can't set HID report
the kernel binary for the updated versions of the mini dongle is only able to be run on windows 10
There are 4 revisions of the "For Windows 10" mini dongle and 2 of the longer one.
Xbox Wireless Adapter for Windows 10 USB\VID_045E&PID_02E6 = 7/8 (6.3.9600.16384), 10 (19.29.20.953 - 21.50.45.656) USB\VID_0E8D&PID_7600 = 7/8 (6.3.9600.16384), 10 (19.16.17.976 - 19.29.20.953) USB\VID_0E8D&PID_7612 = 7/8 (6.3.9600.16384), 10 (19.16.17.976 - 19.29.20.953)
Xbox Wireless Adapter for Windows 10 - Windows 10 only
USB\VID_045E&PID_02F9 (1.0.45.0 - 1.0.45.1)
USB\VID_045E&PID_02FE (1.0.45.0 - 1.0.46.1)
USB\VID_045E&PID_091E (18.31.1.43 and 1.0.45.4 - 1.0.45.5)
The newer dongles with the 1.0.xx.x versioning adheres to the windows 10 Network Adapter WDF Class Extensions
Ah, thanks a lot for the info. I have the 02FE one, which would explain things. I'm assuming the Windows 7 compatible ones were released more recently?
But either way, the issue remains that I wasn't able to set the HID report even through USB. I'm hoping someone with more experience with HID could help me out here. I was able to see that the URBs were the same as in Windows 10 though, so I have no idea what's up with that.
I'm assuming the Windows 7 compatible ones were released more recently?
The opposite actually, 02E6 is the oldest of the 4 mini dongles.
annoyingly, its what i received 2 years ago directly from microsoft when i bought one instead of one of the newer dongles, so it has the issue where occasionally windows decides it is the current network adapter.
As to this issue, windows 7 only exposes the feature set of an Xbox 360 control and doesn't expose the XinputHID capabilities that 8+ introduced.
Gaming.Input is on 10 yes, but the XinputHID drivers are from 8.
on 7, the One and Core controllers aren't treated as more than Xbox 360,
the controller itself uses the xb1usb.sys driver, and the hid-compliant sub device uses the legacy hidusb.sys/hidclass.sys combo, this changes on 8+ where the xbox controls get an xbox platform hid filter.
I just found a version of the 1.0.46 driver that installs on 02E6 variants of the dongle o.o