Rune Factory: ToD saves stopped working

[Layer72o]

So I managed to get the game working well enough and everything was going great for a few days, only I loaded it up today and my in-game saves were a session behind. It seems to work fine off that save and I can load from/save over it just fine, but the game refuses to accept save updates when loaded from the more up-to-date save state I have.

Haven't changed any system or emulator settings between getting the game working and now.
As far as I can tell it's not a write-only issue as the game loaded normally and other wii games save just fine. I have also tried a few other revisions and none of them solve this issue. Because someone will ask, the revisions are r7358, r7714 and 3.0-153.


Currently using the 3.0 x64 release of Dolphin
Dual core/idle skipping enabled
JIT
DSP HLE
Scaled EFB copy
EFB copies to texture
External frame buffer disabled
Per pixel depth/fog disabled
OpenMP texture decoder enabled

PC Specs
WinVista 64
i7 920 2.67GHz
6gb ram
GeForce GTX 260

[Layer72o]

In game saves are not updating at all now. They appear on the menu when I hit save, but they aren't loadable and the list of saves just reverts to a listing from the other day when i reopen the emulator.

[Chaoticy]

I started my game this morning to find out that I'm having the same problem. I lost maybe 2 hours due to it.

The problem happened to me with 3.0-159, but after testing 177 just now it seems to save my game.

Only problem is that with 3.0-177 the game clears the code cache every 2 seconds causing it to stutter so bad that it's unplayable.

[Layer72o]

Do you use save states frequently by any chance? I tried continuing using only save states and performance degraded into a horrible mess.
177 does nothing to allow me to use in-game saves.

[Chaoticy]

Well I do try and use save states as often as I remember to, because the game randomly crashes and I don't want to lose too much progress.
But as for the game saves, I was able to save my game again after updating to 177 but I haven't tested it with more than one save due to the fact that it's pretty much unplayable like I stated before.

On that note though do you have the problem with the constant cache clearing? I'm kind of wondering if its just me since I haven't seen any other posts about it.

[Layer72o]

I don't have the cache clearing issue with 177.
I also don't think 177 fixed the saving issue for you. I was able to update my save files so long as the game time was really close to what the save was (+1~ minute in-game time), but any viable amount of playtime between saves would just cause them to not work (not an issue with them disappearing over time, an issue with them never being created).
To me, it feels as though the use of save states has somehow corrupted something. Not sure if I feel like devoting another 20-30 hours of play time to testing this theory.

[Chaoticy]

Well admittedly I didn't do very much testing with the whole save issue, but now that I know I'm the only one having the cache issue I'm going to see if I can figure out what's wrong here. If I do manage to fix it then I'll try some more testing with the saves.