Ya, it makes no sense. When first step goes off your guy goes charging straight down the field so much he basically has to stop and turn around so that the OT can start blocking him again instead of the DE turning as much as he can as soon as he is on the side of the OT.
Wow, watching that replay, the RDE (the one moving at the right angle) is lined up in the neutral zone. He's almost a full a yard in front of the rest of the d line.
The LDE, NT and DT are lined up on the 22, the RDE is almost fully on the 21. L.O.S. was the 20. That could be whats causing it maybe, like its reading him in the wrong spot so it makes him play weird.
EDIT:
I was going off the center of the dots, not the front when I said the yard lines....
1 - At the snap the DE estimates the direction the OT will move, and guestimates the distance he will need to travel to get "around" him.
2 - DE's Jump The Snap and/or First Step fires - he travels the same distance he estimated he needed to travel prior to the snap, however the LT clearly either fails his vision check or otherwise is nowhere near quick enough to track the DE.
3 - DE doesn't get another vision check until 3 frames later.
4 - DE completes his initial "charge" and then turns and kills the QB.
It doesn't look pretty but it is pretty much working, and I very much doubt that it's any particular bug other than just a freak combination of outputs and inputs which makes it look ungainly.
Essentially the issue is the number of vision checks the DE makes "after" he beats the OT is pretty static. Hes covered those 5 yards before he gets chance to even think about moving towards the QB.
Originally posted by Koncorde Simple answer is thus: Essentially the issue is the number of vision checks the DE makes "after" he beats the OT is pretty static. Hes covered those 5 yards before he gets chance to even think about moving towards the QB.
If that's the case then adding an earlier vision check when first step or jump the snap fires could make sense since a player wouldn't really do what the DE's are sometimes currently doing.
I wouldn't complain. Looks like your guy pretty much smoked that one. I'd be happy as hell if my guy was in there so quick he had time to comb his hair.
Originally posted by Randy Lykuhmynx If that's the case then adding an earlier vision check when first step or jump the snap fires could make sense since a player wouldn't really do what the DE's are sometimes currently doing.
You've got a chicken/egg problem. A - the DE doesn't know how far the LT will run until you move. B - the LT doesn't know where to move until you run. C - the DE doesn't know the LT will fail his vision check, jump the snap or first step will fire. D - the LT doesn't either.
When they fire you get the issue then: A - the LT's previous routing is not sufficient. B - the DE has overcompensated.
If you put in a vision check for the DE he wont make a better angled run, what he would need is a vision check in the middle of his initial burst. However he still wouldn't change direction until he was able to complete his "move".
Generally speaking over pursuit is pretty common for DE's in general - it just looks bad in GLB because of the LT's complete inability to even make an effort at stopping the guy and the somewhat extravagant amount of distance the DE can cover in that fraction of a second.
Wouldn't a vision check on tick 3 for his position relative to the OT and QB, allowing the DE to start turning earlier because he can see he is behind the OT, be better than the DE seeing this fact on tick 5? From tick 4 to 5 the DE is actually continuing to accelerate even though every player on the field is behind him.
Using the snap awareness script the DE should at least have a chance to tell he's behind the OT, and start turning, instead of continuing at a high speed away from the QB
Edit: I just wanted to say, I don't think you're wrong. Maybe there isn't a way to fix it either but I think there could be ways to at least improve it, rather than penalize DE's when their "special powers" happen.
Unfortunately I don't know how many ticks "first step" actually functions. It might be that when the SA fires the player has to reach his max speed before attempting any other motion - in which case the failure is with the SA functionality and not the vision checks at all.
It's less a penalty and more of just a visual oddity. It's also hard not to prove that it isn't in some way down to a lack of vision or a failed vision check so would require more looking at (my personal though is the SA function somehow plays into it).