@SpudsMcToole there are warnings all over to back up your builds! Also, where are you storing all of these? There are certain folders that get overridden during updates. There are other folders like .emulationststion that do not. You should follow tutorials and save you custom work in folders that do not get overridden.

@edmaul69 I was actually able to get it to work. I tried a different ps3controller option, Shanwan Clone, and both controllers immediately connected. Problem solved, hooray!

edit: This also seems to have solved my Bluetooth reconnect issues as well. If anybody else is having the issues that I was, I suggest trying a few of the other ps3bluetooth driver options.

Problem solved here. What I had to do was unplug the keyboard dongle and reboot, then pair the joypads one at a time. With that done, putting the keyboard dongle back in didn't seem to conflict any more and everything's fine.

I'm having the same kind of issue, except I still haven't found a way to figure it out ... Posted it as an original topic here, but no one came to my rescue :(

https://retropie.org.uk/forum/topic/10289/psx-multitap-port-2

@Awsomepie that's always the worst. Those are the times where I wish I had a visual savestate where it takes a screenshot of where I'm at in the game like on pajama Sam. I guess there are always cheat codes...

@edmaul69 Thanks for your help, I will give it a try :)

What do you want to do with that arduino?
Retropie is built for the raspberry pi, not an arduino.

@edmaul69 Awesome. Thanks I'll try that.

@mediamogul

I redid the setup of kodi as a standalone system per (https://github.com/retropie/retropie-setup/wiki/KODI) again and that worked!

thanks for your help!

@RetroHopeful Not at all. That file only has the settings for the latest controller you configured, no worries :)

It effectively suggests that select is being mapped as the hotkey - which is a good sign!

I'd expect you'd be able to exit a game by pressing the keys you mapped to select and start, together, on the keyboard. And, as you redefine your other controllers, I'd expect you to be able to do the same for each as that happens.

Still, I'm puzzled/concerned with that error message you keep getting - that clearly suggests something is wrong with your current setup.

At this stage, if it isn't too much trouble, I'd strongly suggest formatting your SD card (or trying out a new one), reinstalling the image, and seeing how that goes.

@Yamt that appears to be a waveshare clone and should follow the waveshare 32b guide.

@paulmdickey no problem. glad to help.

The USB port on the Wii U pro controller is just a charging port and doesn't do data. If you want to connect to the Pi via bluetooth you'll have to go into the bluetooth settings of the RetroPie. While you can get this to work, I highly suggest you get a PC wireless controller adapter. I tried hooking my Wii U controller to the Pi's bluetooth and it worked at first. But very soon I started experiencing ghosting to the point I couldn't even play the games. Using the adapter, I synced it very easily to my controller and Emulation Station recognized the controller very easily.

@cerealspiller great! Glad it worked for you and thank you for the update!

I know for my Wii U controller, I couldn't get RetroArch hotkey shortcuts to work as I wanted until I went into the config file and manually added the start button as the "exit" button. But it took me awhile at first to understand how the hotkeys worked (didn't know what hotkey option meant when I set up the controller in emulation station because it didn't do that in my Reys image).

Hi @herb_fargus

Thanks for the reply

Tried that and it worked, but it was left orientated and i couldn't find any way to change the viewport. And it reset on restart.

Kind Regards
Toke

Update: Installed the newest firmware for the controllers (4.0), whereas apparently I was previously on 2.65 or something like that.

One controller works and the bug even seems to be fixed.

The other controller now won't connect to Retropie at all.

Edit: Took me like an hour of fiddling but both controllers now connect properly and the save state bug is gone! Had a devil of a time getting Retropie to let me register and connect both pads at once for some reason.

Thanks for the suggestion to update the firmware, I had completely forgotten that I had done it when I first got the pads and I honestly wouldn't have thought a small Hong Kong company like 8BitDo would keep working on new firmware updates for so long - pleasantly surprised to be wrong. At least in the end the fix turned out to be relatively simple!

@cyperghost In terms of speed, you won't notice the differences on a pi3, but a non-oc'd pi2, mame2003 got slowdowns and fba did not. I use lr-fbalpha for both my pi2 and pi3. As it was already pointed out, you need a different romset for lr-fbalpha. Mame2003 and fba2012's cps2 romsets will NOT work in lr-fbalpha. There was a change in the roms where it requires key files to decrypt the games now. More info on what version of romsets each emu requires https://github.com/retropie/retropie-setup/wiki/FinalBurn-Alpha