5 ms·

Could you provide some technical detail on the creation process? The Xbox One controller doesn't identify itself as a Human Input Device, so it requires a Kext,

by jpierre 12y ago

Could you provide some technical detail on the creation process? The Xbox One controller doesn't identify itself as a Human Input Device, so it requires a Kext, yeah? Did you need to use a USB sniffer to identify the initialization sequence and button mappings? Another OS X Kext for the (USB) Xbox One controller, if only for comparison: https://github.com/FranticRain/Xone-OSX https://github.com/FranticRain/Xone-OSX

kgarten 12y ago
using the Xone-OSX https://github.com/FranticRain/Xone-OSX https://github.com/FranticRain/Xone-OSX works quite fine for me. Anybody has an input about the differences?
- fernandotakai 12y ago
  how's steam support?
  - kgarten 12y ago
    Castle Crashers and Guacamelee work well. Unfortunately, The Force Unleashed does not recognize it. Yet, believe it's a game specific problem (the port is terrible ...). Haven't tried other games.
- lloeki 12y ago
  I stumbled upon it just yesterday when packaging my release on GitHub. I purposely did not look at anything beforehand because 1) I wanted to do everything from A to Z myself†, and I knew TattieBogle's 360 driver was GPL licensed and 2) I wanted (made possible as a side effect of, and a motivation for, 1.) this one to be BSD. † When starting this I knew zilch about C++, USB, HID descriptors and kext development. Quite a roadtrip. (edit): A quick glance show that it's loosely based on TattieBogle's, and tries hard to mimic a 360 gamepad[0], down to the USB products id[1] and string. IOW it's not really a native Xbox One gamepad driver but an "emulator" of the 360 gamepad. [0]: https://github.com/FranticRain/Xone-OSX/blob/master/Xbox%20One%20Controller%20Driver/Xbox%20One%20Controller%20Driver/Xone_Driver.cpp#L436 https://github.com/FranticRain/Xone-OSX/blob/master/Xbox%20O... [1]: https://github.com/FranticRain/Xone-OSX/blob/master/Xbox%20One%20Controller%20Driver/Xbox%20One%20Controller%20Driver/Xone_Controller.cpp#L147 https://github.com/FranticRain/Xone-OSX/blob/master/Xbox%20O...
lloeki 12y ago
I'm planning to write an article about the development of this driver, including USB woes and writing the HID descriptor. The only thing I didn't do from scratch is getting the init packet (which I got from the Linux kernel).

by jpierre 12y ago

kgarten 12y ago

using the Xone-OSX https://github.com/FranticRain/Xone-OSX https://github.com/FranticRain/Xone-OSX works quite fine for me. Anybody has an input about the differences?

fernandotakai 12y ago
how's steam support?
- kgarten 12y ago
  Castle Crashers and Guacamelee work well. Unfortunately, The Force Unleashed does not recognize it. Yet, believe it's a game specific problem (the port is terrible ...). Haven't tried other games.
lloeki 12y ago
I stumbled upon it just yesterday when packaging my release on GitHub. I purposely did not look at anything beforehand because 1) I wanted to do everything from A to Z myself†, and I knew TattieBogle's 360 driver was GPL licensed and 2) I wanted (made possible as a side effect of, and a motivation for, 1.) this one to be BSD. † When starting this I knew zilch about C++, USB, HID descriptors and kext development. Quite a roadtrip. (edit): A quick glance show that it's loosely based on TattieBogle's, and tries hard to mimic a 360 gamepad[0], down to the USB products id[1] and string. IOW it's not really a native Xbox One gamepad driver but an "emulator" of the 360 gamepad. [0]: https://github.com/FranticRain/Xone-OSX/blob/master/Xbox%20One%20Controller%20Driver/Xbox%20One%20Controller%20Driver/Xone_Driver.cpp#L436 https://github.com/FranticRain/Xone-OSX/blob/master/Xbox%20O... [1]: https://github.com/FranticRain/Xone-OSX/blob/master/Xbox%20One%20Controller%20Driver/Xbox%20One%20Controller%20Driver/Xone_Controller.cpp#L147 https://github.com/FranticRain/Xone-OSX/blob/master/Xbox%20O...

lloeki 12y ago

I'm planning to write an article about the development of this driver, including USB woes and writing the HID descriptor. The only thing I didn't do from scratch is getting the init packet (which I got from the Linux kernel).