Can't save states on any system
-
- /opt/retropie/configs/all/retroarch.cfg
- The folder
/opt/retropie/configs/all/retroarch/cores
does not containfceumm_libretro.info
-
@smeghead said in Can't save states on any system:
The system retroarch reference the one in the all retroarch config :
retroarch.cfgThe file here doesn't show an recently updated
retroarch.cg
. The update would add some new options, which are now showing up in your.cfg
file. Are you sure re-installedretroarch
after updating the RetroPie-Setup script and you didn't get any errors ?EDIT: @WhiskeyIce I can see the same symptom your config file - some options which the new updated install script will add are missing.
Can either of you re-run an update for RetroArch from the setup script, exit the setup script, then look into
$HOME/RetroPie-Setup/logs/
and get the most recent log file there. Unpack it (7zip should be able to handle this), then post the log file on pastebin.com. -
@mitu sorry, it was this one, I'd backed up the old one
new retroarch.cfg -
@smeghead your config file seems to be have been saved from the menu and also not configured by the setup script. Try removing the lines:
libretro_directory = "~/.config/retroarch/cores" libretro_info_path = "~/.config/retroarch/cores"
and see if saving works.
-
@mitu do I re-install from binary or install from source?
-
@WhiskeyIce Both are fine - use the binary option since it's faster.
-
-
Oh it's working now!
Not sure why it failed before!
Thank you for your help @mitu -
@WhiskeyIce said in Can't save states on any system:
Oh it's working now!
Should be, the log file shows the
info
files have been downloaded:.... git clone --recursive --depth 1 --shallow-submodules --branch master "https://github.com/libretro/libretro-core-info.git" "/opt/retropie/configs/all/retroarch/cores" Cloning into '/opt/retropie/configs/all/retroarch/cores'... HEAD is now in branch 'master' at commit '3302a7322258a2fc2c0cd2a5bf2eda239910eb83' Already on 'master' ...
-
@mitu not working yet after removing these two lines
-
-
@smeghead You ran a 'all packages' update - I asked you to re-install RetroArch only. Go to the
retroarch
package and in thecore
section and re-install it, then re-try again to see if saving works. -
@mitu ah yes sorry, after re-installing retroarch it's working.
Thanks you a lot ! -
@mitu I noticed this thread after having the same problem on a fresh RetroPie build. Following the steps here, I re-installed theRetroArch
package (from Binary) inRetroPie Setup
, but the issue persisted. I thought maybe it was because I still had my previousretroarch.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.
-
@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. -
@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 individualretroarch.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
asmenu_show_load_content_animation
and changing it from"true"
to"false"
. -
@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.
-
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. -
@ObscureUsername Did you try to explicitely update
runcommand
? Which version of RetroPie were you using before you updated ? -
@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/LinuxSo 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
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.