I have completed the emulator finder. For those interested in using, see: https://gist.github.com/Langerz82/ec7c60edd6b02da78018fa113fda27b0

Hey just a note: The video output will most likely corrupt and show random pixels, this is normal operation and due to sending the emulator process in the background.

All the best!

@ronbo85 said in Control Panel Layout images:

In bash scripting, how do I get iterative values? (load 'em into arrays?)

Yes, you can use arrrays.

And when it comes to single elements (miscDetails) vs. multiple (button labels), would I need individual XMLStarlet calls? (it's a nice, and compact language, but I'm having a hard time wrapping my head around how best to code it).

My example shows everything in one call, but you can run separate commands if you want to get different values without parsing the output.
For instance, to get the contents of the miscDetails node:

xmlstarlet sel -t -m '//game[@romname="roundup"]/miscDetails' -v "text()" control.xml

If you want to get the how many buttons player1 has :

xmlstarlet sel -t -m '//game[@romname="roundup"]/player[@number="1"]' -v "@numButtons" -n control.xml

Thanks, that seems to get rid of that console error. Now the games just hang, will do some more troubleshooting :D

Solved?

The problem was that the pi4 has 2 "connected" outputs (given by xrandrs output), this means that the MODE_CUR array is increased by one (HDMI-1 HDMI-2), and MODE_CUR[5] becomes aspect ratio instead of being the refresh rate, my solution basically looks for /primary/ instead of /connected/... but no clue if that will mess things up for others.

runcommand.sh
runcommand.sh.diff

In 2.0.10, it looks like a hint was added (SDL_HINT_GAMECONTROLLERCONFIG_FILE) to point to a user chosen 'gamesdbcontroller.txt' file. It looks like PPSSPP doesn't use this mechanism to load the file, but it might affect how SDL2 works when the game controller API is initialized by the emulator.

I'll see if a recent source build for PPSSPP triggers this on a RPi, it could also be something that's changed in the emulator since the last binary build in RetroPie.

@BuZz editing /opt/retropie/configs/all/runcommand.cfg did the trick, thankyou! :-)