Runcommand System Splashscreens!

meleu

@backstander said in Runcommand System Splashscreens!:

I think this script looks at the theme's directory structure and matches with the rom's directories

What script? :-)

This is the @Rookervik 's pixel-friendly launching images pack topic. lol

backstander

@meleu
I was just assuming he was talking about your script ;-)
Now after reading @madmodder123 post again, maybe he is just copying the images around lol. Either way he'll get better results if he using pce-cd and tg-cd directory names.

zoop

@Rookervik Thank you! This gives the setup a much more polished look. Great job and thanks for sharing.

Nathan1031982

Awesome loading screens. Now I just have to get to installing them.
Thanks for the contribution!

madmodder123

@backstander
I have tried all of these but it still loads up the regular tg16 image instead of the tg16cd image
alt text

backstander

@madmodder123
I did some digging and both the Carbon and Pixel themes have a directory named tg-cd but this Pixel Runcommand System Splashcreens uses the directory named tgcd All 3 do have the correct pce-cd directory.

Let's just reinstall it!
I'd recommend that you SSH into your RPi (make sure your are connected to the internet)
https://retropie.org.uk/docs/SSH/

Here is how I installed it from the command prompt:
wget https://dl.dropboxusercontent.com/u/60872572/EmulationStation/Pixel/Pixel_RunCommand_Wallpapers/launching.zip

unzip -o launching.zip -d /opt/retropie/configs/

This should fix the "tg-cd" name
you might have to delete /opt/retropie/configs/tg-cd/ first
rm -r /opt/retropie/configs/tg-cd/
mv /opt/retropie/configs/tgcd/ /opt/retropie/configs/tg-cd/

alysin_croft

@Rookervik Looks great, but is there a reason why some have a pure black background, while some have a noisy gray background? (For example, PSX background is black, while NES is gray with pixelated noise)

madmodder123

@backstander
I tried everything you suggested, and it still hasn't worked properly :'(

pjft

Hi all,

I just installed the latest Carbon loading screens and they look great. Thanks!

An odd question, though: do these add a material time to the loading process, or is it just my impression/perception? i.e. is the emulator/runcommand script running in the background of the image, or is it only going to run after the image? It might be perception, mind you, so just wanted to double check :)

Also, I take it we're choosing to have lower-resolution images because it'd take a bit to load them, is that it?

Thanks!

EDIT:

I believe I know why my impression is that one. Truth is, when I launch it, it pops the runcommand menu for a very brief instant, then the image shows up, then the image ends up disappearing while the emulator still hasn't loaded, and then finally the emulator loads.

It seems from the code it's just loading for 2 seconds.

If I increase the time, what are the consequences? I believe the emulator will always render on top, according to @Buzz , but other than that I take it it doesn't impact in any way the loading time? Also, if I press a key/button, I take it the image disappears, is that it?

That's exactly what I want, if that's the case. Any reason for it to be only for 2 seconds in the current commit?

Thanks.

meleu

@pjft said in Runcommand System Splashscreens!:

An odd question, though: do these add a material time to the loading process, or is it just my impression/perception?

On the raspi it adds 2 more seconds to show the image (and after the image is gone the screen goes black for another 2 seconds waiting the user "press a button to configure").

On x86/x11 it doesn't happen (feh runs in background).

meleu

I saw your edit after my last post...

@pjft said in Runcommand System Splashscreens!:

It seems from the code it's just loading for 2 seconds.

The command used to show the image is here: https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/supplementary/runcommand/runcommand.sh#L900

fbi -1 -t 2 -noverbose -a "$image" </dev/tty &>/dev/null

The -t 2 is the 2 seconds timeout option. The script doesn't do anything during these 2 seconds. Initially we tried running fbi in background, but @BuZz changed it in this commit due keyboard input/stdin issues.

If I increase the time, what are the consequences?

If you increase the seconds in the -t fbi option, the script will take more time to launch the game, since it will take more time showing the image.

I believe the emulator will always render on top, according to @Buzz

Maybe he said that before that commit, when fbi were executed in background.

Also, if I press a key/button, I take it the image disappears, is that it?

AFAIK fbi exits when the <enter> key is pressed. Then if you press the button 0 in joystick (the same that calls the runcommand menu), it stops the fbi and then wait 2 more seconds (with a black screen) for the "press a button to config".

pjft

@meleu Oh. Ok, that's very interesting to know - thanks for the breakdown.

Then, correct me if if I'm wrong: the script is, indeed, making the loading process take 2 more seconds than it would without the image being shown? Is that correct?

Thanks.

meleu

@pjft said in Runcommand System Splashscreens!:

Then, correct me if if I'm wrong: the script is, indeed, making the loading process take 2 more seconds than it would without the image being shown? Is that correct?

If you're talking about RetroPie on a Raspberry Pi, then you're absolutely right. I have nothing to correct. :-)

As I said above, on a x86/X11 platform, runcommand uses feh to show the image and launch it in background.

pjft

@meleu Sorry. I did mean on the Raspberry Pi indeed. :)

Thanks for the heads up!

Hope you're doing well.

Caveman420

It wont work on the Megadrive for me. Its working perfect on all the other consoles. Any ideas?

meleu

@Caveman420 is there a file named /opt/retropie/configs/megadrive/launching.png in your system?

Caveman420

@meleu yeah it is. I have two folders for roms Genesis and Megadrive, but only one for config files, Megadrive. If I delete the genesis rom folder it deletes the megadrive one as well. I also tried adding a genesis config folder and copying the contents of the megadrive config folder but nothing. I'm still new to retropie not really sure what else to try.

meleu

@Caveman420 I can't confirm right now, but I think the ...configs/genesis is a symbolic link to ...configs/megadrive...
I suggest you to remove and reinstall lr-picodrive, it would reinstall the config files you messed up.
And then try to put the megadrive launching.png in the right place.

madmodder123

@backstander
Could it have somethng to do with the fact i am using Pixel-Metadata instead of the regular theme?

Caveman420

@meleu Ok I tried that and nothing happened. I just wiped everything and started a fresh install using the image I got from the retropie website and the exact same thing happened