search

Swordfish90 / Lemuroid

All in one emulator on Android!
GNU General Public License v3.0
2.51k stars 164 forks source link

Autosave states kill save files #335

Open ulmeck opened 2 years ago

ulmeck commented 2 years ago

Describe the bug When using auto save states (at least in GBA, I expect for other cores), if a glitch causes the core to fail/be killed, the core appears to restart from the last autosave, axing existing save files and losing progress.

Turning off auto save states and reenabling seems to do something similar.

Expected behavior I would expect that on start, the app would detect a core crash, and restart the rom from boot with the current save files intact, instead of the last autosave state.

Smartphone (please complete the following information):

Souvikns commented 2 years ago

This happen to me, I lost a lot of progress in radical red, do you think turning off autosave can solve the problem for now?

svin24 commented 2 years ago

I am not certain but I think this issue affects me too on Pokémon emerald(Moemon). I actually saved and every time I saved I restarted the emulator to check my save was there. After leaving my phone for a while I found it missing reverting to a save file from a few hours ago.

I tested it a bit with a standard save state. I have a save with a time of 2:3x. With a save state at 3:44. If I save the game from the save state and restart the emulator it will load the 3:44 save file but if I force stop the mulator it will go back to the the 2:3x save file