Thinking of changing the timing method to clear confusion; I've done some calculations based on only track finish time added from rewatching the runs and here are my results:

Whitzwolf: 2.30.20 1.56.65 2.15.01 2.24.63 2.04.43 2.35.75 2.32.01 - 2.34.63 (As I skipped the leaderboard too fast to see my time I will use the slowest time) 2.01.09 2.10.29 2.46.47 2.20.87 2.50.74

23.325.576 23.330.76 Final time: 28m30s76ms

mcilrain: 2.28.32 - 2.28.99 (leaderboard not clear) avg = 2.28.65 1.55.90 2.09.81 2.20.25 2.06.21 2.32.67 2.30.72 1.59.21 - 2.03.34 (leaderboard not clear) avg = 2.01.27 2.11.26 2.35.44 - 2.39.19 (leaderboard not clear) avg = 2.37.31 2.16.14 - 2.17.67 (leaderboard not clear) avg = 2.16.90 1.24.14 + 1.21.20 = (no leader board but from the laps at race end) 2.45.34

avg : 23.290.629 avg : 23.296.29 Final avg time: 27m56s29ms

fast : 22.346.527 fast : 22.351.27 Final fastest time: 27m51s27ms

slow : 23.295.635 slow : 23.301.35 Final slowest time: 28m01s35ms

I haven't been able to accurately do Jck's time due to how fast he skips through lol

My only gripe with this is if we do only calculate this method then it kind of removes a little the spirit of speed running as inbetween menus would not count. It does however very easily simplify how fast we all are. I'm not sure if time is tied to FPS however.

Hi, I'm glad you're back! I was starting to lose hope, lol My total tracks time should be 27:50.

I agree with you: if we only calculate track time it means that the player can takes his time in-between the races and I think this is against the spirit of speedrunning a full game where you have to overcome difficulties not only from the game itself, but also from his UI. IMO the current rules are perfect: time starts at the selection of your bike before the first race and stops when you cross the finish line of the last race. It's easy and straightforward and it doesn't need a lot of measurements and calculations.

If we really want to keep track of lap times I suggest to do it track by track in a "Levels leaderboard" as many other games do, taking advantage of the Time Attack mode built-in in Moto Racer.

About the FPS, times are not directly tied to FPS, but grip is. Running the game with -FrameRateMax90 or -FrameRateMax0 (unlimited framerate) increases the grip allowing to easily lower you times. Therefore I would enforce the usage of the standard (at least in the GOG version) -FrameRateMax60 command line parameter.

I just read your post in the other thread. I understand the reasoning behind those calculation now. I still think time should be calculated as I stated before, but the "total track time" could be shown in a new column along with the "real time", as for example in Mario Kart 64 leaderboard (https://www.speedrun.com/mk64).

I'm happy to switch the timing method now and rankings to total real completion time. The hard mode rankings currently follow this and thus do not need to be adjusted.

As for the FrameRateMax rule I'm not sure how we would enforce that but I do like the idea.

I'm personally happy with both including or excluding menu interactions or loading times. When I submitted my Easy run back then it wasn't clear what method was used so as long as it's consistent and doesn't require much player or mod input, I'm all up for it :P

Enforce the FrameRateMax rule is actually quite easy because with high framerates the bikes stay almost vertical even in the the tightest corners, but in fact I cannot exclude that some settings combination can solve the visual glitch while retaining the advantages.

Ananas is the wise one: consistent and effortless is the way! :D