1am MKPC thought lol
Page : 1
On 2024-09-17 at 07:40:54
Typing this at around 1:40am and when I'm in this sleepy state I have random and foggy thoughts about various things, and I was wondering about the fact that MKPC calculates times at the millisecond but isn't any time unit lower than 1/240th of a second always irrelevant in this context since the game's FPS can't be set above 240 anyways?
@Wargor
@Wargor
9
1
1
3
2
2
On 2024-09-17 at 09:12:12
Typing this at around 1:40am and when I'm in this sleepy state I have random and foggy thoughts about various things, and I was wondering about the fact that MKPC calculates times at the millisecond but isn't any time unit lower than 1/240th of a second always irrelevant in this context since the game's FPS can't be set above 240 anyways?
Ce qui est marrant c'est que chaque frame est équivalente à 0'00"067 secondes in game (même si tu peux monter jusqu'à 240 fps le temps reste basé sur les 15 fps lol)
Ce qui est marrant c'est que chaque frame est équivalente à 0'00"067 secondes in game (même si tu peux monter jusqu'à 240 fps le temps reste basé sur les 15 fps lol)
1
1
On 2024-09-18 at 01:14:22
Même si tu peux monter jusqu'à 240 fps le temps reste basé sur les 15 fps lol
Ah, ça par contre je ne le savais pas, mais ça fait du sens vu que c'était le nombre de FPS du jeu à l'origine... Intéressant!On 2024-09-18 at 14:08:35
The 1AM thoughts... Relatable asf lmao
1
2
1
On 2024-09-19 at 18:10:23
What's even more interesting is that the last time digit (aka the number of ms) varies a lot in TT records, even though this theoretically shouldn't happen if the FPS is truly capped to 15... So, I'm wondering how this is possible, is it because device performance/lag causes the FPS to not always be constant?
Definitely can't wait to have an answer from Wargor himself.
Definitely can't wait to have an answer from Wargor himself.
On 2024-09-19 at 19:15:32
_
if you increment by 0.06 (1/15th of a second) you can get any number in the ones place, so yes, the timer only updates 15 times a second, but that isn't apparent unless you have multiples of 1/15 memorized.
if you increment by 0.06 (1/15th of a second) you can get any number in the ones place, so yes, the timer only updates 15 times a second, but that isn't apparent unless you have multiples of 1/15 memorized.
1
On 2024-09-21 at 02:55:07
if you increment by 0.06 (1/15th of a second) you can get any number in the ones place, so yes, the timer only updates 15 times a second, but that isn't apparent unless you have multiples of 1/15 memorized.
On 2024-09-21 at 20:14:41
if you increment by 0.06 (1/15th of a second) you can get any number in the ones place, so yes, the timer only updates 15 times a second, but that isn't apparent unless you have multiples of 1/15 memorized.
What time did you calculate on?
On 2024-09-26 at 20:59:31
if you increment by 0.06 (1/15th of a second) you can get any number in the ones place, so yes, the timer only updates 15 times a second, but that isn't apparent unless you have multiples of 1/15 memorized.
What time did you calculate on?
On 2024-09-26 at 23:10:26
tu veux pas finir fwaysKart 4 plutôt
On 2024-09-26 at 23:11:38
la coupe fwies
On 2024-09-26 at 23:54:03
tu veux pas finir fwaysKart 4 plutôt
Mec on attend toujours MK2(P)...
Yesterday at 19:14:32
Typing this at around 1:40am and when I'm in this sleepy state I have random and foggy thoughts about various things, and I was wondering about the fact that MKPC calculates times at the millisecond but isn't any time unit lower than 1/240th of a second always irrelevant in this context since the game's FPS can't be set above 240 anyways?
sorry, you are not getting an answer from wargor!
part im explaining:
https://github.com/tmalahie/mkpc/blob/b89bb80ffe85c751b193fa688ddeb154481ed3d1/scripts/mk.js#L17161
oversimplifying as hell, not accurate
the game adds a value to your timer 15 times per second.
its almost always 67ms (1 frame at 15fps), unless you cross the finish line checkpoint.
when you do, the game compares your current and previous position and looks up how early or late you crossed the finish line checkpoint between the positions and adds a fraction of a frame to make it more accurate.
example below:
this is why top boo lake times on 150cc almost always are a multple of 0.067s because most of the time the player crosses the finish line at the exact same angle (in this case it's adding a whole frame for the finish line, it doesn't have to be tho)
sorry, you are not getting an answer from wargor!
part im explaining:
https://github.com/tmalahie/mkpc/blob/b89bb80ffe85c751b193fa688ddeb154481ed3d1/scripts/mk.js#L17161
oversimplifying as hell, not accurate
the game adds a value to your timer 15 times per second.
its almost always 67ms (1 frame at 15fps), unless you cross the finish line checkpoint.
when you do, the game compares your current and previous position and looks up how early or late you crossed the finish line checkpoint between the positions and adds a fraction of a frame to make it more accurate.
example below:
this is why top boo lake times on 150cc almost always are a multple of 0.067s because most of the time the player crosses the finish line at the exact same angle (in this case it's adding a whole frame for the finish line, it doesn't have to be tho)
2
1
Today at 07:20:32
Thats crazy ur parents let you stay up that late Typing this at around 1:40am and when I'm in this sleepy state I have random and foggy thoughts about various things, and I was wondering about the fact that MKPC calculates times at the millisecond but isn't any time unit lower than 1/240th of a second always irrelevant in this context since the game's FPS can't be set above 240 anyways?
Today at 09:11:11
You Get Sleepy at 1:00 A.M.???
Today at 10:27:48
You Get Sleepy at 1:00 A.M.???
fucking yes?
Page : 1