Emulator Issues #12350
open
Gamecube Memory Card Files Won't Overwrite Old Saves
0%
Description
I discovered this on Path of Radiance but also is on Zoids Battle Legends
When I try to make a save file for any Gamecube game, it gives the message saying the game was saved properly, but the saves will remain unchanged. I was able to make save files for Zoids Battle Legends. I first noticed the problem when I imported a save file for Fire Emblem: Path of Radiance. I initially only did this to create a save file for transferring to Fire Emblem: Radiant Dawn, but a week or so later I started playing Path of Radiance. When I came back the following day to continue my save, I discovered that all the saves I had made were gone, and the save files from the import were put back to where they were when I initially imported the game. Basically, it didn't remember that I deleted a save file and then saved a new file over that slot. I have since tried deleting the memory card folder, and I have tried changing where the memory card points to, and it always points me back to the original saves. I eventually tried deleting the file from the emulator's view of the memory card, and that did delete the files, but ingame it still won't recognize any new saves, or that I even have a save file for the game. On a hunch I checked Zoids Battle Legends and discovered I couldn't update any saves in that game either, so I assume it's all Gamecube games. Wii saves are working fine.
I do not know how to reproduce this bug. I have used Dolphin for years for these games in particular over several computers and never seen it before. I'd be happy to answer any questions or provide any data to try to get us to a point where someone might be able to reproduce the save. I've seen a small number of other people have had this problem but none of their fixes have worked for me.
I am on 5.0-13178.
PC Specs: AMD Ryzen 7 3750H with Radeon Vega Mobile Gfx 2.30 GHz
64-bit operating system, x64-based processor
Windows 10 Home
Let me know if I can provide any further information on this.
Updated by notkate about 3 years ago
Same issue here. Save states work as expected, and memory card saves work as long as the program stays open.
Example: playing Pikmin 2 (ID: GPVE01), the game autosaves at certain points. Resetting the emulation allows me to load from the autosave, but completely closing Dolphin "resets" the memory card file to when it was first created.
The emulator window says in the upper left corner that it has written to the memory card file when appropriate, but checking the actual file shows it was last edited when it was originally created.
I get this message using "verify" on the iso (not sure if relevant, but can't hurt):
This disc image is in the NKit format. It is not a good dump in its current form, but it might become a good dump if converted back. The CRC32 of this file might match the CRC32 of a good dump even though the files are not identical.
Also using 5.0-13178.
CPU: AMD Ryzen 5 3600
GPU: NVIDIA GeForce GTX 1660
Windows 10 64-bit
Updated by TheawesomeMCB about 3 years ago
notkate wrote:
Same issue here. Save states work as expected, and memory card saves work as long as the program stays open.
Example: playing Pikmin 2 (ID: GPVE01), the game autosaves at certain points. Resetting the emulation allows me to load from the autosave, but completely closing Dolphin "resets" the memory card file to when it was first created.
The emulator window says in the upper left corner that it has written to the memory card file when appropriate, but checking the actual file shows it was last edited when it was originally created.
I get this message using "verify" on the iso (not sure if relevant, but can't hurt):
This disc image is in the NKit format. It is not a good dump in its current form, but it might become a good dump if converted back. The CRC32 of this file might match the CRC32 of a good dump even though the files are not identical.Also using 5.0-13178.
CPU: AMD Ryzen 5 3600
GPU: NVIDIA GeForce GTX 1660
Windows 10 64-bit
Yeah I'm having the same issue with pikmin 2. Sometimes it just wont save. Dolphin will say that it has saved but according to windows explorer the file will remain unchanged. It's really weird... And driving me CRAZY!
Updated by Miksel12 about 3 years ago
Does this happen with GCI Folder and normal memory cards?
Updated by TheawesomeMCB about 3 years ago
Miksel12 wrote:
Does this happen with GCI Folder and normal memory cards?
Idk, all i know is that it doesn't always save when doing the memorycard.raw files. There doesn't seem to really be a pattern to it when it does work and when it doesn't. (Sorry for late reply, been busy)
Updated by Techjar about 3 years ago
What directory are you putting your memcard files in?
Updated by TheawesomeMCB about 3 years ago
Techjar wrote:
What directory are you putting your memcard files in?
Some dedicated folders, I have actually found how to replicate it.
So let's do pikmin 2 for example.
- When you first create the memory card you do slot A and choose your folder where you want to save it. We will name this 1.raw
- Let's start the game and it wants to create a save for pikmin 2 files, we say yes. We then see that the promot the game was saved to 1.raw.
- Let's do day 1 as usual.
- After comleteing day 1 we save the game. It says it saved to 1.raw.
- Let's stop the emulation and launch it again. It says we are on day 2.
- Now lets go do day 3, after day 3 we save the game but it says 1.usa.raw, then we exit the game. We then launch the game excpet this time it says we are on day 2, even though it just saved but it saved to the usa one instead of the normal raw one.
- Okay that weird lets start the game again after doing day 3 again lets save. It says it saved the game to 1.usa.raw.
8.Launch the game and it will STILL be on day 2. - So lets close dolphin completely. And relaunch it after doing day 3 itsaves it says saved to 1.raw
- Now let's relaunch the game, it says were still on day 2.
I could go on and on, but it looks like after you close the game and relaunch it, that's when it stops saving correctly after that.
Updated by TheawesomeMCB about 3 years ago
Correction:
- Now lets go do day 3, after day 3 we save the game but it says 1.usa.raw, then we exit the game. We then launch the game excpet this time it says we are on day 2, even though it just saved but it saved to the usa one instead of the normal raw one.
Acutally meant to say: 6. Now lets go do day 3, after day 3 we save the game but it says 1.usa.raw, then we exit the game. We then launch the game except this time it says we are on day 2, even though it just saved but it saved to the 1.usa.raw instead of the normal 1.raw.
Updated by TheawesomeMCB about 3 years ago
Correction again: That was step 6 we were correcting on the previous one. Not step 1.
Updated by Techjar about 3 years ago
Ah, I think I see the problem. You are naming your memcard files without the region suffix. There's some bugginess and unintuitive behavior when you do this that we still address in this area, but if you actually name your card 1.USA.raw in the UI it should work correctly.
Updated by TheawesomeMCB about 3 years ago
Techjar wrote:
Ah, I think I see the problem. You are naming your memcard files without the region suffix. There's some bugginess and unintuitive behavior when you do this that we still address in this area, but if you actually name your card 1.USA.raw in the UI it should work correctly.
Yeah I changed my memory card location to the normal one I use, and it did have the USA suffix. And it works normally, so that's my issue fixed (Thanks!) and yeah that seems to be a bug that if you don't have the suffix in it won't save properly, however this wasn't my thread so maybe the OP's and notkate is having the same issue maybe?
Updated by Techjar about 3 years ago
Yeah I'm going to guess probably the same issue. Dolphin is supposed to automatically fix the suffix, but it seems to not be doing it at the right time.
Updated by TheawesomeMCB about 3 years ago
Techjar wrote:
Yeah I'm going to guess probably the same issue. Dolphin is supposed to automatically fix the suffix, but it seems to not be doing it at the right time.
Which explains when I was doing this on old version's it didn't have this issue. So there was a point in time that an update broke it somehow.