RUN STARTS AT 3:13

There is a glitch with the recording in the beginning of the run, but after the run finishes, I explain in detail in the video what occurred.

You need the video link context to understand the following: I used a clip that had the 'jump start' glitch occur (that had the OBS recording start from when I clicked the "start" button), lined up both audio tracks, of the WR run and a jump start glitch run, so they were the same audiowave on top of each other, used the full recording as a marker for when the brake lights went off on the hopper (aka the start of the run, when power gets put to the wheels), and started the time for the WR clip (that had audio recorded, LUCKILY!) there, synced up in audio with a run with a beginning recording that had the jump start glitch. The jump start glitch itself did not affect timing of the WR run, but did affect audio and UI appearance.

The timer is synced to each frame in the video, so 27 frames @ 60 FPS equals 450 MS