-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[UI] Save state slot doesn't reset to 0 when starting content #12706
Comments
Actually the selected slot I hadn't noticed it at all since I don't have auto conf save enabled, so of course it is always 0 on launch. |
@sonninnos Yeah, I noticed that it was saved to retroarch.cfg after I wrote this issue. Like you say, I assume there's probably some reason for this, although it's not obvious. The auto conf save option, is that Settings -> Configuration -> Save Configuration on Quit you're referring to? I tried disabling it, but the save state slot is still remembered between content launches. |
Sure, because it only prevents it from saving on quit, as the option name hints. That particular resource shouldn't get saved at all if you ask me. |
Yeah, of course. From your previous message ("I hadn't noticed it at all since I don't have auto conf save enabled, so of course it is always 0 on launch."), it sounded like there was a setting that prevents automatic saving to the configuration file. The setting I mentioned was the closest I could find. Could you point me in the right direction, or did I misunderstand your previous message? |
That is the setting I meant. It either saves everything or nothing, so it is not a proper solution. |
Description
The save state slot that is selected before choosing "Close content" becomes the same save state slot that will be selected when launching new content. XMB and Ozone have been tested and behave the same.
Expected behavior
I would expect the save state slot to reset to the default (0) when launching content.
Actual behavior
Save state slot is remembered across content launches.
Steps to reproduce the bug
Version/Commit
Environment information
The text was updated successfully, but these errors were encountered: