This happens in Pokemon XD, Pokemon Colosseum, and Fire Emblem: Path of Radiance for me. All games are NTSC, United States. I verified them with Dolphin before posting, and Dolphin cannot find issues with the dumps.
Essentially the games get stuck in a loop of title screen, "You need a new file", "You can't save", back to the title screen. Rinse, repeat.
I was told that this could be fixed by deleting the memory card files in the folder that was in my Documents (I deleted all of them, including the JP and PAL folders and the SRAM file) to force Dolphin to make new ones, but that has not solved the issue. The games continue to not recognize the new memory card file and are stuck in the loop.
The only significant difference between the messages for each game is that Fire Emblem informs me that there will be no way to save, even if a memory card is inserted later. Which is fine - I suppose I can use save states - but the game doesn't advance past the title screen, same as the Pokemon games. (Also the Internet tells me that save states don't work very well in Pokemon.)
I'm running Dolphin 5.0-10740.
If there's any way to fix this, please let me know!
Essentially the games get stuck in a loop of title screen, "You need a new file", "You can't save", back to the title screen. Rinse, repeat.
I was told that this could be fixed by deleting the memory card files in the folder that was in my Documents (I deleted all of them, including the JP and PAL folders and the SRAM file) to force Dolphin to make new ones, but that has not solved the issue. The games continue to not recognize the new memory card file and are stuck in the loop.
The only significant difference between the messages for each game is that Fire Emblem informs me that there will be no way to save, even if a memory card is inserted later. Which is fine - I suppose I can use save states - but the game doesn't advance past the title screen, same as the Pokemon games. (Also the Internet tells me that save states don't work very well in Pokemon.)
I'm running Dolphin 5.0-10740.
If there's any way to fix this, please let me know!
