Rio de Janeiro, BrazilCrazy Targets' timer is inconsistent and therefore it's not used for the final time, instead we retime all runs to match the RTA (video time) so it can have a more consistent and fair time.
Hello. I was checking this leaderboard as a curiosity and notice that some emulators runs are kinda off the new timing method. I watched uniseth's WR and they splitted on the credits which is not the timing method anymore. I decided to go to framecount and roughly retimed it to 20:44 at 60 FPS with the method that was used on the Console WRs, if a moderator could check and fix this it would be cool.
Happy a good day and sorry for the post!
I was checking some runs on the leaderboard and notice the Any% 2P WR made by Thiag0 had the same video as Thibaudk's run, which was submitted and done on 2019, and I'd like to request to remove the run from the leaderboards to avoid any issues.
Original submission: https://www.speedrun.com/overcooked/runs/yw446v0z
Cheated run: https://www.speedrun.com/overcooked/runs/y98p89vz
The glitch itself is allowed since it uses the same idea as similar ones used in runs on the leaderboard, althought it isn't faster since the final time of the run is 15.433 (at 30 FPS) because, as Yummy_Bacon said, time starts on the first frame the play/restart button is pressed.
For the Survive category though it wouldn't be allowed once the game gets frozen and it would be a disadvantage with other runs which were done without glitches, specially because you could do it over and over instead of playing the mini-game itself.
If it gets allowed in runs, it'll definitely make 2-3 Skip easier, in theory
There is a 2-3 Skip where you use a bat to get on top of the level, it saves 10s althought it's really RNG heavy and nobody goes for it, about the Dpad stuff, kinda curious, did you unabled the Left+Right option from your Emulator or even with it desactivated you could do this?
Used Somewes.com to see the time it takes to the screen to turn black after the first input and it showed me 0.733, so if someone wants to start the time when it turns black, just put 0.73 on the LiveSplit or if the timing method changes, put -0.73 on LiveSplit, that's it I think.
We could try both things, althought even knowing how much time it takes to turn the screen fully black, we'll still framecount it from the first input given since final time somewes/YFT will give to you is based when you set the first frame, sadly it isn't like a LiveSplit or something around that.
I think the timing method could change since it's based on the first input frame, HOWEVER, it's not everybody who does have an inout displayer for that and so it makes retiming really hard and inconsistent, I'd like to suggest if it could starts on the first frame the screen gets black after selecting a file so it would be more consistent like this.
My idea is too add Loadless (Load Removed Time) as a timing method because I notice that some cellphones has slower loadings than others (don't have values yet because didn't retime them precisely, but this is something to be discuted before being added), and loading differences can be an issue due to the disadvantages between them, but again, before that, retiming science should be done and also see if it's worth it since retiming loadless is really hard and it consumes lots of time.
The other thing is about retiming itself, idk what program has been used by the moderators but I've got some different times from the program/site that I do use (which is somewes.com) so I'd like to know what am i doing wrong so I can fix that for future runs (along with the first/final frames as well)
Last thing is I think we could have more ILs, at least 30 levels since we have a category that goes from 1 to 30, but again, just a suggestion
