So I made leaderboards for all of the levels, but wanted to get opinions on the proper timing convention before accepting new runs.

My intent was to allow submissions of stage clears that are done under many conditions, which is to say a level clear could be done in a speedrun or individually with no further context. So I wanted a standardized timing that could apply for all stages.

The timing I want to propose is as follows:

• Starting with the 1st frame when the stage name is displayed. So "1st S T A G E" for stage 1.
• Ending on the 1st frame when the "C L E A R" text is displayed.

The ending timing is pretty standard at this point but this would adjust the starting time as allow submissions from either speedruns or individual level practice.

Runs would still be required to provide full context so that it is clear that Create mode or other methods aren't used to achieve the time, but not all of the mandatory video footage would be included in the leaderboard time. This would lead to the existing TECTONICS runs having their times adjusted.

Here is an example:

Kamey's run of 6:25 would be adjusted to become a 6:21.04

Also I have enabled decimals for the level runs.

It would be good to eliminate differences in loading times between models as a correct measurement method. It would also be nice to be able to apply for a level run in the middle of any% run.

I think it is necessary to scrutinize the time of level run.

However, some people may not be able to scrutinize the time at any% or other locations, so how about setting a rough start and end point?

Timer timing should be as you propose.

Do you mean we should use livesplits for speedrun?

What about starting speedrun? Yes, it's a good idea when the stage name is displayed. It's better to do this for Intelligent Qube because not all users have ps2 (disk speed - fast). And it's better to remove "Any% w/Warp" from Intelligent Qube because it isn't in I.Q Final.

Dima, I'm only talking about stage timing for individual level submission. So with the proposed timing method, someone could retime a gold split from a speedrun and submit that.

I just wanted to make a note about decimals. Since there are 30 frames per second, that means every 0.1s consists of 3 frames. The way I've been breaking it down further is X.X00s, X.X33s, & X.X66s.

NTSC is 30（29.97） or 60（59.94）fps but PAL is 25 or 50fps.

Those are too different.

Youtube is roughly 30（29.97）fps. So it is correct in NTSC case.（If someone send 60 or 50 or 25 fps record, I don't think retiming 30 fps record）

That's a good point. I don't think anyone has submitted PAL individual levels, but I will keep that in mind.