+- forums.PPSSPP.org (https://forums.ppsspp.org)
+-- Forum: PPSSPP - Playstation Portable Simulator Suitable for Playing Portably (/forumdisplay.php?fid=1)
+--- Forum: General Discussion and Announcements (/forumdisplay.php?fid=2)
+--- Thread: autosave?? (/showthread.php?tid=2984)
autosave?? - ppssppftw - 04-25-2013 10:34 AM
Autosave would be cool if implemented
RE: autosave?? - rikimtasu - 04-25-2013 01:42 PM
auto save state? there are some game with autosave build in too if you mean that
RE: autosave?? - Preet - 04-25-2013 01:46 PM
He mean game should be automatically auto save to a particular point in game.am i right??
RE: autosave?? - vnctdj - 04-25-2013 02:29 PM
I think that an autosave function is something strange, we should better use the save system of the game itself...
You have a kind of save anyway, if you press your "Escape" button you can do a "quicksave" : by clicking the "Save State"/"Load State" button you can save/load a precise moment in the game !
RE: autosave?? - Preet - 04-25-2013 03:15 PM
Yeah,this is easy.autosaving can cause other problems.u don't know where it is saving u'r game
RE: autosave?? - GuilhermeGS2 - 04-25-2013 05:17 PM
Yeah, Maybe autosave can cause performance loss.
RE: autosave?? - vontman - 04-26-2013 08:12 AM
and alot of crashes
RE: autosave?? - GuilhermeGS2 - 04-26-2013 04:36 PM
Closed
RE: autosave?? - Henrik - 04-27-2013 07:30 AM
I don't know, it's not THAT crazy. Some emulators can even take a snapshot every second, then if Mario falls into a pit you can just press backspace a few times and warp back.
On a NES though, a savestate is about 2kb so you can have infinite amounts of them in RAM. On the PSP, even a compressed savestate is often 15-20 MB so we can't keep that many in RAM. On PCs though you could keep quite a few though...
The other issue with the bigger savestates is that it takes time to do the snapshot. You only have a few milliseconds to do it, otherwise you will notices a stutter every time the emu takes a snapshot. On fast PCs it may be possible to do it fast enough (we'll have to avoid clearing caches the way we do now though somehow), will be very hard on mobile though.
An alternative autosave model is to simply have a single savestate in RAM that you save to every minute or so, and write it to disk/permanent memory on a background thread. This approach might even be possible to do nicely on mobiles, but loading a savestate other than the very last one will be slower.
Of course there are even more possibilities.