oh hang on, you're using lr-mupen64plus, so that input file is redundant, as it uses retroarch configs.

in which case, you can have a look at the core options to see if there's anything relevant: https://retropie.org.uk/docs/RetroArch-Core-Options/

or core input remapping to rebind it completely: https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping

however for pi4, i wouldn't recommend using lr-mupen64plus at all - it has a lot of issues and is out of date. instead use mupen64plus-gliden64 with this fix: https://www.reddit.com/r/RetroPie/comments/gc83sc/n64_mupen64plusgliden64_performance_fix/

@everett115 please fill out https://retropie.org.uk/forum/topic/3/read-this-first

@BobRossWins https://www.reddit.com/r/RetroArch/comments/c9csnr/game_latency_frames_wiki_runahead_wiki/

Might sound silly but have you opened it up to see if the microswitches aren't pressed firmly?

@BuZz Hehe ... August 2016 - I can remember this ;)

Probably SDL2 doesn't support the controller correctly. But for EmulationStation that shouldn't be an issue - the buttons you have should be enough to navigate and operate EmulationStation.

I don't remember getting this message with reicast. Does it show when you're launching the game ? Usually, if the ROM/disc image is not correct, you're returned to the game list. Did you try to launch the same game with flycast ?

Thank you!

I have also discovered that moving all the ROMS from /arcade/ to /mame-advance/ did the trick it seems too.

Thanks again!

@BobRossWins I have that controller and had the same problem. It seems that Retropie is looking at the L2/R2 triggers as axis instead of buttons. I'm not able to get to my Pi right now so I can't give you the complete path but you can force the assignment by editing the cfg file, with the information in the last post here: https://retropie.org.uk/forum/topic/27253/8bitdo-sn30-pro-wired-trigger-assignment

That worked for me. Something odd that I haven't had the chance yet to investigate: I did a full update with the paddle plugged in and it was then registering L2/R2 as buttons and then I was able to assign them through the GUI.

I hope this helps, I'll be able to be at my Pi tomorrow to add the path to the cfg file I edited, (it's in configs/all I just don't remember the rest).

Ver 2.0
Replace lipo with a anker 20000mah powerbank.
Added usbc port to charge both the abker and the piboy 1up, and also an extra external usb socket (anker powerbank has 2 outputs) to charge my phone or the Pi controller.
Cheers
PSX_20200808_153113.jpg
PSX_20200808_153124.jpg
PSX_20200808_153135.jpg

@WeirdH I fixed that issue by using brackets around the code.

If the controllers are wireless then they probably go to sleep and don't send any button presses to the Pi. If the Pi goes to sleep the controllers won't wake it up.