Wired 360 Controller Not Working

[briannn]

Hi everyone,

I'm currently trying to hook up a wired Xbox 360 controller in order to play Team Fortress 2 on my Macbook Pro 13" (mid 2010).

I'm currently running Lion, OS X 10.7.5

So, I've been scouring the internet for hours, just to find out how to get this stupid controller to work, all to no avail. The latest method I've done can be found here: https://forums.macrumors.com/threads/1327396/

I have whatever the latest driver is on Tattie as well as the 360ControllerSource file downloaded. In regards to the driver, it installed without problem, and even shows up in my System Preferences, but when I click it no controller shows up. I am using a brand new, official Xbox 360 wired controller. I've uninstalled and reinstalled and restarted my computer countless times and tried every method I could find, but nothing is working; my computer will not detect the controller.

It lights up briefly when initially plugged in, then after a second or two, it goes dark.

If there's any other info that would be helpful to know, please let me know; I'm really desperate to get this to work!

Thanks,
Brian

 

[sarthak]

I use a Razer Onza TE BF3 edition 360 controller and it works just fine on Mountain Lion & Mavericks. You should not need the controller driver if the game supports it. For ex. F1 2012 supports the controller without having to install the driver.

If the game doesn't natively support it, then all you should need is the 360ControllerDriver.dmg from http://tattiebogle.net and after installing that it should just work. Check the settings in system preferences.

The latest driver is 0.12 and the method in the thread has a link to 0.08. Are you sure you're on the latest one? You could also try creating a new user account and installing the driver on that one. If all else fails, buy ML, create a USB Install Disk and clean install Mountain Lion onto the system if possible.

Can you check under System Information -> USB -> XBOX 360 CONTROLLER, is the controller status "Unknown" or is it initialized and drawing power. If it doesn't work in Windows then your controller might need replacement.

 

[briannn]

Hi mseth,

The driver I got should be .12, which I picked up from another forum suggestion, however, I followed the steps on the link I posted after the other ones didn't work.


When looking under System Information, USB, this is what it says under "Controller":

Product ID: 0x028e
Vendor ID: 0x045e (Microsoft Corporation)
Version: 1.14
Serial Number: 1BC0D94
Speed: Up to 12 Mb/sec
Manufacturer: ©Microsoft Corporation
Location ID: 0x06400000 / 5
Current Available (mA): 500
Current Required (mA): Unknown (Device has not been configured)

Thanks for the quick reply.

 

[sarthak]

Current Required (mA): Unknown (Device has not been configured)

That means the driver is NOT working.

If you have not tested the controller before:
It could also be the controller. Have you tested the controller in a different operating system, are you sure it is not defective? If not and if you have time try this:

- Download a free trial of Parallels if you don't already own it.
- Download Windows 8.1 free trial ISO image.
- Install it in Parallels as a Virtual Machine
- When you start it, in the menu bar, click Devices -> USB -> 360 Controller.

This will connect the controller to the Windows 8.1 Virtual Machine you have set up. Under Game controllers check to see if all buttons and pads are working.

If you know the controller works:
Are you plugging in the controller once you login or are you leaving it plugged in on boot? Try creating a new user account and installing the driver in that.

ALTERNATIVE LOADING METHOD (BEWARE):
Open Finder -> Press CMD+G -> Type "/System/Library/Extentions"

Do you see a Kext file with the name 360Controller.kext ?
- If yes, then the driver is installed and it might not have loaded.
- If no, then the driver is not installed or not installed properly.

IF YES, then run the following commands in terminal.

cd /System/Library/Extentions
sudo kextutil 360Controller.kext/

Disconnect and reconnect the controller. Then check System Preferences.

If all else fails, consider creating a new user and trying there or updating to Mountain Lion or wait until Mavericks.