auto save/load state doesn't work on all cores
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
Auto state save/load doesn't work on all cores. I love this feature as it lets me quit retroarch and easily get back where I left off without worrying about manual save states.
Expected behavior
When restarting any rom, if there is an auto save state, it should be auto-loaded (assuming save/load configs are both set to true).
Actual behavior
On some cores it fails to load the auto save state.
[What is actually happening]
On most cores it works as expected. It seems to be a problem with the more complex cores. For instance, I have no problem with:
Genesis Plus GX : 1.7.4 5055106
or
Mednafen Pce Fast : 0.9.38.7 918179c
On cores for nintendo DS and psx like:
Desmume : git e8cf461
and
Beetle PSX HW : 0.9.44.1 df1b19a
it does not load the auto save states.
Just speculating, but maybe it has to do with the size of the states? For these more advanced consoles the save states are 100s or 1000s of kbs, vs 10s of kbs for the systems that work.
I also have the newer 'save state compression' option enabled.
I've tried deleting all save states, and this issue persists.
Environment information
- RetroArch: latest (1.8.7)
- OS: windows 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing auto-loading with the listed working and failing cores, using both save/load settings and save state compression enabled. Compare the behavior across Genesis Plus GX, Mednafen Pce Fast, Desmume, and Beetle PSX HW; done means an auto save state reliably loads when restarting each tested ROM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100