Nope, it wasn't. Just the wrong timing - must be saved at the end of the current instruction. Period.WedNESday wrote:From what I've read, it does seem like a variable not being restored properly.
That's what I always did - scanline 240, right before the VBlank. It doesn't matter if it's saved before or after VBlank though.I've never personally implemented savestates for WedNESday, so I've no experience with them. But shouldn't an emulator wait for the entire frame to finish before saving the savestate?