11-09-2020, 02:35 PM
(This post was last modified: 11-09-2020, 02:36 PM by ^aethy. Edited 2 times in total.)
(11-09-2020, 02:28 PM)Evan Wrote:That's because there was no "lock" .. in actuality he swiped too hard to the right, hence his crosshair being that far off in the end, but because the game lagged it froze mid-swipe at the point where his crosshair happened to be on his head. If you're swiping your mouse across someone then there's a pretty good chance it can land on them at some point lol.. it's literally just timing(11-09-2020, 02:22 PM)aeth0r Wrote:(11-09-2020, 02:18 PM)Evan Wrote:Yea.. and the deagle animation freezes.. how is that not lag?(11-09-2020, 02:05 PM)aeth0r Wrote: Clip 2/3 is clearly lag.. after the "flick" you see his crosshair land way past the guy.. he really just overswiped to the right but since the game lagged and froze on the frame where his crosshair happened to be on his head it looks like aimlock.
Clip 1 and 4 don't really prove anything.. like I said with certain commands the greenery part in the middle doesn't render
+1 unban
I gotta disagree hard on clip 3 being "clearly lag". Here is the frame of the video right before the lock: https://imgur.com/a/e6SJi3I
Here is the frame immediately after: https://imgur.com/a/xR4ImVb
After reviewing it more it definitely looks laggy, but it still looks like blatant aimlock.
The same thing also happens while he's shooting the guy standing still
It is probable that he lagged, but the problem still is that lag doesn't explain why his crosshair went from aiming upwards at the column the other guy was at to landing precisely on the center of the other guy's head, even in passing. I don't buy the idea that he lagged and his crosshair magically passed over the dude's head and only looks like its locking on due to lag and nothing else.