Runcommand launch images automatically chosen for ROM-specific emulatorchoices

EctoOne

I have no idea of coding either but i would go for something simple like this:

show /path-to-images/$2-launching.png

well, you have to replace the actual command of course.

EctoOne

I was thinking about this, and it always kinda bothered me that the launching images are scattered around in subfolders on the SD card and won't even be moved by the usbmount service. I wish we could have a dedicated launchimagefolder like we have the splashscreen folder already. This then could (maybe?) work when on a USB Stick, and it would be easier to share custom launching image sets.
And in addition to the OPs request, and I myself could see the need now after installing some Ports, the script could look like this:

if exists /path/$2-launch.png // Checks if an image for a specific emulator exists
    show /path/$2-launch.png
else if exists /path/$1-launch.png // Checks for an image for a specific system
   show /path/$1-launch.png
else
 do nothing

cyperghost

@AndersHP

This snipplet extracts all relevating info out of $3

#!/bin/bash
romfile=$1
#romfile="/home/pi/RetroPie/roms/arcade/mygame.zip"
romname=${romfile##/*/}
echo $romname
rompath=${romfile%/*.*}/
echo $rompath
romroot=${rompath%/*/}/
echo $romroot

You will optain the name of the rom, the path to it and the rootdirectory of your rom location.

Now you need a case selection as @meleu wrote out of the called emulator you obtain with $2

system=$2
case "$system" in
    "pifba"|"lr-fba") system="fba" ;;
    "mame2003"|"mame2010") system="mame" ;;
esac

Now rebuild path were your image is located. But now you have your toolkit and you can try to write a working script with a symlink pointing to your launch image.

meleu

I was at work, on my night shift. Everything was calm and I was fighting agains the mythological Morpheus when I looked at the computer and glanced the bash prompt...

Here is the result: https://github.com/meleu/share/blob/master/system_specific_arcade_launching_images.sh

To download it to your RetroPie:

wget https://raw.githubusercontent.com/meleu/share/master/system_specific_arcade_launching_images.sh

After downloading do the following:

cat system_specific_arcade_launching_images.sh >> /opt/retropie/configs/all/runcommand-onstart.sh

WARNING! WARNING! WARNING

I made some quick tests on an environment that only mimic a RetroPie system but didn't test on an actual RetroPie (you didn't think I had an actual RetroPie system at work, did you?). That being said, don't blame me if sh!t happens. ;)

Cheers!

AndersHP

@meleu That's great, thanks! Will try it out! :)

hiulit

@meleu Nice! You are so quick coding stuff!!! ;)

cyperghost

@meleu said in Runcommand launch images automatically chosen for ROM-specific emulatorchoices:

mythological Morpheus

Would you take the blue pill or the red one NEOleu?

meleu

compliments

Any One Piece fan here? :)

I would like to know if it works for what you want @AndersHP

Have a nice day fellows!

AndersHP

Hmm.. nothing shows, just the run command menu. Tried copying one of my launching images to the arcade config folder, and that showed fine.

Could it be because my roms are run from USB?

meleu

@andershp please, give me the output of these commands (paste on http://dumptext.com/):

ls -l /opt/retropie/configs/mame/launching.*
ls -l /opt/retropie/configs/fba/launching.*
ls -l /home/pi/RetroPie/roms/arcade/images/

And just for checking:

cat /opt/retropie/configs/all/runcommand-onstart.sh

AndersHP

There's no folder called "mame". It's either mame-advmame og mame-libretro.
Sorry, this is probably me not being specific enough. The 3 types in my arcade folder is fba, mame2003 and advmame.

the fba related line returns this:

-rw-r--r-- 1 pi pi 548406 Jan 11 20:24 /opt/retropie/configs/fba/launching.png

I have no images folder in the arcade folder. Should the three corresponding system images be placed in there?

When typing the last line I can confirm that your code is there. Do you want me to SSH into the pi and get the code, or I guess the above things are the reason for my issues..

meleu

@andershp hey, are you still interested in this stuff?

I've made some changes on the script, taking care of those different mame system folders, and maybe it can work now. Again: I didn't test it on an actual RetroPie.

If you wanna give this another try, Just remove from your runcommand-onstart.sh my previous code you added a few days ago (or delete the file if you had nothing there before).

And then try again the same steps I mentioned on a previous post:
https://retropie.org.uk/forum/post/126827

AndersHP

@meleu said in Runcommand launch images automatically chosen for ROM-specific emulatorchoices:

@andershp hey, are you still interested in this stuff?

What do you mean? Of course!

Cool, will try it again and post back here :)

AndersHP

@meleu I just tested, and nothing changed... Still not working.
The script is 3.750 kb, is this the new version?

AndersHP

@meleu ?

meleu

@andershp I'll be able to code and test my code on a real RetroPie system in a couple of days. I hope I find a definitive solution for this.

Wait a little.

meleu

@andershp hey bro! I fixed the script and tested. Seems to be working fine now.

Could you test it again?

By the way, the problem was just that I missed the -launching on the filenames. 😅

AndersHP

Sweet! I will test it tonight. Thanks! :)

AndersHP

Sorry, man. It's not working for me.. I'm starting to feel like something's wrong with me..

The new runcommand-onstart looks like this, correct?

I'm still not understanding that some of the lines contain "mame" - shouldn't it be either mame-advmame or mame-libretro? (see here)

So, just to be sure my setup is not wrong; my 3 launching images are placed here:
/opt/retropie/configs/mame-libretro/launching.png
/opt/retropie/configs/mame-advmame/launching.png
/opt/retropie/configs/fba/launching.png

meleu

@andershp said

The new runcommand-onstart looks like this, correct?

Nop. You're using the previous version. Delete the file and perform those commands again.