this post was submitted on 06 Jul 2023
25 points (100.0% liked)
RetroGaming
19573 readers
552 users here now
Vintage gaming community.
Rules:
- Be kind.
- No spam or soliciting for money.
- No racism or other bigotry allowed.
- Obviously nothing illegal.
If you see these please report them.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've used Lemuroid for Game Boy emulation before but it had trouble remembering my saves for some reason. It'd sometimes forget that I'd saved recently, and so I'd load and find myself in an earlier save. Also on a Samsung phone, albeit an A-series. Do you know what might have caused this?
Nope, I haven't had any issues with save states. Keep in mind, there's a difference between saving the state manually and the option to auto save state when you leave the app. If you force quit Lemuroid or whatever goes wrong as you leave the app, the auto state save might not work. That's my best guess. I usually do both, save state myself, and rely on the auto save state. :)
Oh, I actually meant "real" saves, done from in-game. It's like Lemuroid had some chance of not updating the save file. I never figured out why this might happen. (Maybe it has something to do with not properly generating a new state on exit and having old states wipe newer saves?)
Ohhhh I got you. I'm not sure. In other emulators (on computer) I've seen that save states don't actually save to the drive until you quit the emulator, so maybe something similar happened here?