[QUOTE=Radius;53423]First of all, the real fix is fixing the crashes, not masking the problem. Second, this is partly an API limitation. The API can’t differentiate reads and writes. I don’t say it’s a problem, it can be done, it’s just a bad practice.
No PS1 doesn’t do that. But libretro doesn’t have specializations depending on the platform. That’s a bad practice too (changing the API for every possible use case that pops up).[/QUOTE] No, the real fix is When my game saves, the emulator saves. Regardless of crashes, hangings, power losses, ANYTHING, if the game saves, and the saving process isn’t interrupted, it must keep the save, not lose it because, half an hour later the emulator crashed and the option wasn’t correctly set up!
Cutting straight to the chase, I’ve just thought of a even better solution, that doesn’t involve rewriting any piece of code, or behaviour… apart from a few menu settings:
On the current automatic backup interval of SRAM option, put a lower threshold than 10 seconds and warn that settings that low may be unsafe.
If I could set it to something, like, 1 second, or even half second, and If the description of the option said something like “Settings lower than 10 seconds might cause excessive wear of your storage media”, my trust issues with RetroArch would be over.
And I’ve tested the Nightly build, the new XMB has option descriptions, it’s just a matter of outputting it properly.
It’d work almost like it was real-time saving, so close, that I could even consider it was INDEED real time.
So… Instead of reworking the whole saving issue, can that automatic backup be lower than 10 seconds?