Can't save states on any system

smeghead

@mitu ah yes sorry, after re-installing retroarch it's working.
Thanks you a lot !

GaucheArtist

@mitu I noticed this thread after having the same problem on a fresh RetroPie build. Following the steps here, I re-installed the RetroArch package (from Binary) in RetroPie Setup, but the issue persisted. I thought maybe it was because I still had my previous retroarch.cfg, but even after deleting them and letting the core create a new configuration on launch, the issue has persisted.

~~Is there anything I can do to help troubleshoot this further? Would a verbose log of me attempting to create a save state help in any way?~~

EDIT: Stupidly, I didn't update my RetroPie Setup to the latest build, so it was running 4.8 from earlier in the year. I'll see if updating it and then re-installing the RetroArch package resolves the issue.

EDIT 2: Issue is resolved based on the previous edit. Sucks about that obnoxious new RetroArch boot window though.

mitu

@GaucheArtist said in Can't save states on any system:

EDIT 2: Issue is resolved based on the previous edit. Sucks about that obnoxious new RetroArch boot window though.

You're probably running with the a 'default' RetroArch config, RetroPie disables by default the 'splash' window when starting a game. You haven't seen it so far because the notification is shown only when the core .info file is present.

GaucheArtist

@mitu Oh, that sounds like it can be easily resolved then! Can I simply delete the .INFO files from \retropie\configs\all\retroarch\cores\? Alternatively, could it be disabled through the individual retroarch.cfg files? I prefer to work directly with those when I can, but I didn't see anything about the splash screen.

EDIT: Found it in the retroarch.cfg as menu_show_load_content_animation and changing it from "true" to "false".

mitu

@GaucheArtist said in Can't save states on any system:

I prefer to work directly with those when I can, but I didn't see anything about the splash screen.

The link from my previous post had the config file option, but you seem to have found it yourself.

ObscureUsername

Just putting this here in case someone else runs into the same issue. I'm not sure why, but updating my RetroPie-Setup script wasn't updating runcommand.sh, causing the 'does not support savestates' problem for me as runcommand.sh was an old version without the change mentioned above.

To resolve it I moved my RetroPie-Setup folder somewhere else (instead of just deleting it, so I had a backup), recreated it by running:
git clone https://github.com/RetroPie/RetroPie-Setup.git
from the home directory and then updating the setup script again. I'm not sure if there's a better way to resolve it, but this worked for me.

mitu

@ObscureUsername Did you try to explicitely update runcommand ? Which version of RetroPie were you using before you updated ?

ObscureUsername

@mitu Looking through the logs it looks like I went in all guns blazing and removed runcommand.sh, then afterwards ran both the setup script update and the runcommand update in the hope that one of them would recreate it... they didn't. Probably wasn't the best way to go about it!

The logs say the setup and retropie versions were:
RetroPie-Setup version: 4.7.11 (6598a90a)
System: rpi4 (armv7l) - Raspbian GNU/Linux 10 (buster) - Linux retropie 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux

So I don't think I've explicitly run the runcommand update before then, although I've defintely run the Setup script update several times before that, and updated everything (via the update option on retropie_setup.sh) about a month ago.

Currently (after re-cloning RetroPie Setup) I'm on:
RetroPie-Setup version: 4.8.2 (28f8e144)
System: rpi4 (armv7l) - Raspbian GNU/Linux 10 (buster) - Linux retropie 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux

EnemySoil

@ObscureUsername I have the same issue with not being able to save in any core.

I'm new to all this stuff and some of the things you said have gone over my head

I moved my RetroPie-Setup folder somewhere else (instead of just deleting it, so I had a backup),

When you say you moved the Setup folder do you mean completely off the drive/card RetroPie was installed on, as if you deleted it?

recreated it by running: git clone https://github.com/RetroPie/RetroPie-Setup.git
from the home directory and then updating the setup script again.

This part I take it was done in terminal access by pressing F4, but I don't follow when you said "from the home directory"

windg

@EnemySoil Try to reset ownership permissions for the rom folder.

RetroPie-Setup > Configuration/Tools > resetromdirs , i hope to works.

EnemySoil

@windg I tried that, unfortunately it didn't help

Every time I load a game I get a notification that says "Configuration override loaded" not sure if that has anything to do with not being able to save as well

windg

@EnemySoil
Did you try to update the system from retropie-setup menu as a previous post mension ?

I reccomend to create a new topic with the neccessery info : https://retropie.org.uk/forum/topic/3/read-this-first

EnemySoil

@windg I did, That didn't help either. I am still trying to figure out how to get the logs I need, my verbose logs do not look like the other one's posted in here so not sure that info would help.

I'm new to this so even posting my logs requires me to google how to do it

EnemySoil

@windg Not sure what I did. But every game I loaded had a notification that said "configuration override loaded" when I disabled that in the RetroArch options I can now save again!

Thanks for helping!