Forum Replies Created
kornbabyParticipant03/28/2015 at 06:11Post count: 6
[quote=92844]I’m having some issues with the controllers.
I do the retroarch config like usual, but the retroarch.cfg remains unchanged. Could be something about permissions, will check that later.
SNES controllers are all messed up.
So far I’ve liked the changes made. I’ll just have to try each of the emulators and options to find the most optimal one for each system.
please let me know if you figure this out. I’m also having the issue where I put my custom configs in the retroarch.cfg file for each respective emulator and it seems to ignore that and just read the one thats in the “all” folder.kornbabyParticipant03/16/2015 at 03:14Post count: 6
A follow up to this question… What am I losing by running the 2.6.0 rp1 image on my raspberry PI 2 vs running the 2.6.0 rp2 image that is not going to work with my PS3 controllerskornbabyParticipant03/15/2015 at 15:01Post count: 6
Please ignore this question. I posted the same question twice. ThankskornbabyParticipant02/16/2015 at 20:39Post count: 6
[quote=87380]I have come up with a very easy way to fix the multiple PS3 controller connecting issue.
It turns out the mode PISCAN which turns on ISCAN and PSCAN at the same time for the bluetooth fixes the issue. The command to manually do this is
“sudo hcitool hci0 piscan”
This will let both controllers connect perfectly. So the easy fix I did was just above the Exit 0 in the /etc/rc.local file I added a line that reads:
“hcitool hci0 piscan”
So when the PI boots it enables that mode automatically with a nice simple command.
The other thing I have noticed is that for some reason when you first copy the 2.5 image to your card and boot it your bluetooth adapter is in the state down. This is easily fixed with
“sudo hciconfig hci0 up”
Once you do this a single time there is a line in the /etc/blueooth/main.conf that tells your PI to remember the last manual state set on the adapter so it will be automatically up the next time you boot it.
As for the controller not detected screen if you do not get the controllers paired fast enough the quick and dirty work around is to add a sleep 10 or so timer so there is a delay, you could also echo something like “press the PS button now to pair your controllers” which would make this make a little more sense.
I would love to find a way to get rid of that splash page all together but I may be ok at bashing my way through issues with the help of Google and a little smarts but I am not a code monkey so I that is better left to the real smart people. Maybe an option?
By the way do any of the core developers read these so they can implement these things into a bug fix? Now it will be straight forward now that we have figured it out.
For me the hcitool hci0 command would not work. I did have success adding hciconfig hci0 piscan.
I was wondering if anyone has been able to get the PS3 controller to work with pisnes. The pisnes emulator does not seem to recognize the PS3 controller at all.