NOTE: If you want to use the driver without access to the source code, check the releases page.

• Run the installer located on the releases page.
• Reboot
• Plug the controller in, without powering it on, and it should light up.
• Enjoy!

I don't recommend leaving batteries in the controller while using it wired for extended periods of time. This could potentially cause wear on the batteries that is best avoided.

This is a kext and preference pane that allows users to use the Xbox One controller with their OS X computer. Because the Xbox One controller does not identify as a Human Interface Device, and requires custom startup code, a custom driver had to be made.

There is an uninstaller included in the .dmg. Simply run it, and it will take care of the rest!

• Performs custom startup and handles all buttons on the controller
• Customizable deadzones for both sticks and triggers
• Invert X and Y for each stick individually
• Preference pane allows you to see your controller in action
• New awesome graphics, thanks to k1down
• Signed

• Most games that support a 360 controller. Create an issue if a game works with the 360, but not the Xbox One controller.
• DDHidLib (Ex. OpenEmu)
• Steamworks Controller API (Steam Big Picture, and other Steam games that implement the API)

• Force Feedback (Rumble)
• Recognize controller as GCController
• Change controller input to keyboard input (setting) so as to support unsupported games
• Compatibility with games not using Steamworks API
• Wireless will work with the future release of the controller dongle.

OS X Yosemite introduced a new security feature requiring all kernel extensions to be signed by a certificate with a new custom extension (OID 1.2.840.113635.100.6.1.18) that designates it as a kext-signing certificate. On reboot, unsigned kexts or those with invalid signatures will be left unloaded and the system will alert the user via a warning.

Those hoping to build and run the kext from source, have a couple of options.

A kext developer mode can be enabled to allow invalid signatures. This is a global setting and will disable kext signature checking for the entire system! To enable the mode, run the following and reboot:

$ sudo nvram boot-args=kext-dev-mode=1

To revert to the system default setting of disallowing invalid kext signatures, run the following and reboot:

$ sudo nvram -d boot-args

If enrolled in the Mac Developer Program, one can request the special certificate on the Apple Developer page Requesting a Developer ID Certificate for Signing Kexts - it is worth noting that the certificate is intended for those needing to sign a kext that is commercially shipped or broadly distributed through a large organization.

Kernel extensions are loaded on demand and if the controller does not light up when attached, one could check if the kext is loaded - the kext's status should be displayed if loaded via:

$ kextstat | grep Xone

Though generally unnecessary, the kext can be manually loaded as well:

$ sudo kextutil -t /Library/Extensions/Xone\ Driver.kext

• There doesn't appear to be any documentation as to how to implement a KEXT so that the controller is recognized as a GCController, so currently it is not.
• I couldn't quite grasp how to convert the D-pad Data (4 consecutive bits with 0 for unpressed and 1 for currently pressed) into a proper HID implementation.
• I'm looking into updates to the TattieBogle driver that make rumble implementation clearer.
• The xbox button is handled in a separate packet, which means that it has to be different from the Xbox 360 implementation.