User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Odd pursuit angle by DB - NOT A BUG - CLOSED
TrevJo
offline
Link
 
FS trying to cut off the FB's angle then suddenly just bolts toward the end zone
http://goallineblitz.com/game/replay.pl?game_id=1663228&pbp_id=2747313
Edited by VolBrian on Aug 5, 2011 12:34:58 (Closed)
Edited by VolBrian on May 17, 2011 07:44:04 (Needs more info - title edit)
 
Rage Kinard
offline
Link
 
missed vision check. He's trying to cover the TE.
 
TrevJo
offline
Link
 
notsureifsrs.gif
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by TrevJo
notsureifsrs.gif


He's not.

In this case, I think we're dealing with a pursuit angle that did not come to fruition as a result of the tackle by the CB.

Is this intended? I think it is, but I'm gonna mark this NMI and hope we can gather some replays of safeties doing the same thing and see what the play looks like if the FB had broken the CB's tackle.

 
Link
 
ive seen it a few times i think its intentional
I'm pretty sure the FS knew he'd be beat around the curve, so he adjusted to one that he could get him further downfield
 
Mike Rogers
Lead Tester
offline
Link
 
Originally posted by stromstarhammer
ive seen it a few times i think its intentional
I'm pretty sure the FS knew he'd be beat around the curve, so he adjusted to one that he could get him further downfield


It certainly looks that way.

Agreed that we need more replays to determine if there is any buggy behaviour though.
 
TrevJo
offline
Link
 
Originally posted by stromstarhammer
ive seen it a few times i think its intentional
I'm pretty sure the FS knew he'd be beat around the curve, so he adjusted to one that he could get him further downfield


I agree that that is what happens but I think it's bad pathing.
-Firstly, because the runner had to change direction in order to avoid the sideline, the defender probably would have gotten close enough at least for a diving tackle if he just kept running toward the sideline. I wonder if his calculation for whether or not he can catch the runner fails to take into account diving tackle radius.
-Secondly, even if he came up just short trying to stay at the current angle, there was a CB behind him to at least slow him down with a tackle attempt.
-Thirdly and probably most importantly, by making such a sharp cut, he slowed himself significantly. In fact, his speed dropped below 50% of what it was in one tick. Had he changed direction more gradually, he would have maintained most of his speed.
-Fourthly, the angle he took was useless. I took a screenshot of his position right after the cut and his position at the end of the play... the change was -15 pixels in the x direction and 87 pixels in the y direction. That's a 10 degree angle. How the hell are you supposed to cut off a faster runner who is more than 5 yards outside of you by taking a 10 degree angle? At the end of the play, the runner was on the outside of the numbers. It would have taken the defender at least 60 more yards to get to the outside of the numbers at his current angle.
Edited by TrevJo on May 18, 2011 19:19:27
Edited by TrevJo on May 18, 2011 19:18:20
 
Mike Rogers
Lead Tester
offline
Link
 
Valid points TrevJo.

If we get more replays of it happening (Various builds etc), we can think about sending it up for a fix.
 
TruthHammer
Lead Bugs Mod
offline
Link
 
It looks like a recurrence of this bug that was supposed to have been fixed last month.
http://goallineblitz.com/game/forum_thread.pl?thread_id=4467962

I'll move this to the NMI subforum for now, and if we can get some more replays, I'll ask Catch if we can reopen the other one.
 
TruthHammer
Lead Bugs Mod
offline
Link
 
Thread moved by moderator.
 
VolBrian
Rocky Top
offline
Link
 
Nothing new in over two months. Closing it out.
 
VolBrian
Rocky Top
offline
Link
 
Thread moved by moderator.
 
VolBrian
Rocky Top
offline
Link
 
Thread moved by moderator.
 


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