looks like a weird zone to me but never know
Forum > Discuss GLB Issues With Catch22 > RESOLVED BUGS > CB Gets lost in his own world - WILL NOT RESOLVE
EagleOtto
offline
offline
It reminds me of bad pathing when pursuing ball carriers when they get near endzone.
CB steps forward, looks to be man to man to me, then has to change direction, his direction probably gets messed up because the WRs destination is out of the back endzone
CB steps forward, looks to be man to man to me, then has to change direction, his direction probably gets messed up because the WRs destination is out of the back endzone
Originally posted by Deathblade
looks like a weird zone to me but never know
This was my first inclination when I looked at this a few days ago. Thinking about it, should probably not happen like it did though. I'll send this to QA and they can get to the bottom of this.
For the record, many of the replays posted later in the thread are replays that include Pump Fakes, and should not be considered evidence to this type of behavior.
looks like a weird zone to me but never know
This was my first inclination when I looked at this a few days ago. Thinking about it, should probably not happen like it did though. I'll send this to QA and they can get to the bottom of this.
For the record, many of the replays posted later in the thread are replays that include Pump Fakes, and should not be considered evidence to this type of behavior.
RMiller517
offline
offline
i'll ignore the fact that, under normal football rules, this is technically illegal touching 
very weird behavior, and i'm not saying it makes sense, but does vision play a part in it? if you slow it down, the CB goes back when the ball gets thrown, but not in the exact right direction.
is it possible for a cornerback to "lose" track of the man he's covering?

very weird behavior, and i'm not saying it makes sense, but does vision play a part in it? if you slow it down, the CB goes back when the ball gets thrown, but not in the exact right direction.
is it possible for a cornerback to "lose" track of the man he's covering?
robponce
offline
offline
Alright, beginning intensive determination of this bug.
First. What is the offensive play?
http://goallineblitz.com/images/plays/89.gif
Second. What are possible Defenses as said play?
CB Man WR2. (as confirmed by screenshots)
*this is actually a reason we generally ask for more than one option. Logically, a DC could find out that he screwed up and left a guy in zone when he should have been in man and thus fixes it post-game, but it was already posted as a bug etc etc, but this one looks to be alright*
Third. What is the buggy behavior?
Looks to me like the CB performs exactly as it should up to a point. It's set to -100 coverage distance so of course the first step is forward to try to get to the -100 distance. The WR with probably a combo of speed/first step/momentum blows right by.
THEN the CB turns to the outside. A weird movement indeed.
4th. Examine rest of the play.
If you'll notice, the tick that the CB moves away the QB draws the ball back as if to fire, then brings it back (much like the pump fake). however, just before he's able to reset the ball fully, the SS comes into his field of view and he quick releases it out into the WR.
To me this looks like a pump fake that simply didn't register the display 'pump fake', but something else catches my eye on this play. The RE also rushes the QB just at that moment. What this could also POSSIBLY be, is that the QB drew back, and decided to tuck and run. The CB has low agility/vision, so if the QB was tucking to run, he would probably take a looping curl to the outside to get to the QB. Then the Quick Release fires and it's too late, the pass soars by to the WR.
This troubles me, because option 1 is not a bug in the game, simply a missing display. Option 2 is a bug, where Quick Release fires on a QB pulling down the pass to run which shouldn't happen.
Which circles us all back to the point where we need more examples of this behavior. Anyone else have any that isn't an obvious pump fake? We know it's a streak (from the play that was called) and the CB is in man-to-man, so something (whether it be pump fake, bugged tuck and run, or simply bad tactics) caused him to leave his assignment. Anything of similar value would be huge in narrowing that down, or eliminating a possible cause.
First. What is the offensive play?
http://goallineblitz.com/images/plays/89.gif
Second. What are possible Defenses as said play?
CB Man WR2. (as confirmed by screenshots)
*this is actually a reason we generally ask for more than one option. Logically, a DC could find out that he screwed up and left a guy in zone when he should have been in man and thus fixes it post-game, but it was already posted as a bug etc etc, but this one looks to be alright*
Third. What is the buggy behavior?
Looks to me like the CB performs exactly as it should up to a point. It's set to -100 coverage distance so of course the first step is forward to try to get to the -100 distance. The WR with probably a combo of speed/first step/momentum blows right by.
THEN the CB turns to the outside. A weird movement indeed.
4th. Examine rest of the play.
If you'll notice, the tick that the CB moves away the QB draws the ball back as if to fire, then brings it back (much like the pump fake). however, just before he's able to reset the ball fully, the SS comes into his field of view and he quick releases it out into the WR.
To me this looks like a pump fake that simply didn't register the display 'pump fake', but something else catches my eye on this play. The RE also rushes the QB just at that moment. What this could also POSSIBLY be, is that the QB drew back, and decided to tuck and run. The CB has low agility/vision, so if the QB was tucking to run, he would probably take a looping curl to the outside to get to the QB. Then the Quick Release fires and it's too late, the pass soars by to the WR.
This troubles me, because option 1 is not a bug in the game, simply a missing display. Option 2 is a bug, where Quick Release fires on a QB pulling down the pass to run which shouldn't happen.
Which circles us all back to the point where we need more examples of this behavior. Anyone else have any that isn't an obvious pump fake? We know it's a streak (from the play that was called) and the CB is in man-to-man, so something (whether it be pump fake, bugged tuck and run, or simply bad tactics) caused him to leave his assignment. Anything of similar value would be huge in narrowing that down, or eliminating a possible cause.
Edited by robponce on Jul 11, 2010 16:29:48
Originally posted by robponce
The CB has low agility/vision
This is what they are/were at the time of the play...
CB Agility is 55.76
CB Vision is 62.76
What is considered low?
The CB has low agility/vision
This is what they are/were at the time of the play...
CB Agility is 55.76
CB Vision is 62.76
What is considered low?
RMiller517
offline
offline
Ok, so hopefully somebody follows me here:
Watch the replay frame by frame. Right before the QB looks at the WR2, the WR makes a slight cut to the outside. The route was likely over at that point, but when he does, the cornerback moves back to the right, but then when the ball goes in the air, tries to adjust himself. I'm wondering if this is a creative route running fake, where the CB didn't go all the way back into the end zone (right next to the WR) because it makes more sense to stand in front of the WR to deflect or Intercept it, but then got faked out when anticipating the route/pass
thats my theory. thoughts?
Watch the replay frame by frame. Right before the QB looks at the WR2, the WR makes a slight cut to the outside. The route was likely over at that point, but when he does, the cornerback moves back to the right, but then when the ball goes in the air, tries to adjust himself. I'm wondering if this is a creative route running fake, where the CB didn't go all the way back into the end zone (right next to the WR) because it makes more sense to stand in front of the WR to deflect or Intercept it, but then got faked out when anticipating the route/pass
thats my theory. thoughts?
Edited by RMiller517 on Jul 12, 2010 10:05:20
Djmr
offline
offline
I actually think you're both wrong 
I believe its part of the route-messing-up-when-routes-reach-endzone-bug - check this out - http://goallineblitz.com/game/forum_thread.pl?thread_id=3904373
On the first replay, the CB on the right (Arbok) makes a similar movement, only inside instead of outside. On the second replay, the MLB does almost exactly what the CB did.

I believe its part of the route-messing-up-when-routes-reach-endzone-bug - check this out - http://goallineblitz.com/game/forum_thread.pl?thread_id=3904373
On the first replay, the CB on the right (Arbok) makes a similar movement, only inside instead of outside. On the second replay, the MLB does almost exactly what the CB did.
robponce
offline
offline
Originally posted by Djmr
I actually think you're both wrong
I believe its part of the route-messing-up-when-routes-reach-endzone-bug - check this out - http://goallineblitz.com/game/forum_thread.pl?thread_id=3904373
On the first replay, the CB on the right (Arbok) makes a similar movement, only inside instead of outside. On the second replay, the MLB does almost exactly what the CB did.
the MLB maybe, he does make a similar route, hesitant to say the same, but could be... but that wasn't the bug in those situations. those were post INT bugs, and the first replay is just the CB jumping the route. No bug in that one.
As far as
Originally posted by RMiller517
Ok, so hopefully somebody follows me here:
Watch the replay frame by frame. Right before the QB looks at the WR2, the WR makes a slight cut to the outside. The route was likely over at that point, but when he does, the cornerback moves back to the right, but then when the ball goes in the air, tries to adjust himself. I'm wondering if this is a creative route running fake, where the CB didn't go all the way back into the end zone (right next to the WR) because it makes more sense to stand in front of the WR to deflect or Intercept it, but then got faked out when anticipating the route/pass
thats my theory. thoughts?
I think it could make sense, but the WR 'move' happens 7 or 8 ticks before the ball is thrown. The CB continues to slide outside long after the 'move' and it wasn't a severe cut which would cause more reaction from the CB. So I don't think that necessarily is the issue.
I actually think you're both wrong

I believe its part of the route-messing-up-when-routes-reach-endzone-bug - check this out - http://goallineblitz.com/game/forum_thread.pl?thread_id=3904373
On the first replay, the CB on the right (Arbok) makes a similar movement, only inside instead of outside. On the second replay, the MLB does almost exactly what the CB did.
the MLB maybe, he does make a similar route, hesitant to say the same, but could be... but that wasn't the bug in those situations. those were post INT bugs, and the first replay is just the CB jumping the route. No bug in that one.
As far as
Originally posted by RMiller517
Ok, so hopefully somebody follows me here:
Watch the replay frame by frame. Right before the QB looks at the WR2, the WR makes a slight cut to the outside. The route was likely over at that point, but when he does, the cornerback moves back to the right, but then when the ball goes in the air, tries to adjust himself. I'm wondering if this is a creative route running fake, where the CB didn't go all the way back into the end zone (right next to the WR) because it makes more sense to stand in front of the WR to deflect or Intercept it, but then got faked out when anticipating the route/pass
thats my theory. thoughts?
I think it could make sense, but the WR 'move' happens 7 or 8 ticks before the ball is thrown. The CB continues to slide outside long after the 'move' and it wasn't a severe cut which would cause more reaction from the CB. So I don't think that necessarily is the issue.
Stray Doug
offline
offline
What I notice is that CB2 is following WR2 straight up field while QB is targeting TE, but when the vision line hits WR1 (looking at old replays, I don't like the Flash ones), the very next tick is where CB2 changes his vector to head towards the corner instead of WR2. I don't have a theory as to why this is, but just something I noticed.
Edited by Stray Doug on Jul 13, 2010 09:06:18
RMiller517
offline
offline
Originally posted by Stray Doug
What I notice is that CB2 is following WR2 straight up field while QB is targeting TE, but when the vision line hits WR1 (looking at old replays, I don't like the Flash ones), the very next tick is where CB2 changes his vector to head towards the corner instead of WR2. I don't have a theory as to why this is, but just something I noticed.
could it be possible then that the CB was covering the WR2 but acting as if he was covering the WR1?
What I notice is that CB2 is following WR2 straight up field while QB is targeting TE, but when the vision line hits WR1 (looking at old replays, I don't like the Flash ones), the very next tick is where CB2 changes his vector to head towards the corner instead of WR2. I don't have a theory as to why this is, but just something I noticed.
could it be possible then that the CB was covering the WR2 but acting as if he was covering the WR1?
robponce
offline
offline
I think we might want to get Catch's eyes on this one since it hasn't really moved forward much.
Catch?
Catch?
kuaggie
offline
offline
Originally posted by robponce
I think we might want to get Catch's eyes on this one since it hasn't really moved forward much.
Catch?
i agree.....although it's pretty impossible to tell if this is phantom play call or buggy man logic. It really looks like a zone.....
I think we might want to get Catch's eyes on this one since it hasn't really moved forward much.
Catch?
i agree.....although it's pretty impossible to tell if this is phantom play call or buggy man logic. It really looks like a zone.....
RMiller517
offline
offline
Can't duplicate on the test server or dev box even by positioning players manually - it's one of those perfect storm things that requires a certain set of perfect conditions for it to happen. Closing as will not resolve (Per Catch's Instructions) but if Bort figures out a way to do so, he wil..
Edited by RMiller517 on Jul 23, 2010 11:35:28
You are not logged in. Please log in if you want to post a reply.




























