Choose the core, not only the system
Each supported console has several cores with different accuracy. A TAS movie is tied to the core it was recorded on and may desync on another.
Config > Cores
BizHawk is built for determinism: save states, frame advance and Lua scripts. It is the wrong emulator for casual play and the right one for a TAS.
Install **BizHawk**, pick a **core** per console, then use **frame advance** and **save states** as the basic workflow. Determinism only holds if the same core and the same ROM are used.
Each supported console has several cores with different accuracy. A TAS movie is tied to the core it was recorded on and may desync on another.
Config > Cores
Frame advance, pause and save state are the tools a TAS is built from. Everything else in the interface is secondary to these three.
Space pause, frame advance, F5 save state
The input display shows every button per frame. It is what makes a recorded run reviewable by someone else.
View > Input display
The Lua console runs scripts that read memory and draw information on screen. That is how a run shows its own timing or a hit counter.
Tools > Lua Console
A recorded movie file does not contain the ROM. Store the movie next to the exact file it was made with, or the playback desyncs for everyone else.
Play the movie back from the start and confirm the same result. A run that only works live is not verified.
Different core, different ROM revision or a changed setting. Restore the exact setup.
The emulator is running, not paused. Pause first.
A version mismatch against the emulator API. Use a script for the same release.
Fast-forward without audio, or raise the buffer.
It works, but RetroArch is smoother for casual use.
Yes. The community publishes its verification rules and the exact core list.
Delete the movie and state files to remove the work. The emulator configuration lives in its own folder and can be reset from the config menu.
Free · no account needed · tracks your progress