Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
OS X Use Xbox 360 controller with Mac!
- Thread starter Jameshrcairns
- Start date
- Sort by reaction score
Thanks for your response Edwin. At least I can give up knowing there's not much I can do at this point.
/ goes off to see if it's possible to get my Dreamcast arcade stick working with a mac (fears the worst).
If I make any progress on that I will let you know.
Edwin
Hey guys,
I've been trying to get my wired Xbox 360 controller to work with my mid 2009 MBP in conjunction with the Dolphin emulator.
In the past, I have used the Xbox360Controller driver from Tattiebogle with success (this was ~winter 2011). However, I later installed Gamepad Companion (~spring 2012) which caused the middle button of the controller will flash once then disappear. The controller is not detectable by either the Gamepad Companion software nor the Xbox360Controller software.
I've read in this thread that it may be worthwhile to delete all drivers related to Gamepad Companion (my demo has expired anyway), however when I go to System/Library/Extensions, the folder is empty (I cannot view kernels/drivers).
What I am asking you guys is:
1) How do I purge my mac from all Gamepad Companion-related software (I heard it interferes with functional drivers like the one from Tattiebogle)?
2) Am I proceeding in the right direction?
Currently running on OSX 10.6.8.
I've been trying to get my wired Xbox 360 controller to work with my mid 2009 MBP in conjunction with the Dolphin emulator.
In the past, I have used the Xbox360Controller driver from Tattiebogle with success (this was ~winter 2011). However, I later installed Gamepad Companion (~spring 2012) which caused the middle button of the controller will flash once then disappear. The controller is not detectable by either the Gamepad Companion software nor the Xbox360Controller software.
I've read in this thread that it may be worthwhile to delete all drivers related to Gamepad Companion (my demo has expired anyway), however when I go to System/Library/Extensions, the folder is empty (I cannot view kernels/drivers).
What I am asking you guys is:
1) How do I purge my mac from all Gamepad Companion-related software (I heard it interferes with functional drivers like the one from Tattiebogle)?
2) Am I proceeding in the right direction?
Currently running on OSX 10.6.8.
The contents of /System/Library/Extensions should not be empty! If you can't view the files on Finder, try using the terminal.
Awesome. Got the terminal to display all kernels and plugins.
Now...is there anything specific I'm looking for that may prevent the (Tattiebogle) Xbox360Controller from working?
I suspect the following kernels may need to be deleted:
ControllerMate.ktext
Wireless360Controller.ktext
WirelessGamingReceiver.ktext
Here is the procedure I've used for deleting the above kernels, but it appears not to be working.
Step 1
ls /system/library/extensions
Step 2
sudo rm f /System/Library/Extensions/ControllerMate.ktext
Step3
It then prompts me to enter a password, and upon entering the password I get this response:
Password:
Sorry, try again.
Password:
rm: f: No such file or directory
rm: /System/Library/Extensions/ControllerMate.ktext: No such file or directory
MZ-MacBook-Pro:Extensions mz$ sudo rm f /System/Library/Extensions/ControllerMate.ktext
Any help?
Now...is there anything specific I'm looking for that may prevent the (Tattiebogle) Xbox360Controller from working?
I suspect the following kernels may need to be deleted:
ControllerMate.ktext
Wireless360Controller.ktext
WirelessGamingReceiver.ktext
Here is the procedure I've used for deleting the above kernels, but it appears not to be working.
Step 1
ls /system/library/extensions
Step 2
sudo rm f /System/Library/Extensions/ControllerMate.ktext
Step3
It then prompts me to enter a password, and upon entering the password I get this response:
Password:
Sorry, try again.
Password:
rm: f: No such file or directory
rm: /System/Library/Extensions/ControllerMate.ktext: No such file or directory
MZ-MacBook-Pro:Extensions mz$ sudo rm f /System/Library/Extensions/ControllerMate.ktext
Any help?
Ahh, so all I have to do is delete the controller mate kernel.
Do you guys check the command I posted above? When I re-typed ls /system/library/extensions the controllermate kernel is still there :/
Do you guys check the command I posted above? When I re-typed ls /system/library/extensions the controllermate kernel is still there :/
You are using the wrong dash is my guess. You also need to pass -r to get rid of directories, which is what kexts are. Also, I recommend that you unload the kexts before deleting them using kextunload (must be run as root), otherwise you will need to restart the computer.
Awesome. Got the terminal to display all kernels and plugins.
Now...is there anything specific I'm looking for that may prevent the (Tattiebogle) Xbox360Controller from working?
I suspect the following kernels may need to be deleted:
ControllerMate.ktext
Wireless360Controller.ktext
WirelessGamingReceiver.ktext
Here is the procedure I've used for deleting the above kernels, but it appears not to be working.
Step 1
ls /system/library/extensions
Step 2
sudo rm f /System/Library/Extensions/ControllerMate.ktext
Step3
It then prompts me to enter a password, and upon entering the password I get this response:
Password:
Sorry, try again.
Password:
rm: f: No such file or directory
rm: /System/Library/Extensions/ControllerMate.ktext: No such file or directory
MZ-MacBook-Pro:Extensions mz$ sudo rm f /System/Library/Extensions/ControllerMate.ktext
Any help?
You added an extra t
Code:
sudo rm f /System/Library/Extensions/ControllerMate.k[U][B]t[/B][/U]exttry this:
Code:
sudo rm f /System/Library/Extensions/ControllerMate.kextHaha thank you very much, dunno how I overlooked that!
Here are the command combinations I tried and affiliated errors:
kextunload /System/Library/Extensions/ControllerMate.kext
You must be running as root to unload kexts, terminate services, or remove driver personalities.
sudo kextunload /System/Library/Extensions/ControllerMate.kext
Can't open CFBundle for /System/Library/Extensions/ControllerMate.kext.
MZ-MacBook-Pro:extensions mz$
sudo rm –f /System/Library/Extensions/ControllerMate.kext
Password:
rm: -f: No such file or directory
rm: /System/Library/Extensions/ControllerMate.kext: is a directory
sudo rm -rf /System/Library/Extensions/ControllerMate.kext
(Here there is no error, nothing happens).
After all of this, I finally got rid of it (confirmed with ls command of extensions folder).
Not sure WHICH of these steps worked, but this is just for any one who comes across this thread.
Much thanks and love, will tell you if the 360controller driver now works with the xbox 360 controller soon.
EDIT
Still no luck with the controller...flashes once then is unresponsive (not being picked up by TattieBogle Xbox360Controller driver even after reboot).
Here are the command combinations I tried and affiliated errors:
kextunload /System/Library/Extensions/ControllerMate.kext
You must be running as root to unload kexts, terminate services, or remove driver personalities.
sudo kextunload /System/Library/Extensions/ControllerMate.kext
Can't open CFBundle for /System/Library/Extensions/ControllerMate.kext.
MZ-MacBook-Pro:extensions mz$
sudo rm –f /System/Library/Extensions/ControllerMate.kext
Password:
rm: -f: No such file or directory
rm: /System/Library/Extensions/ControllerMate.kext: is a directory
sudo rm -rf /System/Library/Extensions/ControllerMate.kext
(Here there is no error, nothing happens).
After all of this, I finally got rid of it (confirmed with ls command of extensions folder).
Not sure WHICH of these steps worked, but this is just for any one who comes across this thread.
Much thanks and love, will tell you if the 360controller driver now works with the xbox 360 controller soon.
EDIT
Still no luck with the controller...flashes once then is unresponsive (not being picked up by TattieBogle Xbox360Controller driver even after reboot).
Last edited:
Now working for me
Came back just to say I got this to work with something fairly easy..
FYI This is on a 2011 15" MBP (top-end), Lion, with both wireless and wired (official) xbox controllers. I bought the wired after giving up on the wireless, only to find the wired had the same issues. But now they both work.
Before right this second, trying the newest edition of tattiebogle did not work, neither did downloading the extra controllers file, neither did manually editing in product/vendor IDs (or their decimal equivalents) to the kext file. Always got "no devices found"
This time, however, after deleting .12 from the pane, and deleting the 360controllers.kext file, then installing the .11 tattiebogle driver (yes, .11 NOT .12, and I still got a notification about their being a newer version on my computer).
I then pulled up the pref pane and (!) noticed the button with a "+" sign to the left of where it says "no devices found". I don't know if it's there in .12 but I didn't notice it before. Clicking on this there was a list of about 8 drivers, including a "MadCatz Controller". I decided maybe my last best chance was to try editing the device IDs under that entry, since obviously the pane was 'ready' to accept a MadCatz if I had one. So I'd say, first find out which ones are already in your list, and edit one. (The list was full of controllers I don't own)
To edit the list, instead of opening the kext (which didn't work last time) I opened (in textedit) the file that automatically imports all the 65+ devices (available here as of today. Says ZIP but it's actually just a command file). I replaced the MadCatz controller device & manufacturer IDs with the DECIMAL versions of the microsoft controller (as found under utilities pane --> system information --> usb --> controller, then just convert to decimal). I saved a version and double-clicked it, which pulls up a terminal window asking for your password. The file should append the information into your kext file.
Keep in mind, at least on my computer, in the system information program I think device ID came before manuf ID, and in the controller addition file it was the other way around. Scroll down to the callouts/notes section and it specifies which order it's in).
After doing so I didn't even need to restart. It was just in the controller pane as 'controller 1' and so far it recognizes joystick and button input. I still haven't gamed with it yet.
I really don't know if this would have worked for me on tattiebogle .12, but I spent so many hours doing this that it's working now and I don't dare mess with it. The frustration of all this just has me hoping this will help someone else stop banging their head against the wall. I have some friends who work in the xbox division so maybe if I bother them enough they'll have someone make a driver.
So in short (steps one and 2 might not be necessary, try starting at 3 if there is a "+" button available):
1. Remove TB v.12 by deleting pref pane and kext file, restart.
2. Install TB v.11, restart.
3. Open pref pane, click "+" button on left. Choose a controller there, any controller (that you don't own)
4. Plug your controller in, find device and manuf. ID, convert to decimal
5. Download and edit extra controllers file, edit entry for chosen controller(put dev and manuf id in the right place!) Save.
6. Unplug controller, run the extra controllers command file.
7. Plug controller back in. Press the xbox button/wireless connect if needed. Worked for my wireless as well (newest revision)
8. Pray
Came back just to say I got this to work with something fairly easy..
FYI This is on a 2011 15" MBP (top-end), Lion, with both wireless and wired (official) xbox controllers. I bought the wired after giving up on the wireless, only to find the wired had the same issues. But now they both work.
Before right this second, trying the newest edition of tattiebogle did not work, neither did downloading the extra controllers file, neither did manually editing in product/vendor IDs (or their decimal equivalents) to the kext file. Always got "no devices found"
This time, however, after deleting .12 from the pane, and deleting the 360controllers.kext file, then installing the .11 tattiebogle driver (yes, .11 NOT .12, and I still got a notification about their being a newer version on my computer).
I then pulled up the pref pane and (!) noticed the button with a "+" sign to the left of where it says "no devices found". I don't know if it's there in .12 but I didn't notice it before. Clicking on this there was a list of about 8 drivers, including a "MadCatz Controller". I decided maybe my last best chance was to try editing the device IDs under that entry, since obviously the pane was 'ready' to accept a MadCatz if I had one. So I'd say, first find out which ones are already in your list, and edit one. (The list was full of controllers I don't own)
To edit the list, instead of opening the kext (which didn't work last time) I opened (in textedit) the file that automatically imports all the 65+ devices (available here as of today. Says ZIP but it's actually just a command file). I replaced the MadCatz controller device & manufacturer IDs with the DECIMAL versions of the microsoft controller (as found under utilities pane --> system information --> usb --> controller, then just convert to decimal). I saved a version and double-clicked it, which pulls up a terminal window asking for your password. The file should append the information into your kext file.
Keep in mind, at least on my computer, in the system information program I think device ID came before manuf ID, and in the controller addition file it was the other way around. Scroll down to the callouts/notes section and it specifies which order it's in).
After doing so I didn't even need to restart. It was just in the controller pane as 'controller 1' and so far it recognizes joystick and button input. I still haven't gamed with it yet.
I really don't know if this would have worked for me on tattiebogle .12, but I spent so many hours doing this that it's working now and I don't dare mess with it. The frustration of all this just has me hoping this will help someone else stop banging their head against the wall. I have some friends who work in the xbox division so maybe if I bother them enough they'll have someone make a driver
.So in short (steps one and 2 might not be necessary, try starting at 3 if there is a "+" button available):
1. Remove TB v.12 by deleting pref pane and kext file, restart.
2. Install TB v.11, restart.
3. Open pref pane, click "+" button on left. Choose a controller there, any controller (that you don't own)
4. Plug your controller in, find device and manuf. ID, convert to decimal
5. Download and edit extra controllers file, edit entry for chosen controller(put dev and manuf id in the right place!) Save.
6. Unplug controller, run the extra controllers command file.
7. Plug controller back in. Press the xbox button/wireless connect if needed. Worked for my wireless as well (newest revision)
8. Pray
Last edited:
PowerA Mini Smoke...HELP
Ok, so I have read the whole of the thread, and done all of the steps and trouble shooting, and so far the only thing I've gotten to give me even any level of progress is...
which only makes the controller ring flash like it has power but no connection
However my USB report has gone from this to start, after and during everything prior the last post,
Pro Ex mini for XBOX:
Product ID: 0x531a
Vendor ID: 0x24c6
Version: 1.00
Serial Number: 0000BAF6
Speed: Up to 12 Mb/sec
Manufacturer: BDA
Location ID: 0xfa140000 / 7
Current Available (mA): 500
Current Required (mA): Unknown (Device has not been configured)
To this after tweaking the additional controller script,
Pro Ex mini for XBOX:
Product ID: 0x531a
Vendor ID: 0x24c6
Version: 1.00
Serial Number: 0000BAF6
Speed: Up to 12 Mb/sec
Manufacturer: BDA
Location ID: 0xfa140000 / 7
Current Available (mA): 500
Current Required (mA): 500
MacBook Pro 15 Model A1286 Mid 2010
Processor 2.53 GHz Intel Core i5
Memory 8 GB 1067 MHz DDR3
Software Mac OS X Lion 10.7.5 (11G63)
Trying to use a Power A Pro EX Mini Smoke
Manuf. ID 9414 Model ID 21274
please advise, thank you so much...
Anders
Ok, so I have read the whole of the thread, and done all of the steps and trouble shooting, and so far the only thing I've gotten to give me even any level of progress is...
which only makes the controller ring flash like it has power but no connection
However my USB report has gone from this to start, after and during everything prior the last post,
Pro Ex mini for XBOX:
Product ID: 0x531a
Vendor ID: 0x24c6
Version: 1.00
Serial Number: 0000BAF6
Speed: Up to 12 Mb/sec
Manufacturer: BDA
Location ID: 0xfa140000 / 7
Current Available (mA): 500
Current Required (mA): Unknown (Device has not been configured)
To this after tweaking the additional controller script,
Pro Ex mini for XBOX:
Product ID: 0x531a
Vendor ID: 0x24c6
Version: 1.00
Serial Number: 0000BAF6
Speed: Up to 12 Mb/sec
Manufacturer: BDA
Location ID: 0xfa140000 / 7
Current Available (mA): 500
Current Required (mA): 500
MacBook Pro 15 Model A1286 Mid 2010
Processor 2.53 GHz Intel Core i5
Memory 8 GB 1067 MHz DDR3
Software Mac OS X Lion 10.7.5 (11G63)
Trying to use a Power A Pro EX Mini Smoke
Manuf. ID 9414 Model ID 21274
please advise, thank you so much...
Anders
Last edited:
Just wanted to confirm you did all that from a clean install (no kext file present), Also -->> make sure to put the vendor/product in the right place. I BELIEVE it was opposite as it was in system. Meaning it may go Vendor ID then product ID. For fun, use two different --available-- entries (as shown in the '+ button' list) and put the same numbers in different places in the two different entries, if you're not sure which is which in the file.
Also being sure that the entry that you edited in the list was a controller that already appeared in the pop-up box when you clicked on the + sign to the left of 'no device found'. By 'the right place' above I mean the first instance (in the extra controller list) of the controller name you chose from the ones listed in the '+ button' list.
If you did it all right, I'd say go back to the + sign in the controller pane, look for the next entry that looks available, go straight back to the extra ctrl list, edit the appropriate entry, and just run the file again. Restart for good measure. Also when choosing from the list in the + sign if you can choose a controller that may have some of the same characteristics as your controller, i.e. if you're using a mini one maybe try to find another mini one (just in case that matters).
Otherwise, since these steps got it working on a genuine msft wireless controller from Amazon (and I have gone everywhere and nobody has gotten the newest wireless edition to work), just get one off amazon for $30, keep the packaging and return it if you really can't get it to work. You could do the wired one too but it's the same price and the exact same steps got both working for me. Keep in mind all the other things everyone said on the entire internet got these things working, did not work for me. So I'm hoping all this will work for someone.
Wii Remote Alternative?
This is probably off topic considering the 360 thread title, however pertinent considering the problems.
I've been trying without success to get my 360 controller to work with AC2 as well without success. Mainly because the game only thinks it necessary to give us symbols instead of the actual button letter like any other game (i.e. Press 'kick' instead of Press 'space' or whatever). I desperately want to like this game but every control I don't know feels like a homework assignment; it's like 'press, ok which key does correspond to? Press escape, go to controls, oh, that button, resume game.
Anyway, since the buttons are color coded I figured the 360 controller would make things easier but surprise surprise, no support. I even went so far as to ask Ubisoft if it was possible but they essentially stated that since the game was so old it was unlikely they would put any effort into it and that no controls beyond the mac keyboard and mouse were supported.
So anyhow, I realized this was bs when I was at least able to get the game to respond to inputs from the 360 controller by tweaking my Assassin2.ini file and adding a new input by hand. Read: The program will respond to control pads, but it has no idea what it's doing. I just have to figure out which button is which.
This has been surprisingly easier when on a whim I downloaded the wiimote drivers from WJoy, paired one of my wiimotes (along with a classic controller) and badda bing, badda boom. Assassin's Creed 2 seems to love it. It can't seem to enumerate the buttons worth a crap, but it definitely recognizes them since I can now navigate the game using the Classic Controller's d-pad and ABXY buttons. To see what I mean, check out the included screenshot and code from my Assassin2.ini file (located in ~/Library/Application Support/UBI-MAC-001-WW/)
Not saying this will work for everyone, but it just proves Ubisoft is pathetic at customer support since the game obviously supports controllers with simple additions to the configuration files.
This is probably off topic considering the 360 thread title, however pertinent considering the problems.
I've been trying without success to get my 360 controller to work with AC2 as well without success. Mainly because the game only thinks it necessary to give us symbols instead of the actual button letter like any other game (i.e. Press 'kick' instead of Press 'space' or whatever). I desperately want to like this game but every control I don't know feels like a homework assignment; it's like 'press
, ok which key does correspond to? Press escape, go to controls, oh, that button, resume game. Anyway, since the buttons are color coded I figured the 360 controller would make things easier but surprise surprise, no support. I even went so far as to ask Ubisoft if it was possible but they essentially stated that since the game was so old it was unlikely they would put any effort into it and that no controls beyond the mac keyboard and mouse were supported.
So anyhow, I realized this was bs when I was at least able to get the game to respond to inputs from the 360 controller by tweaking my Assassin2.ini file and adding a new input by hand. Read: The program will respond to control pads, but it has no idea what it's doing. I just have to figure out which button is which.
This has been surprisingly easier when on a whim I downloaded the wiimote drivers from WJoy, paired one of my wiimotes (along with a classic controller) and badda bing, badda boom. Assassin's Creed 2 seems to love it. It can't seem to enumerate the buttons worth a crap, but it definitely recognizes them since I can now navigate the game using the Classic Controller's d-pad and ABXY buttons. To see what I mean, check out the included screenshot and code from my Assassin2.ini file (located in ~/Library/Application Support/UBI-MAC-001-WW/)
Not saying this will work for everyone, but it just proves Ubisoft is pathetic at customer support since the game obviously supports controllers with simple additions to the configuration files.
Code:
[]
VendorID=65535
ProductID=65535
Button1=14
Button2=19
Button3=18
Button4=13
PadUp=0
PadRight=0
PadDown=0
PadLeft=0
Select=0
Start=0
ShoulderLeft1=0
ShoulderLeft2=0
ShoulderRight1=0
ShoulderRight2=0
StickLeft=0
StickRight=0
LeftStickUp=20
LeftStickDown=21
LeftStickLeft=22
LeftStickRight=23
RightStickUp=64
RightStickDown=0
RightStickLeft=0
RightStickRight=0
i am using the 0.11 version of the xbox controller driver from http://tattiebogle.net/ (or http://mice-software.com) and it works fine on the current build of mac os (pre-sea-lion)
I still get a stupid bug that if i plug and unplug the controller a few times it kills all my USB on my Mac Pro
I still get a stupid bug that if i plug and unplug the controller a few times it kills all my USB on my Mac Pro
Sounds like you still have the old drivers installed. I had that a while back (0.08 or 0.09?) but I have not seen it in the latest versions.
Edwin
Snow Leopard problems
What is the best version of the Tattiebogle drivers to use on Snow Leopard 10.6.8? I have tried both 0.11 and 0.12, as well as older versions. 0.11 recognises when I have a controller plugged in, and the Xbox button on the controller lights up at first, but no keypresses are registered. With 0.12, it won't even recognise that I have a controller plugged in (it doesn't appear in the drop-down menu of devices).
I've tried a couple of the other workarounds on this thread, but with no luck (it seems a lot of the advice is for people running Lion).
I'm running a 2008-era 64-bit Intel Core 2 Due MacBook Pro.
What is the best version of the Tattiebogle drivers to use on Snow Leopard 10.6.8? I have tried both 0.11 and 0.12, as well as older versions. 0.11 recognises when I have a controller plugged in, and the Xbox button on the controller lights up at first, but no keypresses are registered. With 0.12, it won't even recognise that I have a controller plugged in (it doesn't appear in the drop-down menu of devices).
I've tried a couple of the other workarounds on this thread, but with no luck (it seems a lot of the advice is for people running Lion).
I'm running a 2008-era 64-bit Intel Core 2 Due MacBook Pro.
I'm using Snow Leopard too and likewise found the 0.12 drivers to do nothing at all. The 0.11 versions have been fine for me, but I had to go through some steps to purge the prior install from my mac...
1. To find out what files have previously been installed, paste this in the terminal:
2. Remove the necessary files which should probably be something like this:
3. Tell you mac to forget about previous installer. I had to use this as the installer repeatedly gave me a message saying that a newer installation already existed...
Paste this in the terminal (you will need to key in your mac admin password at some point):
then:
This worked for me, allowing me to reinstall the 0.11 drivers again. Hope it helps. I'm using a wired 360 controller for what it's worth. It might require a restart after uninstalling too
1. To find out what files have previously been installed, paste this in the terminal:
pkgutil --files com.mice.pkg.Xbox360controller
2. Remove the necessary files which should probably be something like this:
1. /Library/PreferencePanes/Pref360Control.prefPane
2. /Library/StartupItems/360ControlDaemon
3. /System/Library/Extensions/360Controller.kext
4. /System/Library/Extensions/Wireless360Controller.kext
5. /System/Library/Extensions/WirelessGamingReceiver.kext
6. /Library/Application Support/MICE/360Daemon
7. /Library/LaunchDaemons/com.mice.360Daemon.plist
2. /Library/StartupItems/360ControlDaemon
3. /System/Library/Extensions/360Controller.kext
4. /System/Library/Extensions/Wireless360Controller.kext
5. /System/Library/Extensions/WirelessGamingReceiver.kext
6. /Library/Application Support/MICE/360Daemon
7. /Library/LaunchDaemons/com.mice.360Daemon.plist
3. Tell you mac to forget about previous installer. I had to use this as the installer repeatedly gave me a message saying that a newer installation already existed...
Paste this in the terminal (you will need to key in your mac admin password at some point):
sudo su -
then:
pkgutil --forget com.mice.pkg.Xbox360controller
This worked for me, allowing me to reinstall the 0.11 drivers again. Hope it helps. I'm using a wired 360 controller for what it's worth. It might require a restart after uninstalling too
Last edited:
Thanks for the suggestions, Bertrude. I cleared the old installs and did a clean install of 0.11, with restart. I also unchecked all the controllers on the '+' menu except for the standard 'Controller' entry. (I'm using the official X360 wired controller.)
Unfortunately, still no luck. The first quadrant of the Xbox button lights up, but keypresses aren't being detected. And when I take the controller out, it crashes my computer! So annoying.
Thanks again for your advice.
Unfortunately, still no luck. The first quadrant of the Xbox button lights up, but keypresses aren't being detected. And when I take the controller out, it crashes my computer! So annoying.
Thanks again for your advice.
I don't know if it will help in this case, but you might also want to try repairing the permissions on your Hard Disk in Disk Utility and resetting the NVRAM/PRAM (hold down CMD, Alt, P and R as your mac restarts until it re-restarts and you hear the start up tone again).
Keep your setup the way it is. Leave the controller connected and restart with it still plugged in. Your computer will act like it crashed (the way it does when you unplug) but if my hunch is correct, when you load up the pane again after the restart (again, controller still plugged in), it will work. This was my exact problem and this was the only way I got it to work in any fashion. It just means you have to restart every single time you've unplugged the controller.
At a bit of a loss here. I'm using the 0.12 drivers, and I've ran the extra controllers script, but I still can't get it to see my device.
It keeps saying no device found and my controller just flashes green.
It's a normal Gamestop 360 wired controller.
Here's what the USB information says as well.
Gamepad for Xbox 360:
Product ID: 0x0301
Vendor ID: 0x0e6f
Version: 2.00
Serial Number: 000013AC
Speed: Up to 12 Mb/sec
Manufacturer: Performance Designed Products
Location ID: 0x14200000 / 4
Current Available (mA): 500
Current Required (mA): 500
I've tried uninstalling it and using 0.11, but now it says I'm trying to install a driver on a device that has a new version. I used app cleaner to remove 0.12, and it's not in my Systems Preferences anymore. But it seems some of it is still somewhere.
It keeps saying no device found and my controller just flashes green.
It's a normal Gamestop 360 wired controller.
Here's what the USB information says as well.
Gamepad for Xbox 360:
Product ID: 0x0301
Vendor ID: 0x0e6f
Version: 2.00
Serial Number: 000013AC
Speed: Up to 12 Mb/sec
Manufacturer: Performance Designed Products
Location ID: 0x14200000 / 4
Current Available (mA): 500
Current Required (mA): 500
I've tried uninstalling it and using 0.11, but now it says I'm trying to install a driver on a device that has a new version. I used app cleaner to remove 0.12, and it's not in my Systems Preferences anymore. But it seems some of it is still somewhere.
Last edited:
I couldn't get the 0.12 drivers to do anything either.
I also don't think the extra controllers script works with 0.12, as it's for the 0.11 drivers.
I got the same message when trying to install 0.11 after 0.12 but if you follow the steps I outlined 4 posts ago, that should clean whatever remnants are left of the 0.12 drivers, allowing you to have a go with the 0.11 version.
I also don't think the extra controllers script works with 0.12, as it's for the 0.11 drivers.
I got the same message when trying to install 0.11 after 0.12 but if you follow the steps I outlined 4 posts ago, that should clean whatever remnants are left of the 0.12 drivers, allowing you to have a go with the 0.11 version.
Followed all those steps, the only thing I had to do was make it forget about 0.12. Did that, installed 0.11, and then the extra controllers script. Followed by a restart.
Plugged in my controller and I'm still just getting No Device Found, and the green light flashing.
I notice when I click the plus the GameStopGamepad4 is coloured blue, while everything else is black.
Last edited: