Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save State Auto Increment Resets To 0 After Quitting RA #17520

Open
2 tasks done
Quest79 opened this issue Feb 5, 2025 · 4 comments
Open
2 tasks done

Save State Auto Increment Resets To 0 After Quitting RA #17520

Quest79 opened this issue Feb 5, 2025 · 4 comments

Comments

@Quest79
Copy link

Quest79 commented Feb 5, 2025

Is there an existing issue for this?

  • This is a bug in RetroArch frontend
  • I have searched the existing issues

Description

TLDR: 1.20 is not remembering its save-state slot # between sessions causing state overwrites. Why? This worked fine in 1.16 i have not tested other versions except 1.20. See below to analyze my save settings.

I have my saves setup to

  1. Auto save on quit
  2. Auto load on game open
  3. Save states auto increment
  4. Saves saved to working and accessible directory inside a folder names after the core, in the same dir as the game itself (there are no issues with reading or writing files)
  5. I have done this before (1.16) and its worked as any sane person would expect it to.

What happens? Everything works except the most important thing; keeping my save stats.

  1. Pretend im playing a game and i have 10 save-states. It auto-incremented. (yay!)
  2. I quit the game and an auto save is created (great)
  3. I open the game and it auto-loaded the auto-0save (omg brilliant!)
  4. I gleefully play and make a new save-state. To my horror it saves to slot 0. OVERWRITING MY PREVIOUS SAVE
  5. I try again and it auto-saves to save-state slot 1...then 2... etc.

Where is the setting that allows RA to remember between sessions what save-state slot it is at? Why is it doing this? Why in any world would anyone want it to work this way? I know it is possible because this is how it worked in 1.16. Am I just screwed out of updating? Is this a bug?

Expected behavior

What would you expect to happen?

  1. I expect that when I make save states that they auto increment.
  2. I expect when i quit RA, that an auto-save is made
  3. I expect when i open RA, the auto-save is loaded.
  4. I expect when i click my save-state hotkey that it remembers where its last slow # was saved to.

Steps to reproduce the bug

Image

Image

Version/Commit

1.20.0

Bisect Results

It worked in 1.16 possibly after that too

Present in the nightly version

I don't know

Platform & operating system

Windows 11

Affected Cores

Snes9x

Environment information

No response

Relevant log output

@Quest79
Copy link
Author

Quest79 commented Feb 5, 2025

Video of this issue. is there an obscure setting im missing? If so it REALLY should be on by default.
RA does remember the savestate slot on between restarts on 1.16.

Desktop.2025.02.04.-.22.31.57.01.mp4

@Quest79
Copy link
Author

Quest79 commented Feb 5, 2025

I tried the nightly and this issue seems to not be present.

I have a suspicion that this may be an issue with Launchbox somehow, as Launchbox does its own install of RA inside its "Emulators" folder. It was 1.20. It shouldn't make a difference though??? Anyone have an idea why this would happen?

Image

@zoltanvb
Copy link
Contributor

zoltanvb commented Feb 5, 2025

Unfortunately this is an issue in the 1.20.0 stable version. It was fixed in the nightly already shortly after: #17351

@Quest79
Copy link
Author

Quest79 commented Feb 5, 2025

Thank you much for the reply. I will let the Launchbox devs know. I can stop going crazy now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants