Fast forward

Using the replay command

Besides manual save states, TMInterface provides a replay command that can be used to automatically replay a specific part of the race. If you have an input script loaded with load filename.txt, you can choose to replay its specific part by executing e.g: replay 6.89 where 6.89 is the time in seconds to which TMInterface will speed up the game and hand the control over to the player.

You can control the replay speed at which TMInterface replays the race in the Settings General tab.

The replay command will be persistent across race resets. Subsequent resets will also switch to using the nearest save state to your chosen time point, which is a big advantage over using the speed commands inside the inputs file.

To make sure you can comfortably prepare for taking over the control of the race, TMInterface will always make sure to show 3 seconds of the race before the takeover happens.

If you do not want TMInterface to replay the specific part anymore, you can execute replay to disable replaying.

Using speed commands

A more manual method of getting to a point in a script quickly is to add certain speed commands to speed up input replaying. This however will mean that your script always replays all of the inputs, which is not ideal. For this reason, it is recommended to use the replay command.

Given an input script:

0 press up
...
56.34 steer -10043

You can speed up the process for replaying the script by putting set speed commands into the file at certain timestamps, like so:

0 set speed 30 # Set speed to 30x at the beginning of the race
0 press up
...
56.34 steer -10043
56.34 set speed 1 # Set speed back to 1x after all inputs

Because timed commands are not subject to line ordering, you can also do the same at the end of the file:

0 press up
...
56.34 steer -10043
0 set speed 30
56.34 set speed 1

You can insert the set speed command anywhere in your scripts at any timestamp, depending on where you want in the run to reset the speed.