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!

@mitu said in Keys not working when using physical keyboard in EmulationStation Desktop Edition:

you need is to turn on Game Focus by pressing Scroll Lock

Thanks a lot mitu for your quick and precise answer. I confirm that pressing the Scroll Lock key i see a notification on screen (Game Focus On) and the keyboard full keyset is available!
I guess we can tag this post as solved ;)
And huge thanks as well to have allowed this post

I'm very late on this one but I had the same issue.

It's also been reported in GitHub (https://github.com/RetroFlag/GPiCase2-Script/issues/22) - there's a workaround there that worked for me.

@gruik said in Retropie on Raspberry pi 5 + 5:4 DVI Black Screen:

Now that I read it again, I feel dumb because it's called "legacy" and explicitly says that the hdmi filter is for the pi 4 only...

Yes, and in this context 'legacy' means every Pi model with recent RaspiOS (Bullseye or up), not just the Pi4.

We don't support 3rd party images - you'll have to ask Waveshare for an updated Pi4 image that supports newer board revisions.

@mitu Great, thanks!

@ploinkploink

On my RetroPie system, this error was due tu a wrong kernel. And the wrong kernel was due to an upgrade to Debian 11 (which I should never have done) and downgrade to Debian 10.

apt install --reinstall raspberrypi-bootloader raspberrypi-kernel
and reboot solved the issue.

@ime01 said in Could someone upload Mame Set Rebuilder? :( - New User Request.:

Hello, may I ask where I can download a tool called - MAME Set Rebuilder? - legit of course.
There is a link to a forum that one cannot use because I do not speak Italian. :)

Use Google Translate or chatGPT, no upload on external forum, register to retropie-italia.it

@ime01 said in Could someone upload Mame Set Rebuilder? :( - New User Request.:

I tried the mame old developer sites but it was not there nor, accessible.

The original website is retropie-italia.it

@quicksilver any time I make the change to "trivial" or anything else for that matter, it gets changed right back when I restart emulation station. Anyone know why?

@Rens I think you're asking what parameters are passed to the onstart/onend scripts. It is just the four mentioned in the docs: $1 = system, $2 = emulator, $3 = rom path and $4 = command

https://retropie.org.uk/docs/Runcommand/#runcommand-scripts

Useful data are passed as arguments to these scripts:

$1 - the system (eg: atari2600, nes, snes, megadrive, fba, etc). $2 - the emulator (eg: lr-stella, lr-fceumm, lr-picodrive, pifba, etc). $3 - the full path to the rom file. $4 - the full command line used to launch the emulator.

You can see here, for example, the runcommand-onstart.sh and others are called with the user_script function:

user_script "runcommand-onstart.sh"

The function:

https://github.com/RetroPie/RetroPie-Setup/blob/cdb2bda29fab4cae57ca5bf283f87620ab4be851/scriptmodules/supplementary/runcommand/runcommand.sh#L1300

# calls script with parameters SYSTEM, EMULATOR, ROM, and commandline function user_script() { local script="$CONFIGDIR/all/$1" if [[ -f "$script" ]]; then bash "$script" "$SYSTEM" "$EMULATOR" "$ROM" "$COMMAND" </dev/tty 2>>"$LOG" fi }

The meat is here:

bash "$script" "$SYSTEM" "$EMULATOR" "$ROM" "$COMMAND" </dev/tty 2>>"$LOG"

As you can see, only the four parameters "$SYSTEM" "$EMULATOR" "$ROM" "$COMMAND" are passed to $script

@Jimmy14 Getting off-topic here but as a starter:

You may want to use something like the PAM8302 and then use audremap in the config.txt

I have not been down that road but the information in the refenced pages should get you started.

Feel free to start a new thread here, but I assume in the Raspberry Pi forums you will have more guys which may have dealt with it already.

Are you using the Libretro core of pcsx_rearmed or the standalone emulator ? Is your RetroPie installation updated ? How did you install RetroPie and which image did you use ?

Please add the make/model of your controller, 8bitdo have a lot of controller models.

Thank you Mitu