@mikejkelley turns out it was an xbox controller firmware needing update issue.

I can't reproduce this with exFAT using a Pi3 (which is the same platform as the Pi Zero 2w). I have an up-to-date RetroPie system created from the RP Pi3 image and updated regularly.

Starting with an empty drive and adding the retropie folder to it, the synchronization of the folder by the usbmount service preserves the case for all folders - the folders under roms are all lower case, the only uppercase folder is the BIOS folder and that's outside the roms folder.

Ok, also thanks for your help, but I think I'm just gonna reinstall it without the desktop environment

@mitu that fixed the problem and now it’s fully built, thank you

@pindapoe

I had something similar to this and I had -x and -y arguments in the .commands file that was restricting the size of the video window. Take them out. But yeah, Hypseus all the way....

Whoohoo!

I got it back running once again!

It gave me much joy to see that the save file from the Final Fantasy game I've been playing on handheld showed up as available on my Pi!

I even said in my best hacker voice, "I'm in...." lol

At least I took excellent notes this time around in case another update is ever needed. :)

@Lolonois Tried apt list --installed | grep ^alsa but gave me a "command not found" error

emulationstation.jpg

I had to configure Audio Device to that way to make it work in Pi 5, maybe that is the problem with linapple?

You could try enabling manual texture sampling but make sure to use opemGl or else it wont work. That's how i solved it for resident evil 4 and MKDD

How is this related to RetroPie ? If your only usage of the Pi is for Kodi, then I'd recommend you install a Kodi distribution like LibreElec.

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

Does this provide any clues?

Not really, the Joy2key keyboard messages are ok since they're associated with the runcommand menu and the joy2key utility. However, the fact that there are no disconnects for your physical gamepads means their connection is fine - it's what the dmesg command was used for.

@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.