- 1,787
- 715
Lookism speed calculations:
1. Warren Chae's multi punch The calculation assumes that all of the punches moved in one single timeframe (0.08s), but there is no evidence supporting that. Each punch could've just moved in seperate timeframes (each punch moving in 0.08s) which would've been enough to blitz the other guy.
Plus, all of the punches don't even need to move that fast for the other guy to not be able to react to them. He's literally getting bombarded with punches, which would naturally reduce his ability to be able to react to attacks.
Decision: Getting rid of the calc (2 staff votes)
2. Piggy blocks a knife
This is just a variation of those old "Dodging punches from close range" calcs. The "piggy" character after performing this feat almost got killed by the dude with the knife which pretty much invalidates the calc as it assumes that the speed gap between them is like 40x.
Decision: Getting rid of the calc (2 staff votes)
3. Sinu kicks 5 fodders
edit: Looking at the feat closer, the dudes who get hit individually doesn't seem to be able to move nor react to the kicks, which actually does justify using one timeframe for all of the kicks. Homewer, the distance used is still really inflated. There's nothing to support that he pulled his leg back after every kick, so the distance should be 5 meters instead of 10.
The calc also uses 0.029s as the timeframe which was deemed as invalid in this thread.
Decision: Fixing the timeframe (2 staff votes)
4. Goo full moon slashes
Feel like I'm just repeating myself here but these multiple hit calculations are just insane. I don't see any evidence showing that all of the sword slashes happened in one timeframe. This calc is even worse because no timeframe can even be given to all of the seperate slashes as no one is getting blitzed here.
Decision: Getting rid of the calc (2 staff votes)
5. Shingen punches Masaichi
The calculation assumes that Shingen rotates his shoulder and punches the dude's hand in the timeframe of the guy's punch moving 3 cm. The scene itself invalidates this as we see that Shingen can almost fit his whole arm between his face and the dude's fist in the 4th scan, which means that Shingen moved away from the punch before punching it himself, which in turn invalidates the timeframe.
Decision: Getting rid of the calc (2 staff votes)
Small note: I didn't include this calculation in the thread as it already got recalculated here.
Viral Hit speed calculations
1. Viral Hit: Start of series Hobin low kickLike the "Piggy blocks a knife" calculation, this calculation implies that there's a 30x gap in speed between Hobin and the other guy, while we see that that's not the case at all in the full fight.
Decision: Getting rid of the calc (2 staff votes)
2. Hobin moves fast
The calculation has no pixel scaling, assumes almost all of the distances and uses calc stacking.
Also there's no proof that Hobin moved all the distance in the timeframe.
Decision: Getting rid of the calc (2 staff votes)
Manager Kim speed calculations
Jincheol park shoots a knifeThe reason why this calc is invalid is kinda similar to the Shingen Punches Masaichi calc, but it's less obvious. In the first scan we see the knife that was thrown at Jıncheol is right near Jıncheol's head. Homewer after Jıncheol shoots the knife away (the second scan) we see that his hand is positioned to be ahead his head, despite the first scan showing us that the knife was thrown is right near him. The calculation assumes that Jıncheol only moved his head away while looking at the position of his hand, we see that Jincheol must've moved his head back too.
This invalidates the timeframe used in the accepted calculation as we can't know if the knife got past Jincheol's head or not because his head isn't at the same plane as the knife by the time he shoots it away.
Decision: Getting rid of the calc (2 staff votes)
Questism speed calculations
1. Daniel moves fastThe distance moved by Daniel is inflated. He doesn't need to move his forearm more than 90 degrees to grab the dude.
Decision: Using 90 degrees forearm movement instead of 180 degrees (2 staff votes I think?)
2. Daniel dodges Sooyun's blade
The calculation uses 2 cm as the distance between the sword and Daniel's face, but we literally see in the full scene (specifically in this panel) that Daniel's face is nowhere near the sword when he blocks the hit. This can only mean that Daniel also moved away from the blade as he was moving his hand to block it, which invalidates the timeframe.
Also, looking at the scene closer, it seems like this is more of a Power Null/Damage Reduction hax rather than a speed feat, as he literally gets some sort of power boost that lets him do that in the scene.
Decision:
Staff Agreements: @Drite77, @Floxy178
Staff Disagreements:
Last edited: