User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > This WR Screen happens way to much.....look at this BS!
Page:
 
chief31
offline
Link
 
Originally posted by NCAACAL
this is not a bug you dumb asses. its a quick pass. learn to look at the game recaps.


The ball is thrown before the snap. No offensive player has moved on the first frame, yet the pass is in the air on the first frame.

Rather the replays are accurate, or not, they aren't supposed to be this out of synch.

Maybe the bug is in the replay, and he text was right. Either way, there is something wrong with this.
Last edited Nov 30, 2008 05:31:27
 
raiderdav
offline
Link
 
What do you expect? It was a WR screen to Michael Crabtree. This play is working as intended unless the opponent is Oklahoma or Baylor.

 
Black Peter
offline
Link
 
Wonder if Bort can run some stats on how often it's used now. Seems to have become the meat and potatoes play for a whole lot of offenses in games I watch. Kind of absurd, but whatever.
 
Jack Del Rio
offline
Link
 
Usually on any kind of screen the D linemen at least ENGAGE the O linemen. To suggest that the QB has already put the ball in the air before anyone can take a step is retarded.
Still a bug.
 
tautology
offline
Link
 
I'll admit that it does seem a bit much for the QB to get off a pass before the O-line can even move...much less the defense.
 
Checkmate187
offline
Link
 
Read the script about the play. QB pass to WR. This is the same thing as seeing a TD play but it stops before the ball gets there.... this just happens to start after the play begins.
 
Link
 
Originally posted by chief31
Originally posted by NCAACAL

this is not a bug you dumb asses. its a quick pass. learn to look at the game recaps.


The ball is thrown before the snap. No offensive player has moved on the first frame, yet the pass is in the air on the first frame.

Rather the replays are accurate, or not, they aren't supposed to be this out of synch.

Maybe the bug is in the replay, and he text was right. Either way, there is something wrong with this.


It seems like the bug Bort tried to fix earlier:

- Added code to make sure QB drops back on pass plays for at least a couple ticks, to avoid the "insta-snap-pass" that's been coming up recently, especially for slow QB's.


It is pretty obvious that QB doesn't drop back on this pass play for at least a couple ticks consider all O-linemen do not move on first frame.

Last edited Nov 30, 2008 11:06:23
 
tautology
offline
Link
 
It's a pretty fine line on the WR screen...if you slow it down too much, it would become a total waste of time as the defense would smother it every time.

It does seem to me that slowing it by 1 tick is warranted though...no QB is that quick.
 
Frigoc1
offline
Link
 
What would you put into offensive AI to run it?
 
tjsexkitten82
offline
Link
 
This is a bug. "The replays aren't accurate" isn't really an adequate response when your LG is snapping the ball parallel to the line of scrimmage. That breaks so many rules of football, there's no way Bort can allow this to continue. If it's supposed to be a quick throw, it would clearly take more time to get the ball back to the QB and then have him throw it. In this replay and others like it, the ball does not move backwards as it would in a snap to the QB at any point. It shouldn't rocket directly from the LG to the WR.
Last edited Nov 30, 2008 11:15:50
 
tautology
offline
Link
 
Originally posted by tjking82
This is a bug. "The replays aren't accurate" isn't really an adequate response when your LG is snapping the ball parallel to the line of scrimmage. That breaks so many rules of football, there's no way Bort can allow this to continue. If it's supposed to be a quick throw, it would clearly take more time to get the ball back to the QB and then have him throw it. In this replay and others like it, the ball does not move backwards as it would in a snap to the QB at any point. It shouldn't rocket directly from the LG to the WR.


Otherwise DEs will need to be even faster to get the sack...


I do agree, though...it's a bit too fast.
Last edited Nov 30, 2008 11:19:00
 
chief31
offline
Link
 
It seems like something about the order of how the scripts are read is going out of order, as if it is reading the pass, before it is reading the snap maybe?
 
OttawaShane
offline
Link
 
Originally posted by chief31
Originally posted by NCAACAL

this is not a bug you dumb asses. its a quick pass. learn to look at the game recaps.


The ball is thrown before the snap. No offensive player has moved on the first frame, yet the pass is in the air on the first frame.

Rather the replays are accurate, or not, they aren't supposed to be this out of synch.

Maybe the bug is in the replay, and he text was right. Either way, there is something wrong with this.


agreed.
 
ryan_grant-25
offline
Link
 
Originally posted by The Avenger
This TD by the WR to help win the game against us!.

Its a new DIRECT SNAP to the WR....

PLEASE FIX BORT!

http://goallineblitz.com/game/replay.pl?game_id=253578&pbp_id=6995471

P.S. same game where our kicker misses 2 extra point kicks from the 2 yard line out of 3 attempts...he made 18 for 18 the game before!!



maybe if you cry enough, it will drown in your tears.
 
whoshotjr
offline
Link
 
Originally posted by Toriq
Wonder if Bort can run some stats on how often it's used now. Seems to have become the meat and potatoes play for a whole lot of offenses in games I watch. Kind of absurd, but whatever.


Yeah it's typically a play that works in moderation in real life and then has diminishing returns when used too much. I remember Dick Jaroun being guilty of overusing it with the Bears, it would work a couple times and then get shut down...but he would just keep going to it. I guess that's what you do with Cade Mcnown at QB.
 
Page:
 


You are not logged in. Please log in if you want to post a reply.