Cybertron
offline
offline
Cybertron
offline
offline
Fuck this....it is a damn screen! He should just throw it every time!
https://glb2.warriorgeneral.com/game/replay/832386/1238562
https://glb2.warriorgeneral.com/game/replay/832386/1238562
atlbruce
offline
offline
Maybe the o-line needs to be able to block for more than 2 seconds for the screen to set up? There may be something in the code relating to that.
ellix
offline
offline
In each one the QB was likely 1 or 2 ticks away from throwing the ball. The receiver has to set his feet and then the QB will begin the motion of throwing the ball a few ticks later. If your Oline could hold up at all it would be fine.
Cybertron
offline
offline
Originally posted by ellix
In each one the QB was likely 1 or 2 ticks away from throwing the ball. The receiver has to set his feet and then the QB will begin the motion of throwing the ball a few ticks later. If your Oline could hold up at all it would be fine.
The QB should start to throw before the WR feet are set. He should throw the ball due to the pass rush, not wait for the WR to set his feet. If he is about to get crushed, he should throw the ball regardless.
In each one the QB was likely 1 or 2 ticks away from throwing the ball. The receiver has to set his feet and then the QB will begin the motion of throwing the ball a few ticks later. If your Oline could hold up at all it would be fine.
The QB should start to throw before the WR feet are set. He should throw the ball due to the pass rush, not wait for the WR to set his feet. If he is about to get crushed, he should throw the ball regardless.
ellix
offline
offline
Originally posted by Cybertron
The QB should start to throw before the WR feet are set. He should throw the ball due to the pass rush, not wait for the WR to set his feet. If he is about to get crushed, he should throw the ball regardless.
I agree with that, I'm only making the point that its working consistently as its currently implemented.
The QB should start to throw before the WR feet are set. He should throw the ball due to the pass rush, not wait for the WR to set his feet. If he is about to get crushed, he should throw the ball regardless.
I agree with that, I'm only making the point that its working consistently as its currently implemented.
BoDiddley
offline
offline
The biggest takeaway is that Beat Down fired on all three sacks. It's a thing of beauty when it actually fires
Cybertron
offline
offline
Come on...ridiculous! He is sacked 5 ticks after the WR is ready for the pass! 
https://glb2.warriorgeneral.com/game/replay/833237/1413939

https://glb2.warriorgeneral.com/game/replay/833237/1413939
Myrik_Justiciar
offline
offline
Originally posted by Cybertron
Come on...ridiculous! He is sacked 5 ticks after the WR is ready for the pass!
https://glb2.warriorgeneral.com/game/replay/833237/1413939
I think you need to up your OL's Tech a hair and it should buy you enough time to get the play to work.
Come on...ridiculous! He is sacked 5 ticks after the WR is ready for the pass!
https://glb2.warriorgeneral.com/game/replay/833237/1413939
I think you need to up your OL's Tech a hair and it should buy you enough time to get the play to work.
vipermaw82
offline
offline
Originally posted by Cybertron
Come on...ridiculous! He is sacked 5 ticks after the WR is ready for the pass!
https://glb2.warriorgeneral.com/game/replay/833237/1413939
Got scurred
Come on...ridiculous! He is sacked 5 ticks after the WR is ready for the pass!
https://glb2.warriorgeneral.com/game/replay/833237/1413939
Got scurred
You are not logged in. Please log in if you want to post a reply.





























