MiSTer FPGA Forum

Johnny Love wrote: ↑Tue Sep 15, 2020 11:04 pm After closer inspection, it turns out that I never mentioned I was using the "Vitor Vilela SA-1 Enhanced v1.32" version of SMW, at least not here. I did mention it on reddit ( https://redd.it/hqy45b ) which might have more useful information other than that.

I could reproduce it with the SA-1 version. This version uses the save ram as work ram and so the save file is 128KB instead of 2KB on the normal version and it takes a while to write it to sdcard. So if you very quickly load another rom it is still in the process of writing the save to sdcard. If you wait a few seconds then the save is not cleared. The previous SNES core would always clear the save with this game even if you wait a few seconds.

This is more like a main Mister issue. It should show that it is saving on the OSD and block it until it is finished.

I am having this issue with Donkey Kong Country

the .sav file is there in the folder, but when I boot the game, I lost a lot of progress. I play again some time, save the game ad then reboot the game with right most button on mister io board, saveis fine.

But If I turn off mister and go back later, the progress is lost in DKC.

pbsk8 wrote: ↑Mon Feb 01, 2021 2:37 am I am having this issue with Donkey Kong Country

the .sav file is there in the folder, but when I boot the game, I lost a lot of progress. I play again some time, save the game ad then reboot the game with right most button on mister io board, saveis fine.

But If I turn off mister and go back later, the progress is lost in DKC.

Even when autosave is turned on, you still need to open the menu for the save to be written to the card, otherwise it'll be lost.

I deleted the .sav for DKC and I am starting fresh a new gameplay,

I will try now saving in game and then pressing the osd menu button and then pressing the left button to reboot mister and turn it off by pulling the power plug.

I hope this works

This happened to my Minnish Cap save file for GBA a few months ago. It worked great for months, then it started ignoring the save file for some reason.

It does sound like files are being randomly corrupted for whatever reason. It's likely not ignoring the save file so much as it's either empty or corrupt, and the game just doesn't know what to do with it. You could open it in a hex editor and see if it's empty, or if some of the information looks malformed compared to a real save.

Sarge wrote: ↑Sun Feb 07, 2021 4:45 am It does sound like files are being randomly corrupted for whatever reason. It's likely not ignoring the save file so much as it's either empty or corrupt, and the game just doesn't know what to do with it. You could open it in a hex editor and see if it's empty, or if some of the information looks malformed compared to a real save.

Robert, the GBA core dev did just that for me and said the first several bytes were corrupted.

Sounds a lot like what used to happen to me back in the day on my GBA flash cart. I used to run PogoShell, and it would randomly corrupt a bit when I ran on the DS. It didn't do it with an actual GBA, though. Very strange indeed. Hopefully this is something that gets sorted out soon; I'd hate to put in a ton of time only to lose my save through no fault of my own.

EDIT: Just noticed that there was an update that displays a "saving" message when autosave is on. Perhaps this will help alleviate some of those issues.