Forum Replies Created
- dannysmith43Participant04/17/2015 at 14:23Post count: 6
Thanks for the replies on this, I’m only using 2.6 so it was a different issue. Found out the what the problem was last night…POWER! The 2A Samsung Note 4 charger was fine but the cable I was using (not the original Note 4 one) was not! Soon as I swapped over the cable, stable bluetooth PS3 goodness.
I need to rebuild it from scratch tonight as SSH is constantly up and down, which is driving me nuts but I’ve tried so many tweaks to get the pad working, I’ll probably screwed something else.
Thanks again!dannysmith43Participant04/14/2015 at 22:45Post count: 6
Hey, I’m thinking about getting a 2.4Ghz wireless usb gamepad, will they all work the same?
I’m looking at this one
any one else have this model?
thanksdannysmith43Participant04/14/2015 at 22:44Post count: 6
Hi, I have the same problem
Configure ps3 controller it is difficult because it detects motion controller.
Sorry for my English
I have the same issue also. What do you mean by “it detects motion controller”?
When I try to register my PS3 pad in Emulationstation it goes crazy, detects phantom inputs and not the correct keys, only over bluetooth. Same issue for you?dannysmith43Participant04/14/2015 at 22:11Post count: 6
[quote=94473]You could help test the updated PS3 controller driver module. Update RetroPie-Setup and select “PS3 driver install”.
After installation you can plug in your controller every time. Pairing will be done automatically. No manual six pair and so on.
In emulationstation press F4 at least two times to reach command line.
sudo git pull
sudo ./retropie_packages.sh ps3controller
Ok. As written above your controller will be paired if there is a bluetooth dongle and a ps3 controller connected. It is necessary “atm” to run retroarchinput for every ps3 controller because sixad adds the mac address of every ps3 controller to the device name. Retroarch does not know these device names and VID/PID detection seems to be not broken. Had no time to evaluate why retroarch does not use given VID/PIDs.
sudo ./retropie_packages.sh retroarchinput
After reboot your controller should always connect.
I managed to give this a try today, it seems to work better in terms of it pairs after each boot of the Pi, which is great. Unfortunately I still get the problem with the controller not registering correctly. This seems to happen in Retroarch, Emulationstation and using jstest. I think it’s the analogue that goes crazy, it randomly registers phantom movements before I can set my own key. I’m using a standard dual shock ps3 controller (CECHZC2J), barely customised version of Retropie and the “standard” bluetooth dongle (CSR 8510 A10). I can’t believe that I’m the only person having this problem with a ps3 pad?!dannysmith43Participant04/11/2015 at 22:27Post count: 6