Overlays Unsaved Upon Updating?

GreenHawk84

Hello,
I haven't been on in a while but I decided to update my Retropie and unfortunately all my overlays unsaved from all the games.

I had them individually saved for each game, not sure what happened? Before I go in and re-save everything in RGUI, does anyone have a quicker fix?

All my files are still there, the images and .cfgs located in /opt/retropie/configs/all/retroarch/overlay/.

sleve_mcdichael

@GreenHawk84 said in Overlays Unsaved Upon Updating?:

All my files are still there, the images and .cfgs located in /opt/retropie/configs/all/retroarch/overlay/.

Then you just need a per-game override config, like:

~/RetroPie/roms/snes/Super Mario World (USA) (Rev 1).zip.cfg (named exactly as the ROM file + .cfg note: .zip.cfg it has both extensions):

# place this file if it doesn't exist
# make sure it includes a line like:
input_overlay = "/path/to/your_overlay.cfg"

Ashpool

@sleve_mcdichael true, but not quite right, IIRC the config (pointing to the overlay|image folder/imagefile) could go to to various places (and the user should be aware of it, if using both locations) -> 1st the one within the rom folder, in this case the filename should be romname.extension.cfg (e.g. asteroid.7z.cfg) and then be used by all (libretro) cores accessing this rom path, or 2nd within the ../configs/all/retroarch/config/[CORE] folder without the rom filenames extenstion (e.g. asteroid.cfg) {and then being used by that core for matching roms within all rom-folders it has access to (?) - as you (i assume), I am in favour of the cfg next to the rom in its folder approach, and therefore haven't tested the other way for its limits/hazards)) ... at least in mid 2023 this was valid: https://retropie.org.uk/forum/post/289427

(Edit: P.S.: also the user should be aware that these so called overlay configs are not just a setup for the screen layout/overlay-image used but in general an override for everything that can be included/set within the (root)-retroarch.cfg (IIRC/AFAIK) and if multiple exist in the various places one should be aware of the chain-of-command (which comes first and which would do the final setting in case of a particular option set in multiple instances of such an override config; I apologize for adding this here, as it has nothing to do with the OPs problem, but is (IMHO) something every user using libretro overlays should keep in mind whence setting them up.)

Ashpool

@GreenHawk84 If all your overlays/image files to be referred by the actual retroarch config that is setting up the screen/overlay for that rom(&libretro core) are still present and there, what is about the override config file? I am not aware of any core-name changes, but if you opted for the configs-core-romname.cfg approach is the core-name still the same? Maybe it could help if you take one particular rom/core as an example and list for all needed files (image/config of image/rom config to point to image) their place and content and verify that the core referenced (if it is in the cores config folder) is actually being still used by the runcommand ? Also from which version/underlying OS have you upgraded (A while could mean anything (especially in retro context) from a few weeks to some years/decades)? I am not sure what would happen nowadays if someone would do an upgrade from a Jessie based image (or older?) -> what was the base of your original image/how did you updated your install? What System (I assumed a Raspi, but whether or not...)? ... please provide all the details necessary to set the context for the troubleshooting.

GreenHawk84

@Ashpool said in Overlays Unsaved Upon Updating?:

... please provide all the details necessary to set the context for the troubleshooting.

Sorry about that, I am running a Pi4B with Buster. I have updated frequently but this time it's been maybe a couple months.

Here is a screenshot of what Retroarch shows me now, I think overlays simply got turned off somehow:

When I toggle this, the work I did before comes back, but I am still unsure where to go to set this globally so I don't have to do this on all my games:

mitu

Try adding input_overlay_enable = true into the global RetroArch configuration file (/opt/retropie/configs/all/retroarch.cfg).

GreenHawk84

@mitu

Looks like that's already set, but all my cores and games are toggled off:

I wonder if each game override is defaulting the setting to off? I had all this set before so not sure what the update could have done to break it.

sleve_mcdichael

@GreenHawk84 the # symbol at the beginning of # input_overlay_enable = "true" makes it into a comment. Remove that symbol to explicitly enable the setting.

mitu

@GreenHawk84 said in Overlays Unsaved Upon Updating?:

I wonder if each game override is defaulting the setting to off? I had all this set before so not sure what the update could have done to break it.

The default is not true, starting with version 1.16 it defaults to false.

EDIT: but if this is option that's causing this issue, I'd be happy to change the defaults in RetroPie to avoid this kind of problems during upgrades.

GreenHawk84

@sleve_mcdichael, yep removing the hash worked. Basic knowledge, easy fix, thanks a lot!