• Login
  • Register
  • Dolphin Forums
  • Home
  • FAQ
  • Download
  • Wiki
  • Code


Dolphin, the GameCube and Wii emulator - Forums › Dolphin Emulator Discussion and Support › Support v
« Previous 1 ... 24 25 26 27 28 ... 1196 Next »

Rules for using save states and memory card saves without corruption?
View New Posts | View Today's Posts

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Rules for using save states and memory card saves without corruption?
05-23-2022, 11:07 AM
#1
falconzinx Offline
Junior Member
**
Posts: 3
Threads: 1
Joined: May 2022
Are there any rules to follow when using save states so that memory card save files are not corrupted?
_____________________________
(description of problem)
It seems like on occasion,
when I frequently either save or load a state,
it becomes impossible to make a save on a memory card,
with an in-game message mentioning something along the lines of "memory card is corrupted".

When I try to make a new memory card file,
and load the state,
I still cannot make a save back into the new memory card file either.

When I load from the memory card again,
I'm able to return to where I last left off and can make a save state,
and then save back onto the memory card without any problems.
_____________________________

Is this kind of occasional memory card corruption from save states something to do with how the Dolphin emulator handles the save state and memory card data?
For instance, I notice that saves are claimed as successful in-game before the message of a successful memory card write pops up, 
implying I should be waiting for that message to pop up before closing the emulator.
Find
Reply
05-23-2022, 02:31 PM (This post was last modified: 05-23-2022, 02:33 PM by Shonumi.)
#2
Shonumi Offline
Linux User/Tester
**********
Administrators
Posts: 6,512
Threads: 55
Joined: Dec 2011
I'm not sure about the particulars, but from what I understand the issue of being unable to make Memory Card saves alongside save states generally tends to happen when the user relies exclusively on save states for most of their gameplay. At some later point, they try to make save via Memory Card and it fails.

I've never had this happen to me personally, so I can't say for sure why it happens in Dolphin. I think the best practices are typically as follows:

1) Use Memory Card saves as your primary method of saving game progress. Save like you would on a real Gamecube first and foremost.
2) Use save states as temporary saves. For example, use it to save your progress right before a difficult part of gameplay that you might rather not repeat (right before a boss battle, right tricky platforming, etc).
3) Use save states as a backup for Memory Card saves. Typically, I save via Memory Card, and before I close Dolphin I make two quick save states. This ensures that at least one type of save should be good so I don't lose any progress.

Basically, from what I've seen, any save state/Memory Card problems tend to come from an relying too greatly on save states. I have no idea, technically speaking, what causes this. I'm just basing my information anecdotally from what I've noticed from users over the years, so I could be wrong. At any rate, the points I listed above work well for me.
Website Find
Reply
05-23-2022, 03:27 PM
#3
falconzinx Offline
Junior Member
**
Posts: 3
Threads: 1
Joined: May 2022
Yes, I've been treating the normal Memory Card save method as the primary one of which I've also been backing up separately (Dolphin Emulator -> GC).
Save states are still pretty important to me though, given the use of this emulator on-the-go. 

I've found a thread here*  that might also help with the problem.
Apparently, I should be treating the order of operations as such:
  1. make a real save, then 
  2. make a save state.
or at least ensure that the save state isn't happening just before a memory card save.

As per that thread, I've also changed the save format to .gci to hopefully limit any memory corruption to individual files rather than a whole memory card.
___________________________
* (https://forums.dolphin-emu.org/Thread-memory-card-corrupted--43015) 
"I've broken my memory cards using save states on Windwaker. If you loaded a savestate from before you do a memory card save and then try and do a memory card save, it can corrupt the card. Try switching the type of memory card in Dolphin to the GCI folder and launch a game. It will decrypt the card and save everything as individual .gci files"
Find
Reply
05-23-2022, 03:31 PM
#4
Venomalia Offline
Member
***
Posts: 214
Threads: 10
Joined: Dec 2020
In my experience, this happens very quickly in Pokémon Colosseum, if you want to check it out.

I would advise you to choose between Memory Card or Savestate.
[Image: Ko--Fi-Support-red?logo=ko-fi] [Image: GitHub-Projects-lightgrey?logo=github]
Website Find
Reply
05-25-2022, 12:36 PM
#5
falconzinx Offline
Junior Member
**
Posts: 3
Threads: 1
Joined: May 2022
(05-23-2022, 03:31 PM)Venomalia Wrote: In my experience, this happens very quickly in Pokémon Colosseum, if you want to check it out.

I would advise you to choose between Memory Card or Savestate.

Is there a list of games where this "memory card corruption due to save state" problem is more likely to happen?
Find
Reply
05-26-2022, 11:19 AM
#6
vlad54rus Offline
Junior Member
**
Posts: 32
Threads: 2
Joined: Jun 2020
I've seen this happening in Sonic Adventure 2: Battle where loading earlier save state after memory card save was written prevents all saving afterwards.
Find
Reply
« Next Oldest | Next Newest »


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:


Users browsing this thread: 1 Guest(s)



Powered By MyBB | Theme by Fragma

Linear Mode
Threaded Mode