This project packages an Xbox One controller driver for Mac OS X built on topof the IOKit framework. It is a true kernel mode driver, meaning that programsbuilt with the user-facing IOKit API will recognize the controller (but alsomeaning that the driver needs wired memory for its code, and that a failurewill bring down the whole operating system).
It is based on the documentation found on kylelemons's xbox and bkase'sxbox-one-fake-driver repositories, though it shares no common code.
The Xbox One controller is not HID-compliant, and this is the reason thatgeneric drivers aren't sufficient. However, it's not too far from a compliantdevice. The three main differences are that:
- the device needs to be 'turned on' by the computer (which is done by sendingit
05 20); - the device sends more than just HID reports on the interrupt pipe;
- the device does not expose a report descriptor.
This driver attempts to bridge these three shortcomings.
Status
I'm hoping other people with an Elite controller can help me determine if mine has a problem that others aren't seeing. I got an Elite controller on launch day. Almost immediately, I noticed that I was activating the left trigger a lot when I didn't mean to. Filmlight baselight for nuke 4.4.10055 for mac. Specifically, in Destiny, while running around I would aim down sights without really. Xbox One Wireless Controller Trigger Rumble Motor Replacement. The guide is a Rumble Motor replacement, but the process is still the same. After you have the Rumble Motors off, You're able to undo the spring, and the trigger just falls off. I can't seem to find a part yet, i'll let you know when I do. All the ones I see are out of stock.
In my book, this driver is ready for production. This means that it is usefulfor actual gaming and that people are unlikely to have problems with it.
The driver only works when the controller is connected with a USB cable to theMac. I believe that the controller does not use Bluetooth, which makes itunlikely to ever work unless Microsoft releases some USB dongle.
Technicalities
The driver exposes the controller as a HID gamepad whose name is 'Controller'(that's Microsoft's controller guys' fault, not mine, though it wouldn't be veryhard to change). This gamepad has 16 buttons and six axes:
- Button 1: Sync
- Button 2: ?
- Button 3: Menu ('start')
- Button 4: View ('select')
- Button 5: A
- Button 6: B
- Button 7: X
- Button 8: Y
- Button 9: D-Up
- Button 10: D-Down
- Button 11: D-Left
- Button 12: D-Right
- Button 13: Left Bumper
- Button 14: Right Bumper
- Button 15: Left Thumb Stick Press
- Button 16: Right Thumb Stick Press
- Axes X, Y: Left Thumb Stick
- Axes Rx, Ry: Right Thumb Stick
- Axis Z: Left Trigger
- Axis Rz: Right Trigger
You'll notice that the triggers are considered axes. This is because the XboxOne controller has analog triggers with values varying between 0 and 1023.These are not buttons (in the sense that buttons can only be either on or off).
The driver does not expose rumble motors. From badgio's XboxOneControllerproject, it appears that the magic byte sequence to send to the controller is:
where .w and .x are values for the left and right triggers, and .y and.z are values for the left and right handles, respectively. So on thecontroller's side, force feedback is fairly simple. The problem is that from theonly example implementation of force feedback I could find, it appears thatthe work required on the software side is non-trivial. Not to mention thatI know of just one application that takes advantage of it.