rpie-art: easy way to install art on your RetroPie

meleu · 24 Jul 2017, 20:12

@ohmycommodore said in rpie-art: easy way to install art on your RetroPie:

so for the launching images, you do in fact need to manually delete / download images if you want to switch themes...?

Yep. Maybe using the "uninstall art" option can be less painfull for those who have fear of command line. :)

i suppose one way around that would be if, in the future, system launching images were included as part of the themes themselves, as a default of sorts instead of the basic text that pops up during a launch.

I aggree it would be awesome, but I'm afraid it won't happen...

An EmulationStation theme is an EmulationStation thing. A launching image is a runcommand thing. The RetroPie developers have a strong conviction that RetroPie (which runcommand is part of) must be frontend agnostic, which means that EmulationStation must not deal with configs that has nothing to do with the frontend itself (the only accepted exception is the input config).

That being said, I think that moving launching image files automatically when the user changes the ES theme set in the UI Settings is something that won't happen.

@BuZz am I right saying that?

BuZz · 24 Jul 2017, 23:27

@meleu yep. Pretty much :-)

beastmode · 28 Jul 2017, 23:20

@meleu I'm unable to press a button to configure launch options for individual games after using the rpie-art tool to set 16:9 basic launching images by @tmntturtlguy

How do I go about solving this?

RetroPie-Setup Script Version: 4.2.12 (all packages updated)

meleu · 28 Jul 2017, 23:40

@beastmode rpie-art can't do this kind of "harm" on your system. Maybe it's related with the issue reported here. The good thing is that it's already solved. You just need to update your RetroPie-Setup script and try again. ;-)

jdrassa · 28 Jul 2017, 23:48

@meleu said in rpie-art: easy way to install art on your RetroPie:

That being said, I think that moving launching image files automatically when the user changes the ES theme set in the UI Settings is something that won't happen.

I was thinking about this recently and one idea I had would be to implement scripting similar to what Pegasus is doing.

meleu · 28 Jul 2017, 23:55

@jdrassa it would be neat! You guys don't stop!! Hehehe!

ruckage · 29 Jul 2017, 00:12

@beastmode
Are you waiting until the launch image disappears? You can't access the menu while the launch image is being displayed.

From the wiki:

Once these images are installed, the timing to activate the the runcommand menu differs, in that pressing a button will not register successfully until just after the image has disappeared.

TMNTturtlguy · 29 Jul 2017, 00:20

@ruckage Very true. I have my launch images display for 4 seconds, i then have about 1/2 second to hit the button in order to access the options menu.

rkoster · 31 Jul 2017, 00:04

Minor issue, but the script allows uninstalling of overlays specific to a game, but does not show the generic overlays for whole systems, such as NES or GBA, so they cannot be uninstalled from there.

Further, going into the Retroarch GUI and disabling the generic overlay or leaving the selected overlay blank doesn't take. Next time you launch the system, it's back.

VGMonkey · 31 Jul 2017, 07:14

Wow, how have i only just heard of this? Thank you for the work involved in getting this up and running.

meleu · 31 Jul 2017, 07:48

@rkoster thanks for the report. Will fix it when I have a chance.

rkoster · 31 Jul 2017, 16:28

@meleu No problem!

For anyone who has need to uninstall manually, you can go to (from memory) /opt/retropie/configs/ and manually edit out the lines that were added to each system's retroarch.cfg.

I managed to get my GBA display stuck off to one side somehow; you can also basically regenerate the retroarch.cfg by reinstalling that package from Retropie Setup.

hansolo77 · 10 Aug 2017, 21:41

I just tried to do the install of this. Followed the instructions in the 1st post. I ran RetroPie-Setup and updated the script (now at 4.2.15). I then existed ES. In the terminal I cloned the repo, then I went into the directory and tried the ./rpie-art.sh --install command. It said this:

chmod: changing permissions of '/home/pi/RetroPie/retropiemenu/rpie-art.sh': Operation not permitted
FAIL: failt to install "rpie-art.sh" on RetroPie Menu.

Not sure what I could have done wrong... don't want to try a sudo ./rpie-art.sh --install until you say to..

meleu · 10 Aug 2017, 21:54

@hansolo77 will look at it tonight. Thanks for the report.

hansolo77 · 10 Aug 2017, 22:09

@meleu OK cool. I was bored and decided to try and install this so I could get @TMNTturtlguy 's loading screen art for his ComicBook theme. Guess I'll just do something else in the interim. ^_^

meleu · 10 Aug 2017, 22:12

@hansolo77 said in rpie-art: easy way to install art on your RetroPie:

Guess I'll just do something else in the interim.

For example use rpie-art with a keyboard. ;-)

hansolo77 · 10 Aug 2017, 22:27

@meleu Naw that'd be to easy. :)

meleu · 8 Nov 2017, 08:02

@hansolo77 said in rpie-art: easy way to install art on your RetroPie:

I just tried to do the install of this. Followed the instructions in the 1st post. I ran RetroPie-Setup and updated the script (now at 4.2.15). I then existed ES. In the terminal I cloned the repo, then I went into the directory and tried the ./rpie-art.sh --install command. It said this:
chmod: changing permissions of '/home/pi/RetroPie/retropiemenu/rpie-art.sh': Operation not permitted
FAIL: failt to install "rpie-art.sh" on RetroPie Menu.
Not sure what I could have done wrong... don't want to try a sudo ./rpie-art.sh --install until you say to..

Everything is fine with the script. All files/directories under ~/RetroPie/ should be owned by user pi. Are you mounting a non-Linux partition in ~/RetroPie/?

Try sudo chown -R pi:pi /home/pi/RetroPie and then try ./rpie-art.sh --install again (without sudo!).

hansolo77 · 11 Aug 2017, 22:59

@meleu said in rpie-art: easy way to install art on your RetroPie:

Everything is fine with the script. All files/directories under ~/RetroPie/ should be owned by user pi. Are you mounting a non-Linux partition in ~/RetroPie/?

Try sudo chown -R pi:pi /home/pi/RetroPie and then try ./rpie-art.sh --install again (without sudo!).

Yeah my whole /RetroPie sub-folder is owned by root. I will try this soon as I get a chance.

hansolo77 · 8 Dec 2017, 03:53

Seems to still be giving me trouble..

chmod: changing permissions of '/home/pi/RetroPie/retropiemenu/rpie-art.sh': Operation not permitted
FAIL: failed to install "rpie-art.sh" on RetroPie Menu.

Prior to cloning from github I did the sudo chown -R pi:pi /home/pi/RetroPie and then ran ls -l /home/pi/RetroPie and saw that ownership was still root:root... not sure what else there is to do....

EDIT - Trying something different. I ran a chown --help and read that the -c flag makes it display when a change occurs. So I decided to try and run sudo chown -c -R pi:pi /home/pi/Retropie and have been watching for the last couple of minutes as its displaying changes from root:root to pi:pi

GRR - ls -l /home/pi/RetroPie still shows root:root

EDIT - Did a little more research..
https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=40402
I asked google how to change ownership of folders in Raspbian. This led me to a search result "chown not working?". A brief read through had me thinking about fstab. According to that thread, the ownership of the drive is assigned during bootup when the drive is mounted. Since my build uses a USB hard drive, I had an a-ha moment and looked at my own fstab settings. Sure enough, I wasn't assigning a proper username at all, so it was defaulting to root. I took out the bit that said user, and replaced it with uid=pi,gid=pi like it says to use in the RetroPie Docs. That doc must have been updated since I installed all this. When I first started, I didn't know ANYTHING about Linux and everything. So I did this a a complete cut/paste job. Had that info been there, it would have been there now too.

Anyway, I rebooted, exited to terminal, did the ls -l /home/pi/Retropie but and confirmed it now reads as pi:pi for all the folders. I then rand the ./rpie-art.sh --install command and it says SUCCESS. Now I just have to play around with it. :)

EDIT - It said SUCCESS, but it didn't install it. Where is it supposed to be? I looked in the RetroPie menu inside ES but it's not there. I also looked inside the RetroPie-Setup menus. Did I miss something?

EDIT - I looked at the source for the script and saw what it's basically doing (copying an entry to the script in to the retropiemenu folder) and started thinking "what if it needs to be ran as a root?" So I ran sudo ./rpie-art.sh --install. This was my result:

pi@retropie:~/rpie-art $ sudo ./rpie-art.sh --install
ls: cannot access /root/RetroPie/roms/mame-libretro: No such file or directory
ls: cannot access /root/RetroPie/roms/arcade: No such file or directory
ls: cannot access /root/RetroPie/roms/fba: No such file or directory
ls: cannot access /root/RetroPie/roms/neogeo: No such file or directory
cp: target ‘/root/RetroPie/retropiemenu/’ is not a directory
FAIL: failed to install "rpie-art.sh" on RetroPie Menu.

Just for kicks, I went into the /home/pi/RetroPie/retropiemenu folder and confirmed there IS a file named rpie-art.sh file in there, but the entry just isn't showing up in ES. There is also a gamelist.xml file here, and when I checked it, it does NOT have the rpie-art entry listed... so maybe that's where it's failing, because it's not updating the gamelist?