Post subject: Bug with loading old savestates in read+write
Skilled player (1216)
Joined: 8/29/2014
Posts: 301
Using Dolphin 5.0, I noticed that sometimes when I accidentally load an older savestate in read+write instead of read-only, I lose all progress after that savestate without any way of getting it back. Loading a newer state in read+write and then loading any state in read-only after the one that caused the bug will simply load it in read+write, and loading any state from before the bug in read-only will not retain the progress made in newer savestates. Even loading a newer savestate in read+write and saving the dtm will not save any of the progress.
Skilled player (1216)
Joined: 8/29/2014
Posts: 301
Actually, it turns out that I was TASing new progress in read-only when it wasn't getting saved(the reason it always coincided with accidentally loading a state in read+write was because I thought I was switching from read+write to read-only when the inverse was actually happening). The teal frame counter looks like it is simply in read+write once it goes beyond the end of the movie in read-only, whereas most emulators continue to display it as "101/100 (movie finished)" or such. Currently it appears that there is no way of distinguishing whether you're in read-only mode after a completed movie or read+write.