Save states vs .srm
-
Is it safe to just use the in-game saves? I haven't had a problem with it yet. Anyone ever lose save data from updates or any other changes?
-
it's fine. whether they would stop working between emulator revisions would depend on the emulator and the changes, but you can almost guarantee that stuff wouldn't change.
-
@Dave-B think it's personal preference, though I use both as I sorta use the save states for the older games that used passwords instead of saves
-
One difference I noticed is that the sram was being written when the game is exited(or periodically if you enable that) while the save state is written immediately. In older versions if things were running too long then it wouldn't exit cleanly then the sram would be lost. I now create a save state whenever I am also making an in game save just to be sure.
Another difference is that the srm is a dump of the sram so likely more compatible between emulators. I've had to make adjustments because of compression but otherwise have been able to move srm's between a few emulators.
-
@sselph You could utilize the autosave_interval setting in retroarch.cfg for situations like that. Retroarch will periodically write the save data to your .srm file according to what you set, so you would be safe in the event of a crash or power loss.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.