Various TAStudio desyncs

Summary

A TAStudios project file contains greenzone savestates which store either incorrect or lacking data. Using such states leads to having desyncs.

• An exported bk2 leads to desyncs in the first round.
• At some point (around the frame range of 5000..7000) I increased savestate history buffers, because I didn't like the movie being replayed from near the beginning. I agreed to try to keep the old states.
• There are greenzone inputs which still store the right data for the rest of the TAS to be replayed as intended: the greenzone savestates at frames 7528 and 7544. Other greenzones, like 7512, lead to desyncs.

Besides manual input, three Lua scripts were used to produce this TAS: Columns3-Lua.zip
Each script was operating primarily at 800% emulation speed (~340 fps).

Core: GenPlus-GX
Game ROM: Columns III - Revenge of Columns (U) [!]
SHA1: 8E52A5D0ADBFF3B2A15F32E9299B4FFDF35F5541
MD5: 441B7E9C9811E22458660EB73975569C

This is a heisenbug. I don't have a list of steps to reproduce it.

Host env.

• BizHawk 2.11; Win10 Pro 21H2; AMD/NVIDIA

Begin with the linked TAStudios project file and the supplied Lua scripts, then compare replay behavior for the greenzone states around frames 7512, 7528, and 7544 using GenPlus-GX. Done means finding a reproducible cause for the incorrect or missing savestate data and confirming that exported or replayed movies no longer desync.