Emulator Issues #10598
Using save states breaks memory card saving in Pokemon Colosseum
Pokemon Colosseum (USA)
Game ID? (right click the game in the game list, properties, info tab)
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
What's the problem? Describe what went wrong.
Game fails to save to a memory card if a save state is loaded at any point after starting. This will happen even if you fully loaded into the game, save successfully, and then try and load a save state after the fact, this will prevent it from saving. The game claims the memory card in slot a is not the same memory card, and refuses to save as a result.
What steps will reproduce the problem?
Start the game and go through the initial intro, and save in Phenac city when possible. Create a save state in front of the PC, and close the game. Reload the game from the save state, and try to save at the PC. It should fail.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
5.0-5681 (Android 8.0)
Is the issue present in the latest stable version?
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
What are your PC specifications? (CPU, GPU, Operating System, more)
Android 8.0, Snapdragon 835, Adreno 540, Google Pixel XL 2. OGL, JIT ARM64.
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Including a save file and screenshot for convenience. This appears to be an Android specific issue.
#5 Updated by merauder75 almost 3 years ago
Hmm, I was actually testing against this on desktop and observed the same issue there. The pattern is pretty specific though in what triggers saves to fail. Essentially, save states will work only if they are from your current "session" of Dolphin in which you loaded the game. If you load the game, make a save state, and reload that state, it will still work. If you close Dolphin, then start the game and reload that same state, saves will break.
I noticed that running the game with all the debug logs turned on, it was reading memory card blocks 0-4, and 350-351 when it was displaying the error message (checking the header probably).
Star Fox Adventures (GSAE01) has the same issue.
1) Make a save state in-game
2) Save in-game
3) Load the save state
4) Save again, the game will say it's not the same memory card
1) Make a save state on the title screen
2) Load a save file
3) Save in-game
4) Load the save state
5) Try to load the same save file; again the game says it's not the same card
I assume it's because the timestamp doesn't match?
You can use the debug cheat code to skip past the opening scenes to be able to save right away: https://tcrf.net/Star_Fox_Adventures#Chapter_Select
PLease try this build: https://dl.dolphin-emu.org/prs/pr-8476-dolphin-latest-x64.7z
It may fix this issue.
The issue reported by Rena is just the usual problem that most games have with saving after loading a state that's older than the last memory card save. There's no way to fix that unfortunately, all we can do is just tell people to not do that.
As for the original issue report, this game actually will refuse to save even when your state is newer than the memory card save. This seems to happen if your SRAM has changed since the save state was created. This PR may address that issue: https://dl.dolphin-emu.org/prs/pr-7396-dolphin-latest-x64.7z
- Fixed in set to 5.0-12530
- Status changed from New to Fixed
Fixed in 5.0-12202 or 5.0-12530. https://dolphin-emu.org/download/dev/aee69b03c5677ceea600cf88321bf762dd2aecfa/