Saveing Fuckery

RetroArch General
#1

Heya fellas,

Losing my mind a bit here. Has something been changed with save states in the last couple years? New hidden toggle that effects saves im not seeing? I could be just blind. I WANT it to be my fault. My previous setup i was able to do all of the following at the same time.

  1. Auto save on exit
  2. Hotkey savestate that auto increments
  3. Auto load last Autosave (or highest number save state?)

Now Retroarch REFUSES to do this. It will autosave on quit and auto load, and it will also increment save state, BUT when i quit and come back into the game, the save stats start at 0 again. Overwriting my shit. My settings clearly say to NOT fing do this yet it does anyway.

Why is something so basic so convoluted? What happened here? Here is a test. I made 5 save states, with auto save on quit on. I re-opened RA, it loaded the auto save as it should. I click my hotkey to make another save state that SHOULD GOTO SAVE STATE 6 yet i get this:

retroarch 020425 211906 🐂 3840x2160
retroarch 020425 211906 🐂 3840x21603840×2160 913 KB

Save settings:

retroarch 020425 212633 🙉 3840x2160
retroarch 020425 212633 🙉 3840x21603840×2160 624 KB
retroarch 020425 212641 🚘 3840x2160
retroarch 020425 212641 🚘 3840x21603840×2160 675 KB

#2

I just confirmed in 1.16 that its working as it should. What the hell hidden setting is doing this? Obviously no one wants their save states to reset to 0 every time they close the game when there is an explicit option to keep auto incrementing. :face_with_symbols_over_mouth:

???

#3

You shouldn’t be using savestates with RPGs. You’re just asking for trouble as evertime you load a save state you overwrite the SRAM with whatever data was there at the point the state was saved.

There are now provisions to address this though.

#4

I’m not sure but I think this is actually a bug. Check the RetroArch GitHub for bug reports and/or pull requests that might mention it.

#5

It’s probably this (already fixed):

1 Like