User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > RESOLVED BUGS > Open Field Pathing is Bugged - FILED BUG #159
Page:
 
NiborRis
offline
Link
 
Originally posted by RMiller517
i have a feeling that this bug has to do with the ongoing pursuit pathing discussions... but i'll leave it here for other potential examples to be found.


I think it's this too - I think there's a problem that when a ball carrier is hit and moves backwards from the hit, the defensive players react as if he's moving backwards as his new path, and calculate a new path to intercept. Then when he starts to move forwards again, they change again. It's an effect that will be more noticeable the more the defender is perpendicular to the ball carrier, and the big shift in trajectory comes with a hefty penalty to speed for turning so sharply.

To limit the scope of the fix to just backwards moving defenders, perhaps the logic should be that if a ball carrier is moving backwards, or away from his endzone, then the D should be trying to move to a spot between the ball carrier and the endzone. I'm not sure that works well in all cases either - the biggest goal should be to avoid loss of speed from the D player turning sharply just because the ball carrier got hit backwards, especially when moving mostly parallel to the yard lines already.
 
Bukowski
offline
Link
 
Originally posted by STG
We need to keep in mind that the graphic representation of the play isn't to be considered 100% accurate of how the play panned out


lol.
 
Bukowski
offline
Link
 
http://goallineblitz.com/game/replay.pl?game_id=1218188&pbp_id=5124473

Here is another one. Watch when the RB cuts to the left for no reason whatsoever, then follow the LE on the bottom of the screen. While the RB is cutting, the LE and a few of the other defenders go in that very same direction, which shouldn't be the case.

Or I mean, unless it was just another faulty graphic representation.
 
Djmr
offline
Link
 
Originally posted by Bukowski
http://goallineblitz.com/game/replay.pl?game_id=1218188&pbp_id=5124473


That replay belongs with the already filed bug, #159 - http://goallineblitz.com/game/forum_thread.pl?thread_id=4073286 Ive added it to the file.

As for the situation about this in general, we are in an ongoing discussion about this, I'll add the relevant points in this thread to the discussion. We don't have enough to send to Bort (particularly, how to go about fixing this), so I think Im going to leave this topic for now.

Oh, and about STG's point, the replays aren't accurate for things like the exact position of the player. When a player moves in a strange direction on the replay, its because of the coding.
 
STG
offline
Link
 
Originally posted by STG

We need to keep in mind that the graphic representation of the play isn't to be considered 100% accurate of how the play panned out



Originally posted by Djmr

Oh, and about STG's point, the replays aren't accurate for things like the exact position of the player. When a player moves in a strange direction on the replay, its because of the coding.


Hey, I still agree that it looked Buggy didn't I?


 
Djmr
offline
Link
 
Originally posted by STG
Hey, I still agree that it looked Buggy didn't I?


Yeah, its ok, just saying
 
kuaggie
offline
Link
 
Can we get more examples of this happening?
 
Stray Doug
offline
Link
 
I feel this may be related to bug #159, but I do think there's a likely fundamental difference between (a) ballcarrier movement, (b) defensive movement when trying to "chase down" a ballcarrier from behind, and (c) defensive lateral movement to cut off angle of a ballcarrier who has not yet "broken free" when ballcarrier moves backwards briefly.

While these could all be grouped because they relate to pathing and open-field behavior, I also thing they could all be considered distinct. I also think (a) offensive and (c) defensive lateral (the example here) are bugged... whereas the recent thread on (b) seemed more like a suggestion. I think the distinction Id make is that (b) isn't really affecting things in a major way in terms of TDs and non-TDs or even yards gained on a play in the vast majority of cases, whereas both (a) and (c) seem like they very clearly are having a significant impact on the result of the play (when they occur). In almost all cases it seems like the reactions are too abrupt.

For this case, when a ballcarrier moves backwards or their speed drops significantly, seems like you want a variable adjustment by the defender based on the relative angle. If the defender is straight downfield of ballcarrier, then they're pretty much making a beeline for the ballcarrier anyway.

If the defender is at a 30-45 degree angle to the ballcarrier, then they adjust the "downfield intercept point" they were moving towards... now instead of heading for the pylon, they maybe move towards a point 5 yards "downfield of the ballcarrier" instead. A tick or two later, if ballcarrier still hasn't moved much, they may have reduced the angle, and say they're at a 25 degree downfield angle relative to ballcarrier, so they start to "hone in" and now are aiming for a point 4 yards downfield of ballcarrier instead. This would result in much subtler adjustments to pursuit angles and mitigate the defensive player's loss of speed.

On the other end of the spectrum if I'm 60 degree angle (more "across-field" than "downfield") I'm probably aiming 10 yards downfield of ballcarrier because I know I still have a lot of horizontal ground to cover and he may well pick up downfield speed again by the time I get over there.

I'm thinking here primarily of players who are still a good distance away... obviously if the defender is 5 yards from ballcarrier, they shouldn't aim for a point 10 yards downfield, even if they are at a 60 degree angle, so that must be considered as well. Might cap the defenders vector at "horizontal or the point x yards downfield" whichever is less... and also make the "aiming point" a function of 4 variables, (a) ballcarrier's vector, (b) my distance to ballcarrier, (c) relative downfield angle to ballcarrier, and (d) how fast I think I am... if I'm a FS I'll take probably a more aggressive angle than a DT would.

Anyway, just some thoughts of how to think about this. I don't know how much of this is in the current code already or if it's an entirely different way of thinking about it from defending dot's perspective. And I think the distinction between the 3 different types of open-pathing we're looking at is important, ESPECIALLY the O vs. D distinction. I just think those are entirely different sets of code most likely, whereas there's at least some similarity between the chase code and the lateral code for defense... it's just sort of a question of how you transition/affect the variables in play when you reach that transition point (around 90 degree angle to ballcarrier)
 
RMiller517
offline
Link
 
to me, i don't know if i would call this a bug in the way the code is being run, as much as a bug in the logic of the code itself. nothing is wrong with the way the defense is reacting, as far as the code is concerned. but the dots just need to behave more human-like, because they obviously wouldn't be doing this.

 
Bukowski
offline
Link
 
http://goallineblitz.com/game/replay.pl?game_id=1263638&pbp_id=5416715

Here is another one.
 
Bukowski
offline
Link
 
http://goallineblitz.com/game/replay.pl?game_id=1265590&pbp_id=5281814

defense slows down during the spin.
 
Bukowski
offline
Link
 
http://goallineblitz.com/game/replay.pl?game_id=1265590&pbp_id=5285558

and again, during the spin.
 
Bukowski
offline
Link
 
http://goallineblitz.com/game/replay.pl?game_id=1265039&pbp_id=4040476

during the spin.
 
Bukowski
offline
Link
 
And I'm not saying that it is a problem with Spin, because the play in the OP wasn't a Spin, just a missed tackle.

But there is obviously something going on.

The reason that is happens with spin, is because of the odd movement that the runner has, which is then basically copied by the entire defense, which is completely wrong.

This is very much related with the open-field pathing bug.
 
Djmr
offline
Link
 
Originally posted by Bukowski
http://goallineblitz.com/game/replay.pl?game_id=1265590&pbp_id=5281814

defense slows down during the spin.


Originally posted by Bukowski
http://goallineblitz.com/game/replay.pl?game_id=1265590&pbp_id=5285558

and again, during the spin.


Originally posted by Bukowski
http://goallineblitz.com/game/replay.pl?game_id=1265039&pbp_id=4040476

during the spin.


all private games, sorry.

I think the key thing Bort needs to do is to make defensive pursuits independent of player movement, but to me suggesting that as a fix is more like a suggestion, since it would basically be a whole new feature.
 
Page:
 


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