Edited by Lensar on Feb 14, 2012 12:01:17
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Only example I could find, QB lost in the backfield- NOT A BUG - CLOSED
Dr. E
online
online
Originally posted by Time Trial
http://www.goallineblitz.com/game/replay.pl?game_id=1836719&pbp_id=4870476
Seen stuff that before, but mostly on HBs. Usually they end up busting for a long gain some play that wasn't meant to go where it went. My guess is a high elusive setting along with build.
http://www.goallineblitz.com/game/replay.pl?game_id=1836719&pbp_id=4870476
Seen stuff that before, but mostly on HBs. Usually they end up busting for a long gain some play that wasn't meant to go where it went. My guess is a high elusive setting along with build.
IdRatherFlyFish
offline
offline
Thank you for opening up the build on that QB.
63 vision -- is that a little low for a scrambling-dot this age? I'm not a super-dot builder, so that's a serious question for the number crunchers.
I wonder this -- if that QB had put a move on the CB, or if the CB (one who made the tackle) had not been there, and this play went for a TD, would it still get posted as a bug?
Very odd play for sure, but we will need more replays before we can classify this as a bug.
Peace,
Fish
63 vision -- is that a little low for a scrambling-dot this age? I'm not a super-dot builder, so that's a serious question for the number crunchers.
I wonder this -- if that QB had put a move on the CB, or if the CB (one who made the tackle) had not been there, and this play went for a TD, would it still get posted as a bug?
Very odd play for sure, but we will need more replays before we can classify this as a bug.
Peace,
Fish
Ali Khaman
offline
offline
Looks like the defense did a good job rather than the QB making a mistake. (And later in the play, the RT makes a bad choice).
QB starts right and see the ROLB coming in, so he decides to counter and take it the other way. The only problem there is that he's got the LOLB and a CB coming in from the other side. The RT saw the LB beating the TE block so he let the CB go (bad move). If that play hadn't been a CB blitz, he probably would have made it at least back to the LOS.
QB starts right and see the ROLB coming in, so he decides to counter and take it the other way. The only problem there is that he's got the LOLB and a CB coming in from the other side. The RT saw the LB beating the TE block so he let the CB go (bad move). If that play hadn't been a CB blitz, he probably would have made it at least back to the LOS.
Kaerey
offline
offline
Originally posted by Ali Khaman
Looks like the defense did a good job rather than the QB making a mistake. (And later in the play, the RT makes a bad choice).
QB starts right and see the ROLB coming in, so he decides to counter and take it the other way. The only problem there is that he's got the LOLB and a CB coming in from the other side. The RT saw the LB beating the TE block so he let the CB go (bad move). If that play hadn't been a CB blitz, he probably would have made it at least back to the LOS.
I don't think it was the ROLB coming that made him turn I think it was the at the time unblocked FS that made him change direction. I think the bigger problem is he is too fast for his lead blockers, if he were a few ticks slower the TE would have engaged, he would have been behind the FB and HB and likely taken that play for a big gain.
From also having a very fast QB level up through the seasons, I have seen similar things when even with a lead blocker, the ball carrier will change path on an unblocked (but soon to be blocked) defender, ignoring the logical assumption that the lead blocker will get him.
Looks like the defense did a good job rather than the QB making a mistake. (And later in the play, the RT makes a bad choice).
QB starts right and see the ROLB coming in, so he decides to counter and take it the other way. The only problem there is that he's got the LOLB and a CB coming in from the other side. The RT saw the LB beating the TE block so he let the CB go (bad move). If that play hadn't been a CB blitz, he probably would have made it at least back to the LOS.
I don't think it was the ROLB coming that made him turn I think it was the at the time unblocked FS that made him change direction. I think the bigger problem is he is too fast for his lead blockers, if he were a few ticks slower the TE would have engaged, he would have been behind the FB and HB and likely taken that play for a big gain.
From also having a very fast QB level up through the seasons, I have seen similar things when even with a lead blocker, the ball carrier will change path on an unblocked (but soon to be blocked) defender, ignoring the logical assumption that the lead blocker will get him.
Ali Khaman
offline
offline
That could be it, too. Either way - I don't see it as so much of a bug as it was that the play just blew up (as football plays often do lol). If that CB hadn't been blitzing on the other side, the turn-back decision wouldn't have been so catastrophic, either.
Time Trial
offline
offline
Originally posted by IdRatherFlyFish
1. Thank you for opening up the build on that QB.
2. 63 vision -- is that a little low for a scrambling-dot this age? I'm not a super-dot builder, so that's a serious question for the number crunchers.
3. I wonder this -- if that QB had put a move on the CB, or if the CB (one who made the tackle) had not been there, and this play went for a TD, would it still get posted as a bug?
Very odd play for sure, but we will need more replays before we can classify this as a bug.
Peace,
Fish
1. All my builds on that team are open (and have been open since they were made) fwiw.
2. 63 Vision isn't that bad... it prevents him from seeing threats that aren't threats until they get within his range. I might still take it to 68, but I'm holding off because it this point the ALGs wouldn't make a huge difference.
3. Yes, this would still have been posted as a bug, but by Truth.
1. Thank you for opening up the build on that QB.
2. 63 vision -- is that a little low for a scrambling-dot this age? I'm not a super-dot builder, so that's a serious question for the number crunchers.
3. I wonder this -- if that QB had put a move on the CB, or if the CB (one who made the tackle) had not been there, and this play went for a TD, would it still get posted as a bug?
Very odd play for sure, but we will need more replays before we can classify this as a bug.
Peace,
Fish
1. All my builds on that team are open (and have been open since they were made) fwiw.
2. 63 Vision isn't that bad... it prevents him from seeing threats that aren't threats until they get within his range. I might still take it to 68, but I'm holding off because it this point the ALGs wouldn't make a huge difference.
3. Yes, this would still have been posted as a bug, but by Truth.
Edited by Time Trial on Nov 15, 2011 20:51:46
Time Trial
offline
offline
Originally posted by Kaerey
I don't think it was the ROLB coming that made him turn I think it was the at the time unblocked FS that made him change direction. I think the bigger problem is he is too fast for his lead blockers, if he were a few ticks slower the TE would have engaged, he would have been behind the FB and HB and likely taken that play for a big gain.
From also having a very fast QB level up through the seasons, I have seen similar things when even with a lead blocker, the ball carrier will change path on an unblocked (but soon to be blocked) defender, ignoring the logical assumption that the lead blocker will get him.
His speed is 128.08, agility 99.22 (no first step)
His blockers are:
TE - speed 141.84, agility 85.84 (no FS)
HB - speed 139.19, agility 86.19 (5 FS)
FB - speed 135.98, agility 85.98 (no FS)
LT - speed 83.54, agility 78.54 (7 FS)
I don't think it was the ROLB coming that made him turn I think it was the at the time unblocked FS that made him change direction. I think the bigger problem is he is too fast for his lead blockers, if he were a few ticks slower the TE would have engaged, he would have been behind the FB and HB and likely taken that play for a big gain.
From also having a very fast QB level up through the seasons, I have seen similar things when even with a lead blocker, the ball carrier will change path on an unblocked (but soon to be blocked) defender, ignoring the logical assumption that the lead blocker will get him.
His speed is 128.08, agility 99.22 (no first step)
His blockers are:
TE - speed 141.84, agility 85.84 (no FS)
HB - speed 139.19, agility 86.19 (5 FS)
FB - speed 135.98, agility 85.98 (no FS)
LT - speed 83.54, agility 78.54 (7 FS)
Kaerey
offline
offline
Originally posted by Time Trial
His speed is 128.08, agility 99.22 (no first step)
His blockers are:
TE - speed 141.84, agility 85.84 (no FS)
HB - speed 139.19, agility 86.19 (5 FS)
FB - speed 135.98, agility 85.98 (no FS)
LT - speed 83.54, agility 78.54 (7 FS)
Strange, he's still in front of the guys though on the replay.
His speed is 128.08, agility 99.22 (no first step)
His blockers are:
TE - speed 141.84, agility 85.84 (no FS)
HB - speed 139.19, agility 86.19 (5 FS)
FB - speed 135.98, agility 85.98 (no FS)
LT - speed 83.54, agility 78.54 (7 FS)
Strange, he's still in front of the guys though on the replay.
Dr. E
online
online
Originally posted by Time Trial
1. All my builds on that team are open (and have been open since they were made) fwiw.
2. 63 Vision isn't that bad... it prevents him from seeing threats that aren't threats until they get within his range. I might still take it to 68, but I'm holding off because it this point the ALGs wouldn't make a huge difference.
3. Yes, this would still have been posted as a bug, but by Truth.
63 vision at that level is horrible.
1. All my builds on that team are open (and have been open since they were made) fwiw.
2. 63 Vision isn't that bad... it prevents him from seeing threats that aren't threats until they get within his range. I might still take it to 68, but I'm holding off because it this point the ALGs wouldn't make a huge difference.
3. Yes, this would still have been posted as a bug, but by Truth.
63 vision at that level is horrible.
Time Trial
offline
offline
Originally posted by Dr. E
63 vision at that level is horrible.
I don't build my dots the same as other people. If I did, I would lose more games.
But it certainly shouldn't be so little vision that it would result in what we are seeing in the play.
63 vision at that level is horrible.
I don't build my dots the same as other people. If I did, I would lose more games.
But it certainly shouldn't be so little vision that it would result in what we are seeing in the play.
alindyl
offline
offline
Considering i see people with HB's with a similar vision at the same or higher level, it doesn't seem like 63 vision is all that horrendous. If 63 was not enough to run with the ball, I would expect to be seeing all sorts of players running around in circles in the backfield when they get the ball.
Since there is no OPP he should try to run as any HB or FB might try to run. Even with super elusive i don't think a player should run backwards in a giant loop because one guy might possibly be unblocked when he comes over to the end of his path.
Since there is no OPP he should try to run as any HB or FB might try to run. Even with super elusive i don't think a player should run backwards in a giant loop because one guy might possibly be unblocked when he comes over to the end of his path.
You are not logged in. Please log in if you want to post a reply.






























