Now the issue is that when I try to configure my xbox controller, a hundred pop-up boxes appear alternating between "connected" and "disconnected."

@nixzero said in How to save controller configurations to IMG backup?:

One thing worth mentioniing is that whenever I would configure the gamepad in ES (back when it was working), the gamepad would always have some random number. "GAMEPAD 20" or "GAMEPAD 5". I thought it was strange that it didn't always say 1 or 2 since I only have 2 controllers connected, and if it's creating profiles it appears to be numbering them randomly.

The numbering is not random and it starts from 1, but if the controller disconnects and re-connects the number is increased. This means that the controller(s) are disconnecting from your Pi for some reason and this might explain why they're not working correctly.

The fact that RetroArch finds the configuration (the messages "Honey Bee Quasi Con controller is configured in port 1/2" indicates that) means the configuration files are ok.

You should check by running dmesg -w from a SSH session, while the emulators are loading/runing, if the gamepads are disconnecting from the USB port when you start the emulator and/or when working in EmulationStation.

@jmcdra said in If one were to install mednafen on retropie...:

I'm also noticing this input delay on RetroArch too

You should have started from there instead of making it look like a mednafen issue. In the first place, i can hardly make sense of using mednafen standalone to play nes games on rpi4, there are plenty of better options afaik.

Retroarch has the P+K method to measure input lag, and in my experience the nes cores usually have 0 frames of input lag (i.e. the game reacts at the frame right after pressing a button), there might be exceptions but i doubt it ever goes beyond 1 frame.

If you are experiencing huge input lag on nes emulation, then i can only suppose something unrelated to emulation is at work here, like display lag or something about your controllers.

Please ignore, I did what seemed most simple and plucked the functions I needed from the script and that seems to work.

#! /bin/bash function enable_plymouth_theme() { if [[ -z "$1" ]]; then echo "--------------------------------------------------------------------------------" echo "| Skipping Plymouth boot splash because no theme name was provided" echo "--------------------------------------------------------------------------------" echo -e "Skipped\n\n" return 255 fi PLYMOUTH_THEME=$1 echo "--------------------------------------------------------------------------------" echo "| Installing Plymouth boot splash and enabling theme '$PLYMOUTH_THEME'" echo "--------------------------------------------------------------------------------" apt-get install -y $APT_RECOMMENDS plymouth plymouth-themes plymouth-x11 rm -rf /tmp/plymouth-themes git clone --depth=1 https://github.com/HerbFargus/plymouth-themes.git /tmp/plymouth-themes mv /tmp/plymouth-themes/* /usr/share/plymouth/themes/ update-alternatives --install /usr/share/plymouth/themes/default.plymouth default.plymouth /usr/share/plymouth/themes/$PLYMOUTH_THEME/$PLYMOUTH_THEME.plymouth 10 update-alternatives --set default.plymouth /usr/share/plymouth/themes/$PLYMOUTH_THEME/$PLYMOUTH_THEME.plymouth update-initramfs -u echo -e "FINISHED enable_plymouth_theme \n\n" sleep 2 } # Hide Boot Messages function hide_boot_messages() { echo "--------------------------------------------------------------------------------" echo "| Hiding boot messages" echo "--------------------------------------------------------------------------------" # Hide kernel messages and blinking cursor via GRUB sed -i 's/GRUB_CMDLINE_LINUX_DEFAULT=".*"/GRUB_CMDLINE_LINUX_DEFAULT="quiet splash vt.global_cursor_default=0"/g' /etc/default/grub update-grub # Hide fsck messages after Plymouth splash echo 'FRAMEBUFFER=y' > /etc/initramfs-tools/conf.d/splash update-initramfs -u # Remove cloud-init to suppress its boot messages apt-get purge cloud-init -y rm -rf /etc/cloud/ /var/lib/cloud/ # Disable motd touch $USER_HOME/.hushlogin chown $USER:$USER $USER_HOME/.hushlogin echo -e "FINISHED hide_boot_messages \n\n" sleep 2 } enable_plymouth_theme "retropie-pacman" # See https://github.com/HerbFargus/plymouth-themes.git for other theme names hide_boot_messages

Hm, seems like the the hid_nintendo driver has some issues with the 8Bitdo pretending to be a Switch Pro Controller. Thanks for the investigatio and write-up.

Generally, users use the XInput mode for 8Bitdo Pro(s) and use the hid_xpadneo driver, probably that's why there haven't been so many reports similar to yours.

@mitu It doesnt work, but I went back to the start, and restored my working backup image (4.8), copied apart ScummVM folder in \opt\emulators, updated everything to 4.8.9, and restored the ScummVM old folder containing ScummVM 2.6 and it works with all the rest updated :)

The problem is with ScummVM 2.9 on Pi 3.

@retropieuser555 I'm baaaack lol

Ok, so updating my retropie didn't help with the save game issues. My son was playing some Kirby games, and they were getting erased every day he logged in.

So, I finally found "resetromdirs" and did it! However, now I have this ...Error after using ResetRomDirs

Although there's a command line, I can't seem to type anything using the controllers. Any help would be appreciated, thank you!

@Rooo7223 said in Retropie games aren't showing...:

there was absolutely no games preloaded.

Yes, that's correct and this is how the image works. There are no games included with the image and you need to add your own games to it in order to play games.

and try to fix it but I really going to do anything. if you do know how to fix this please comment. but i don't feel like going on a emulator website and downloading all the game.

This is explained in the docs -https://retropie.org.uk/docs/First-Installation/ and https://retropie.org.uk/docs/Transferring-Roms/.

@raspberry79
this is as close as we have at this time.
https://retropie.org.uk/forum/topic/36629/unofficial-rpi5-retropie-image/47?_=1747403447694

The fixed libsdl2 package in Ubuntu has been released a couple of week ago, after the bug/regression has been reported last year. If you have used the workaround of installing the RetroPie's SDL2 package, you can now un-pin the package and use the distro's package instead.

Changelog at https://changelogs.ubuntu.com/changelogs/pool/main/libs/libsdl2/libsdl2_2.30.0+dfsg-1ubuntu3.1/changelog. Even though the fix was added in Jan 2025, the updated package was added to the updates repositories on 29 Apr 2025.

@Azuli said in Streets of Rage Remake 5.2 on Retropie 4.8.8 Issue:

@ExarKunIv if you mean the "SoRR2" option on retropie extra, it is asking for "libpng12", which I couldn't yet find a way to install on bookworm.

No, they mean lr-bennugd.

@mitu
... DraStic doesn't like HDMI1 audio output, only HDMI0 and MAYBE headphone jack. Noted.

For anyone running into this and having issues for... Not paying attention to details for whatever reason. (ADD in my case)

1: ES_SYSTEMS.CFG was not in the opt folder for me, but it is recommended to have it there anyway for alterations, so make a copy of it there.

sudo cp /etc/emulationstation/es_systems.cfg /opt/retropie/configs/all/emulationstation/es_systems.cfg

2: the <pi> in the code above is the user name/folder. in my case, the folder is called "retropie" - maybe because it's a custom installation. I needed to change things as follows:

<system> <name>pico8</name> <fullname>PICO-8</fullname> <path>/home/retropie/pico-8</path> <extension>.sh .p8 .png .SH .P8 .PNG</extension> <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 "/home/retropie/pico-8/pico8_dyn -run %ROM%"</command> <platform>pico8</platform> <theme>pico8</theme> </system>

I also was not able to install wiringpi, but the gamepad worked anyway. I wasn't able to exit it via gamepad yet, but I've been very away from retropie, so I might just be missing something. (also I was using a gamepad/mini keyboard combo, so it wasn't an issue yet.)

@mitu
After figuring out I shouldn't be using the 64bit version for this, I got the screen working with sound. Now it's just the usual gambling of installing stuff that's not just roms and emulators in retropie. :v

Thanks!

@mitu Gotcha. Well, I'm glad it was able to resolve itself either way. I'll keep my discussion to this issue on Folly and DTEAM's thread. I appreciate the help and insight, Mitu. Thank you!