This game has a built-in timer for races and shows your time on a leaderboard after each track, which means it's possible to compare speedruns using the in-game clock rather than a real-world clock.
The distinction is important because there are certain optimizations for real time vs in game time. Example 1: Purchasing Radial tires takes more real time than it saves in a race. Example 2: Slowing down before crossing the finish line saves real time but loses in-game time.
There are certain advantages to using in-game time vs real time for speedruns:
In-game time:
- Menuing doesn't matter
- Focus optimization on the races themselves
- Doesn't include lag frames
- 0.1s second timer is precise enough
- Common timing method for games with a built-in timer
- Manually recording and calculating total time Example games: Punch Out, Sonic series, Goldeneye 007
Real time:
- Optimizations/Routing beyond races
- Common timing method
- Easy to time
- Menuing is stressful Example games: Super Mario Bros., F-Zero, Tetris Attack
I am heavily in favor of real time because it's easier to time, and it has more opportunities to show skill (e.g. menuing, routing options). Although, I can see an argument for in-game time, so I'd like to open the floor for discussion.
For clarity - the runs presently starting when name is selected and ending on finish of last race = real time. If so, that's what I think makes most sense, since there's not competition for finishing any particular course in fastest time- and IGTs don't sum to best progression through the entire game, imo.