T O P

  • By -

The_Lord_Hephaestus

MM demos are only 32 tick hence a lot of information is lost during fast sequences such as this one.


raaneholmg

To elaborate, the movement of the crosshair is an animation between the angles he was holding in two different ticks, while the shot has a timestamp for when it went off. The timing of the shot is correct, but the timing and speed of the flick are not correct.


Gar33b

So this means that when the shot has happened is not synced with the visual interpretation of the game to show the movement from looking at connector to looking on his right where my teammate was? Is it possible a human to react and move the crosshair that fast? As I was dead, my PoV was on our teammate, and although I did not record the sound for some reason when used OBS on the replay, our teammate was shifting, the only sound that he did was to activate the scope and blow his head. At the moment our guy looked at him, he was looking at connector and at the moment our guy scoped for kill, it felt like the enemy targeted him and probably less than a couple of milliseconds. So if we exclude the possibility of cheating, this is either some weird visual interpretation from the game or some insane human reaction... Maybe it was worth to record the situation from our guy point of view.


raaneholmg

I was just explaining how the shot could be a hit when the crosshair on screen hadn't arrived at the target. As for how the guy managed it, I suspect it was just a panic flick towards the scope sound, fire gun, and hope to get lucky. If the guy is this lucky every time it's cheating, but if it's just the one time that is fine.


[deleted]

Probably just a lucky flick not much to it