runcommand launching images for ANY theme

hooperre

@meleu Out of 20 attempts I was able to get into it twice and only if I mash buttons (may have changed from the square button to the x button). Something has changed for sure. Any thoughts on what config file I need to dig into?

Edit: Okay so it actually works if I press button 0 AFTER the launching screen has disappeared between then and when the ROM actually loads.

meleu

@dankcushions said in runcommand launching images for ANY theme:

generate images for pixel, got this sort of error:

This is a known issue. Talked about it here:
https://retropie.org.uk/forum/post/48043

I'll try to sort it soon... (Not worked on it yet because the @rookervik 's pack for pixel theme is better than the generated images)

also, no way to exit the preview slideshow?

You can hit ctrl+c, but it will interrupt the image generation. To avoid the preview you can enable the no_show option in the settings. ;-)

Swampy

@meleu Thank you very much, it workes!
Which details of the system do you want to have?
I'm using a Raspberry Pi3 and the newest Retropie-Setup 4.1.16.

meleu

@Swampy said in runcommand launching images for ANY theme:

I'm using a Raspberry Pi3 and the newest Retropie-Setup 4.1.16.

Did you installed the official 4.1 image or update from a previous version?

Swampy

@meleu I updated from a previous version.
I think librsvg2-bin was not installed by default in previous versions of retropie.
So I think you don't have to change something.

Thanks for your great script!

Rookervik

@meleu And Rookervik isn't going to approve it since that would be allowing everyone to use the artwork from the pixel theme and that isn't ok :)

If I find time, later on, I will make another batch of Pixel run commands. But I'm working now and free time is very, very limited.

meleu

@Rookervik maybe making this script without the theme makers approval was a mistake. I didn't think about it, sorry. I'll force the script to be unable to generate images for the pixel theme and add some warning about it.

Should I assume that you don't approve the image generation for every theme you made? Or would you like to list the themes you don't approve?

dankcushions

@Rookervik @meleu
maybe i'm missing the something but all the script does is automatically creates launch images for any given theme, right? it doesn't take art from one theme and create another theme under a new name or whatever, it just expands a given theme. it seems like all it does is save themers time and effort :)

IMO clever scripts like this need to seamlessly work across the board so they can ultimately be an automatic thing that's just a feature of ES/retropie. it makes launching games really slick for ALL themes, hiding the 'DOS'-looking stuff that seems to bother some people.

eventually i dream that even the retropie-setup menu could be automatically themed based on the current ES theme...

but yeah, it's up to the themers is they like the idea or not. don't mind me :)

FlyingTomahawk

@meleu
Have you tried it with the Famicom-mini theme by ruckage?
I enter

bash -x  ./generate-launching-images.sh -t famicom-mini

and it I can see the command prompt code running down like a matrix code. Then he tells me that he's done but failed to create for Amstrad since there is no theme folder.
I click OK and go check /opt/retroarch/configs/nes/ and there is no launching.png file.

Doing this currently on my Pi Zero.

meleu

@FlyingTomahawk I would like to see the nes/theme.xml for famicon-mini theme, but I'm behind a proxy that blocks access to mega.nz.

Can you post this file to ghostbin.com or something similar?

The -x option enables the matrix mode to a bash script. Just kidding! :) It's a kind of "debugging mode" way to execute bash scripts.

I don't know why you are executing the script with bash -x but coincidentally this is the way I'm going to ask you to launch the script again.

Please, execute the following command:

bash -x  ./generate-launching-images.sh -t famicom-mini 2> debug.txt

It will generate the debug.txt file. And then paste the content of debug.txt in ghostbin.com or something.

FlyingTomahawk

@meleu said in runcommand launching images for ANY theme:

The -x option enables the matrix mode to a bash script. Just kidding! :)

Not sure why I used bash -x I guess I just saw that here in this topic and used it and it did work always with other themes like my Futura theme or Simplebigart or Metapixel.
This time I am trying to setup the Famicom-mini theme and it doesn't work.
Here the requested data:

Famicom-mini NES file

Debug file

meleu

@FlyingTomahawk Well, I'll need to take a look in other .xml files. Will try to sort this out tonight.

Also, I'm not sure if you are using the right version of the script. If you installed via RetroPie-Setup, the script is at /opt/retropie/supplementary/launchingimages (it's not the reason of your issue, that's just for you to be aware of).

I had to create a dedicated repository for this tool in order to make it work along with RetroPie scriptmodule. This is the repository: https://github.com/meleu/generate-launching-images

I've edited the OP accordingly.

FlyingTomahawk

No hurry here. When ever you find time to look into it is fine with me.
I haven't update anything on the Pi Zero. With only 1 USB port my possibilities are limited.
I downloaded the image file from the RetroPie website, installed everything and I am using your script before it was merged into RetroPie.
I ordered a Pi Zero W and also a Zero4U so I will have more possibilities then.
Thanks.

FlyingTomahawk

@meleu
I am running this Famicom-mini theme with only 4 systems (NES,SNES,Megadrive,GBA) so it is not a big deal for me to create the launching.png images in Photoshop and upload them to my Pi Zero.
Here a sample.
alt text

meleu

@FlyingTomahawk hey! It looks great! But I want to debug the script anyway. :)

Thanks for the feedback.

HurricaneFan

@meleu I'm running retropie version 4.1.18 and am encountering issues making launching images from Carbon theme.

Settings:

Errors:

meleu

@HurricaneFan try this solution here: https://retropie.org.uk/forum/post/59747

And please let me know if it solves your issue.

It seems that your original installation was before 4.1. Am I right?

HurricaneFan

@meleu I started with the default 4.1 build that was released in November. Then I upgraded all packages before I installed this through retropie setup.

meleu

@HurricaneFan did that solution work for you?
https://retropie.org.uk/forum/post/59747

HurricaneFan

@meleu Your suggestion worked!