[jiggawatt]

Will do Buzz. I did open a ticket. I’m polishing up a fork and then I’ll submit a pull request for the change.

[jiggawatt]

I’ve discovered the fix is to once again remove the axis limitation bit of code and recompile the source. It was told to have been fixed but the code was put back in with a higher limitation and the false assumption that it fixed the problem.

What seems to be happening is the wireless Bluetooth code causes the controller to utilize more axis that when directly plugged in.

[jiggawatt]

Copying the Binary from my 2.6 image worked. Wireless PS3 functional. There’s something wrong with the new updates to mame4all-pi that is causing the issue.

[jiggawatt]

I think the problem is the hciconfig isn’t staying in an “UP RUNNING PSCAN” mode. If you type hciconfig after you initially pair your controller, what do you seen? If you aren’t seeing PSCAN, you won’t be able to reconnect your controller. I had to fight with this problem. What worked for me was adding a couple lines to /etc/rc.local before ‘exit 0’ to keep the PSCAN up and running

hciconfig hci0 up
hciconfig hci0 piscan

[jiggawatt]

I noticed this issue as well, and I think it has to do with a recent commit/change to the setup script. It’s failing to find the sixpair program. You can accomplish what the setup menu now seems to fail at by manually executing the sixpair program
/opt/retropie/supplementary/ps3controller/sixpair
That will register your PS3 controller to the BT dongle on your Pi. You’ll need to restart (stop/start) the sixad service on your Pi once that’s done. Make sure hciconfig shows “UP RUNNING PSCAN”
Then press the PS button and after a second or two it should register.

Hope that helps.

[Author]

Posts