Something strange has recently started happening to me with FCEUX 2.1.4a. When I stop recording a movie and watch from the beginning (to check my progress, etc) sometimes there will be a reset recorded that wasn't supposed to be there. They seem to be at points where I had previously stopped recording or switched to Read-Only Mode. When I go into the actual movie file to check it out, the changed line looks like:
|2|.L......|........||
So I change the 2 back to 0 and save the file, but then none of my savestates work, so I have to watch the movie again and make new savestates. Obviously, this is starting to get on my nerves and I'd like to know what's causing this, especially since this never happened until recently.
I've had it happen 4 times during the (currently ongoing) Dream Team Contest 4. I began to get a theory, and I think I've tracked it down.
When you get to the end of the movie, save a state at its last frame, then load this state, you will get an erroneous reset recorded.
Record a trivially short movie (less than a second if you feel like).
Replay it in read-only. Out to the last frame.
Once at the last frame of the movie (frame count reads 56/56, for example), save state.
Load this state in read+write mode.
Record another second or two.
Now replay. ... Where did that reset come from?!
At other times, I had an incomplete record made. That is, despite having recorded several hundred frames at some point, when I replay the movie, those frames did not appear in the movie file at all. Not sure if it's related.
Found the cause of this problem.
It appears only when you use "Play Movie From Beginning" feature (Shift-R by default).
Some TASers manually switch Read-Only mode and load savestate near beginning to watch their progress, thus they didn't meet this bug.
Now it's fixed in FCEUX 2.1.6 which will probably be released next month.
Details:
When you press "Play Movie From Beginning" while in Read+Write mode, the feature resets emulator and then switches to Read-Only mode.
Now it first switches to Read-Only mode and then resets emulator.
Definitely not related. If you can track the problem, I may try to fix it.