[redfarmer]

Off.

[redfarmer]

I love this project! Any updates? Are you still working on it?

[redfarmer]

Great advice! I’ve been there, manually trying to edit these XML-files and it takes forever. This will probably help speeding things up.

Thanks.

[redfarmer]

Use WinSCP for example and connect to the IP-adress of your pi. User/pass is pi/raspberry. Through samba you can only see a few chosen paths.

[redfarmer]

Like mentioned earlier. Use the sselph scraper. Very fast, and if you use the thumnail option the images will take very little space.

scraper -thumb_only

This may help:

[redfarmer]

It took a while before i had time to try your suggestion but it worked great!

What i did was:

1. pi@retropie ~ $ sudo service sixad stop
2. Paired my bluetooth keyboard
3. pi@retropie ~ $ sudo service sixad start

After this i just connected the PS3 controller and had both working simultaneously. It would be nice to be able to use both the controller and keyboard in emustation aswell as the RetroPie setup but not a big deal.

Many thanks!

[redfarmer]

I don’t have much to add but just wanted to mention that i owned a Vectrex many years ago and Minestorm was indeed built into the machine. I remember when starting my console without a cartridge it defaulted to Minestorm so i guess the emulator kind of does the same thing, it can’t load/find the ROM and assumes you have no cartridge. Maybe you should try downloading a new set of ROM’s.

[redfarmer]

Same prob if running the command with sudo?

[redfarmer]

Thank you! Does that mean i can stop the sixad service, pair the keyboard, start the service and have both working or does it mean i can’t use them together at all?

How do i start the service again? ‘sudo service sixad start’ or maybe reboot?

[redfarmer]

Bump :)

Can anyone share how they paired their bluetooth keyboard? I’ve seen some manual guides floating around (not RetroPie specific but for Rapsberry in general) but they all differ and i’m afraid to screw up my otherwise working setup.

Thanks.

[redfarmer]

Cool! Everything solved :)

[redfarmer]

[quote=110386] @redfarmer
If you connect at runtime sixpair runs without user interaction. Sixpair configures your controller. This takes one second. After this second your controller should be ready for pairing. Remove USB cable and press PS button.

As i said if your controller is configured it is not necessary to connect over usb and run sixpair again. Configuration persists.

[/quote]

Yes, it is already configured so now it connects without issues (i’m not using the cable anymore).

But, does it mean that when configuring a new controller i don’t actually have to go into the RetroPie setup and choose the PS3 pairing option? I can just do it outside the setup, from EmulationStation ie?

Thanks.

[redfarmer]

[quote=110359]@all of you
Was the controller connected at boot up? sixpair runs if you connect your controller “at runtime” (in emulationstaion for example) and the controller should be instantly ready afterwards. If your controller is connected at boot time sixpair does not run.

Sixpair is necessary to write the mac address of your bt dongle to the controller once. The controller should always pair afterwards.

[/quote]

Ok. I’m almost certain i tried both (connected via USB both before and after boot) but still got the error. At least i’m 100% i had it connected during boot several times.

However, i’m not sure i fully understand. You mean that the PS3-controller should always be connected over USB during runtime prior the pairing process rather than having it connected during boot?

[redfarmer]

[quote=110301]Never mind. Redfarmer was correct. Adding another controller and using the PS3 controller as the “player 2” controller somehow allowed it to connect via bluetooth.

Once it paired as “player 2”, I just unplugged the other controller and rebooted.

At that point, I was able to pair correctly as “player 1” with the PS3 controller via bluetooth

Thanks so much for the fix!!!!! I’m about 8 hours into this search.

[/quote]

Glad i could be of help.

[quote=110337] @pizzafaceassn

I had to temporarily remove my wifi dongle to make room for a second controller during the end of the process.

In order to keep the Internet connection, I used a hard wired Ethernet cable.

So in addition to the Ethernet cable, I had:
1. A Logitech wired controller
2. Keyboard
3. Bluetooth dongle
4. PS3 controller wired with USB

I then ran “lsusb” and verified that the PS3 pad was lower on the list of USB devices than the other controller. (I don’t know if that’s actually necessary. I’m just guessing. I’m a beginner at coding)

Next I ran “install/pair PS3 controller” from the setup menu.

The response was exactly the same. So no change there.

Then I just rebooted into game mode. Once everything loaded, I disconnected the PS3 controller from its wired connection and pressed the “PS3” button.

At that point, it paired as player 2.

Then I removed the Logitech controller and rebooted again.

Finally, the PS3 pad paired as player 1

[/quote]

My method was really straightforward. I just connected my first controller and then the PS3-controller and it was automatically the second device. Then started the pairing process. After it was paired i pulled the first wired controller and rebooted just as you mentioned and then it paired as first device.

I do think this should be treated as a bug.

[redfarmer]

Problem is solved!

I first connected a cabled XBox360 controller that made my PS3 controller the “second” device. So when the RetroPie setup wanted me to connect it over USB and then unplug to pair i did not get the error in the screenshot above.

By curiosity i removed the XBox360 controller during the pairing process and the error appeared.

I think the RetroPie setup gets “confused” when the main controller is removed, even in the pairing process. This is why i couldn’t pair when the PS3-controller was the only active controller connected over USB.

[redfarmer]

I’m starting to believe in wizardry because the problem has gone away for me (knock on wood). I honestly can’t remember if the problem was in v3.2 or 3.2.1 but it works now. About the difficulties pressing start in NES-games i usually just needed some patience because waiting for 30sec or so after starting the game usually let me press start. Very strange…

[redfarmer]

Good job! So simple but still frustrating when i couldn’t figure out what was wrong. A fix would be nice.

[redfarmer]

[quote=109838] @redfarmer
What happens if you uninstall joy2key?

[/quote]

I’m actually not really sure how to do that and what effect it would have. Won’t it stop me from using controllers in EmulationStation? How would i get it back?

Thanks.

[redfarmer]

That explains why i could play Smithereens with my brother but unable to play for example Satellite Attack :)

[redfarmer]

I don’t have a solution but just wanted to say that i am experiencing both these issues myself.

[redfarmer]

>>Slayer
Tried pressing the PS button after reboot when in EmulationStation but no go.

>>miahotrod
Interesting. Bug introduced in newer RetroPie?

Is anyone else successfully using PS3-controllers in RetroPie 3.2 or 3.2.1?

This is what it looks like the same instance as i disconnect the USB cable from the controller (rightclick and chose View image to zoom):

[redfarmer]

Thanks for replying!

Yes, they’re genuine. I’ve tried with 2 controllers and one of them was even bundled with my PS3.

[Author]

Posts