{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
5/11/2017 5:37:29 PM
2
Still feel like you're missing my point. The shots you missed were simply because regardless of the visual flinch or not, your aim was off. The shots you hit that looked like they should've missed were BECAUSE there was no actual flinch to the gun and where you were aimed the split second you first was towards their head/body respectively.
English
-
Here. Have a link. The second kill. The scope was most definitely pointed at his chest. It should've been a body shot. But then I came under fire. The muzzle experienced real flinch. And I got a headshot instead.
-
Ok, I'll counter your link with a link of my brother's this weekend, yours is sketchy btw, you could easily have dragged up knowing how far your aim was before shooting and got the kill, it happened way too fast to tell if you pulled up with your aim at the time of pressing the trigger to shoot. So not really a perfect example, even if I get why you'd think it was.
-
Edited by Doos: 5/16/2017 12:27:39 AMExcept it was my play. I remember distinctly being upset because I took the shot while knowing it wasn't aimed at his head. That's why I recorded it because it seemed crazy that I got the headshot. But I will see your link when you get it.
-
In sorry but absolutely not. The shots that hit but looked like they should've missed. I was way off. And being put under fire caused the flinch to move my muzzle where I hadn't even moved it yet and it landed the shot. When I fire and I am that far off from their head and I am not under fire and experiencing flinch. I miss. Every time. But being that far off aim and flinch is definitely what moved my muzzle because I hadn't yet. That is definitely flinch being real.
