You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Auto save state enabled, whenever you close content or quit retroarch, you get an "auto" save state created.
Issues is: when you load content while still having one running, it wont create the save state.
This is insidious because its so easy to do and lose progress.
Expected behavior
I expect that when I load a content while another one is running, it would behave the same as closing the content then opening another one, thus creating a save state when auto save is on.
Actual behavior
It does not create an "auto" savestate if I load another content while one is running.
Steps to reproduce the bug
Make sure auto save and auto load is on
Start any content
Notice the screen content
Load another content while first one is still running
Load first content again and notice no "auto" savestate has been created
Bisect Results
Version/Commit
You can find this information under Information/System Information
RetroArch: Steam version 1.19.1
Environment information
OS: Windows 10 / Steam OS
Compiler:
The text was updated successfully, but these errors were encountered:
Description
With Auto save state enabled, whenever you close content or quit retroarch, you get an "auto" save state created.
Issues is: when you load content while still having one running, it wont create the save state.
This is insidious because its so easy to do and lose progress.
Expected behavior
I expect that when I load a content while another one is running, it would behave the same as closing the content then opening another one, thus creating a save state when auto save is on.
Actual behavior
It does not create an "auto" savestate if I load another content while one is running.
Steps to reproduce the bug
Bisect Results
Version/Commit
You can find this information under Information/System Information
Environment information
The text was updated successfully, but these errors were encountered: