The game is maximally optimised now, I think we should have ms available for top times as it won't be long before WRs are not improvable by more than a second a time.

Agree! We should also update the category rules for more precise start and end time.

I'm proposing this:

• Timer starts on the first frame when donald's airplane starts moving when selecting a stage
• Timer ends on the first frame when the orb starts breaking OR when the boss starts moving down

@petaQ, looks like your last run is 15:24.933, not sure if you stop the time a bit late or if it's because of the youtube video quality. I've used https://somewes.com/frame-count/

My thoughts:

1. Plane starts moving at n+2 frames after 1/2 is pressed. Propeller disappears at left edge at n+115f and entire plane disappears at n+130. I think just using those reference points to precisely time runs is better than retiming: with both odd and even points available you can always extrapolate the button push frame from there even on a console run. If we were to insist on a retiming the more logical start point is gain of control when first stage screen loads.
2. You cannot use Magica coming down as timing end: there are some cases where that is delayed after the last hit through no fault of the player. I think orb break is sufficient.

YT insists on encoding at 30fps. I manually frame count my 60fps recording: if you want I can send that to you. :)

some runner would not have the input displayed or there might have some input lags too. but yeah just need any reference. for some games it's done when the screen fully turns black or something.

as long as it's clear and precise for everyone, probably it's doesn't matter when to start. Personally I like on a screen transition, it's visually precise. I agree it would be better when first stage screen loads but we would need to retime all the runs ahah

The "orb break" means the first explosion frame? we can always add screenshots or a video to explain where to frame cout. (e.g. https://www.speedrun.com/tom_and_jerry_the_movie_the_game)

Youtube has 60FPS option, my runs on youtube are 720P60

My res for OBS is smaller than that so I'll have to send you the raw instead.

I found good example of category rules made by @RadManFromMars https://www.speedrun.com/montezumas_revenge#Levels_1_-_11_SMS

We could include milliseconds for runs which are faster than 15:30, that seems like a good threshold. I am only a verifier though so I can't change any timing rules, that would be up to the full moderator to decide.

Yeah, this is definitely needed. I just submitted a 15:26, so that's 2 seconds off petaQ's time. A month ago we had a WR tie at 15:34. We're both close and there's not much time left to save in the run. I like your idea of only requiring milliseconds for sub 15:30 times.

Adam_ak and btrim are the full mods, but neither has logged in for over a month.

Oh I also see that the board is set up to not include milliseconds. I had kept it on Peta's run but I see now that it's not there on the main leaderboard. We can always go back and edit those times after the fact.