Just for testing purposes i did connect it to my Xbox360 and to another Windows PC, just to sadly confirm: this controller is not compatible with OS X El Capitan but runs just fine on Windows or on the Xbox itself. But no matter what i am doing or trying, the controller remains *dead*. I can see the controller in my system summary, no matter what port it's connected to and it even seems to be recognized correctly, as e.g. Kernel: read - failed to handle report: 0xe00002d7 nothing happened: the controller remains unusable.Īfter doing all of this nonsense, i observed my logs and saw this two entries pop-up everytime i connected the controller to the USB port: I also tried with kext-dev-mode on, authorized not properly signed kext. Up until now downloaded all versions of the Github drivers, all of the tattiebogle drivers, uninstalled them, installed them, removed them again, installed them over another. Going further: I googled many pages and did some fiddlings. I downloaded the latest beta (because it mentioned better compatibility with OS X Yosemite), installed it and had to reboot only to see the controller stay unusable. Next step: i found a new driver on Github. Nothing happened, the controller remained unusable. I thought, this could be an expected behavior and launched Steam so test it anyway. It blinked shortly and went off to never light up again. at all! First i did was to simply connect it. So for now i can say: it is not compatible with OS X El Capitan. After new original Xbox 360 controller arrived, the problems began. After going through some hassle of trying to connect a PS3 controller, who never wanted to show up in my Bluetooth Settings, i resigned a bought new wired controller.
After a bit of research and questioning, i've been told that the Xbox 360 controller was best suited for playing games on my Mac.
0 kommentar(er)
