Core does not support save state

[otrab16]

Can someone help me troubleshoot what might be going on with my install? I can provide whatever logs will help troubleshoot. I've been using this build for about 3 years and just recently my save states stopped working for all cores. I've updated the build and tried to reinstall retroarch and still can't seem to get this to work...

Version: 4.8.6 - Last Commit: 2 days ago (3c599705)
System: rpi4 (armv71) - running on Raspbian GNU/Linux 10 (buster)

I have attached some information within pastebin for reference:

Verbose logging for 1942 w/ NES: https://pastebin.com/Ka8dN3fM
/opt/retropie/configs/nes/retroarch.cfg: https://pastebin.com/kWUD9rYj
/opt/retropie/configs/all/retroarch.cfg: https://pastebin.com/rNmXGiM8

Thanks!

[mitu]

This can happen if you've only updated RetroArch without updating the RetroPie-Setup script.

You say you're using version 4.8.6 - can you re-run an update for RetroArch and then try again to see if you get the save message when saving ? If that still doesn't work, then can you provide the last RetroArch installation/update log from $HOME/RetroPie-Setup/logs (on pastebin.com) ?

[otrab16]

I ran both an update for the entire system to download the retropie script along with raspian update. This is the most recent log that pulled back data for retroarch. No dice... save states still fail.

Reinstall log: https://pastebin.com/zuuQ7UsT

[mitu]

I see from the log that the .info files needed for save state support are downloaded and updated. Can you delete/rename the override for the core at /home/pi/.config/retroarch/config/FCEUmm/FCEUmm.cfg and see if saving works ?

[otrab16]

Thank you so much for the help! Save state now works for NES. I'm assuming I will have to rename the .cfg for each emulator and save a new .cfg to get back my settings I had in place for each core? I appreciate your help on this!

[mitu]

@otrab16 You can remove the line containing libretro_info_path (I think this is the option that's causing the issue) from those .cfg file if you don't want to remove them.

[otrab16]

@mitu it failed to save again after i commented out that line. i'm doing a delta on the two files and it seems there are a bunch of additional options in the newer config file. I'm sure mine is probably from 3 years ago when i initially started building this.

New: https://pastebin.com/x3frXRAh
Old config: https://pastebin.com/2tQ7gLaU

[otrab16]

To give an update I've now updated nearly all of the cores with my custom settings from the new config file save.

Unfortunately, none of the MAME emulators allow for save states. I never saved any custom core overrides to those emulators so this is a bit baffling.

[mitu]

@otrab16 said in Core does not support save state:

Unfortunately, none of the MAME emulators allow for save states. I never saved any custom core overrides to those emulators so this is a bit baffling.

What does 'none' mean ? Mame2003, Mame2010, etc. ? Note that saving state in older MAME versions is driver dependant, so it's not going to work 100% - though you'd get a 'driver does not support save states' instead of 'core doesn't support save states'.

[otrab16]

@mitu to give you an example - mame 2010 states 'core does not support save states'. the core configuration file isn't being pulled though which is why i'm confused because i've never touched any of the MAME core overrides.

[mitu]

Mame2010 appears to have savestate = false in their config, so maybe the 'cannot save' message is normal. Other MAME cores do have 'savestate = true' though (MAME2003, MAME2003+, MAME).