If you're a Mac gamer who's tired of trying to game on your mouse and keyboard, you should get an Xbox 360 controller. By connecting an Xbox 360 Controller to your Mac and mapping its buttons to keystrokes (or mouse actions), you can bring the console experience to your Mac without breaking the bank -- or a sweat.
The OS X driver for Xbox 360 controllers is free, but it's only compatible with 1st-party peripherals. We like the "Xbox 360 Wireless controller for windows," which comes with a wireless receiver. (You'll need this, because unfortunately 360 controllers don't use Bluetooth.) For what it's worth though, you can also use the controller with a regular Xbox 360. Like an actual Xbox, the included receiver can connect with up to 4 wireless controllers at once. And at less than $50 on Amazon, the package still costs less than a fancy gaming mouse.
Controllers or wireless receivers (like this one) that don't bear Microsoft's shiny sticker of authenticity are made by a 3rd-party, so even if they look legit and have the Xbox 360 logo printed on them they won't work for this project.
If you're using a wired controller, this is as easy as plugging it into your Mac's USB port. For wireless, plug in the USB receiver, turn on your controller, and hold the Connect buttons on both devices until a connection is established.
A few Mac games are accommodating enough that they'll recognize your connected controller, and might even let you pick your own control scheme. If this works, you can forget Gamepad Companion (because you won't need it) and skip right down to our very last step.
For now, let's stick to single-action buttons. (We'll map controls to the thumbsticks and triggers next.) Key mapping in Gamepad Companion is simple. Let's say the Space key means Jump, and you want to map that to the A button: Press A on your controller, click on "Single Key..." in the Action menu, then press Space on your keyboard.
Not many of us know it, but there could be a handy use for all those old Xbox 360 or Xbox One controllers. But before you get set up, you need to have the correct hardware installed on your Mac to enable connectivity.
First of all, you will need either a wired or wireless Xbox controller. Both work fine, but for all those passionate gamers with a tendency to erupt, a wireless device would be best to save any damage to wires (or opponents). These wireless receivers can be bought for around $20 on Amazon and handle up to 4 Xbox 360 controllers.
This is an early release of a modern rewrite for this driver. It updates the driver to the modern standard and re-implements wireless controller support. If you find any regression in the driver, make sure to make an issue and specifically mention that you are using this version of the driver.
This is an early release of a modern rewrite for this driver. It should exactly match the functionality of the existing driver. So wireless controllers are still not supported at this time, but your wired controllers should work exactly as intended. If you find any regression in the driver, make sure to make an issue and specifically mention that you are using this version of the driver.
This is the first pass at a modern rewrite for this driver. It should exactly match the functionality of the existing driver. So wireless controllers are still not supported at this time, but your wired controllers should work exactly as intended. If you find any regression in the driver, make sure to make an issue and specifically mention that you are using this version of the driver.
It looks like the hang on boot that some users were experiencing was caused by the Xbox One controller Bluetooth support hooks that had been added to the driver. In order to resolve those issues, all Bluetooth support has been removed from the driver. Simply put, if you are using the controller via Bluetooth, the driver won't do anything for you. Please do not install older versions of the driver in order to get the force feedback over Bluetooth support and then post an issue about your computer hanging on boot.
In addition, a variety of new devices have been added and some minor touch ups were made to Xbox One racing wheel support. Currently, we still do not support the Xbox Adaptive controller, but we are actively exploring support for it.
The guide button on Xbox One S-era (Bluetooth-capable) controllers now works properly as a button, instead of a permanent switch! Also, Force feedback is back! Rumble on. Speaking of which, rumble options for Xbox One controllers have been fixed, so you can rumble the triggers only, or the triggers and the main motors in unison if you want! Whatever floats your boat. And good news, all of the settings changes you make in the preference pane will now actually be saved. Settings bugs have been vanquished and now you won't have to check "Pretend to be an Xbox 360 Controller" every time you reboot your computer. There are some other under the hood fixes that will probably go un-noticed, but the main Readme and the text during installation have gotten a little spring cleaning, so keep an eagle eye out for that.
I suppose it can be done via Bluetooth, or having a reciever plugged into an USB port, but I'm not sure which controller type should I buy. I have an Xbox 360 wireless controller (2013), but it seems not discoverable at all.
It works with the official Microsoft 360 wireless receiver. Probably also the knockoffs. It works with tons of unofficial 360 controllers. Tons of Xbox One controllers. Even tons of original Xbox controllers, if you can figure out how to plug them in.
As of macOS 10.11, Wireless Xbox 360 controller support causes kernel panics. This issue cannot be resolved with minor changes to the driver, and requires that the driver be re-written from scratch to resolve the issue. Due to an excess of caution, we have disabled Wireless Xbox 360 controller support as of 0.16.6. If you want to use a wireless controller, download 0.16.15 or earlier and disable the driver before the computer enters a "sleep" state in order to prevent kernel panics. Alternatively, you can revert to a macOS version before 10.11 to avoid this issue.
I picked up Borderlands 2 for OS X in the recent Steam sale because friends of mine would NOT shut up about the game. So I fired it up only to find out that I needed to use a keyboard (lots of keys) + a mouse (carpal tunnel = no) to play. That sucks. I was hoping that I could use a borrowed Xbox 360 controller to play through, but Aspyr doesn't support that. Grr. So after some research I found a way to use both a wireless Xbox 360 controller as well as a wired third-party Xbox 360 controller. This worked for Borderlands 2 and other games I've tried so far. The cost for this is $5 for the wired controller and $20 for the wireless. Here are the two setups that worked for me.
To connect the wireless 360 Controller to my Macbook Pro I got this wireless gaming receiver for $15 (incl. tax) on Amazon. The computer still wasn't recognizing it, so I installed Tattiebogle 0.11 which you can download here. Follow the instructions for installing and then open up the "Xbox 360 Controllers" icon in your System Preferences. Link up your controller to the receiver and you should now be able to see reactions to you messing around with buttons and analogs on the 360 controller. This is great, but many games will still not recognize your controller. So now you need to map your buttons to keyboard commands. To do that you will need to get Joystick Mapper in the App Store. Once you're in Joystick Mapper you can assign all of the buttons and analogs to keyboard and mouse controls. This will take some trial and error to find out what works best for you, but it does work.
There are many many different 360 controllers out there. Fortunately, there are people out there who can help you out. Once you have Tattiebogle installed you can add support for more controllers. After installing Tattiebogle like described in the last step for the wireless controller, download this link and run the command script to update Tattiebogle. This comes from Shoryuken forum member EddDeDuck. The forum post I found this is here. (Note: found out the link for the command script is now broken. File attached to this step) You will also need the Joystick Mapper app from the App Store to make this work. OK, that's it. Have fun.
360Controller.kext has invalid signature; omitting.More info:I used parallels and created a virtual machine. when I plugged in my xbox 360 receiver, it asked me if I wanted to map it to my Parallels virtual machine or my computer (my Mac). I mapped it to parallels. But now I am trying to map it back to my Mac and I have no idea how to because the 360 receiver hardware isn't registering in the driver configuration settings for the 360 wireless receiver..
however, the controller has been registered by my system profile. tldr; my mac recognizes my controller, but the drivers don't, and I think the cause of the problem is because somehow my controller is tied to my parallels virtual machine desktop. Additionally I fear somehow some of my system memory is somehow tied up in parallels and not accessible from my mac desktop. not sure if that's even possible but it appeared my video card RAM was lower than the specs should be in my system profile. but I'm a noob so i could be wrong. 2b1af7f3a8