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 Bukowski
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.


Spin is a very good candidate for finding more examples of this problem, because it gives an unusual trajectory to the ball carrier, much like the broken tackle that moved the ball carrier backwards in the OP. So for anyone looking for examples, broken tackles are the most likely to demonstrate it, with Spins being more likely than other broken tackles.

 
RMiller517
offline
Link
 
Originally posted by NiborRis
Spin is a very good candidate for finding more examples of this problem, because it gives an unusual trajectory to the ball carrier, much like the broken tackle that moved the ball carrier backwards in the OP. So for anyone looking for examples, broken tackles are the most likely to demonstrate it, with Spins being more likely than other broken tackles.



LTS does sometimes project the ball carrier backwards a bit, too.
 
NiborRis
offline
Link
 
Going to collect a few examples from my own games. They're more subtle, but you can see the effects still.

http://goallineblitz.com/game/replay.pl?game_id=1263834&pbp_id=5408426
Watch the MLB and the CB in the open on the left side of the replay. Towards the end, right around the time of the spin (or other broken tackles) they both make a dodge downfield and away from the ball carrier.

http://goallineblitz.com/game/replay.pl?game_id=1263834&pbp_id=5414015
Watch the CB coming across from the left side running parallel to the 20 - until he bolts upfield, then changes again, right as the runner is hit and moving backwards. You can see the LOLB and LDE do a little pause and almost turn upfield as well at the same time, and also the MLB. The CB especially shouldn't be taking that path.

It's less noticable at the WL level I think because defenses are so fast and so agile, but it's still happening.
 
RMiller517
offline
Link
 
i think the main thing that should happen here is that the farther away a dot is from the ball carrier, the less they should be adjusting to his movements and the more they should be just running in his general direction up the field.
 
MC_Hammer
offline
Link
 
Originally posted by RMiller517
i think the main thing that should happen here is that the farther away a dot is from the ball carrier, the less they should be adjusting to his movements and the more they should be just running in his general direction up the field.


Agreed
 
kuaggie
offline
Link
 
Originally posted by RMiller517
i think the main thing that should happen here is that the farther away a dot is from the ball carrier, the less they should be adjusting to his movements and the more they should be just running in his general direction up the field.


also agreed.
 
robponce
offline
Link
 
Originally posted by RMiller517
i think the main thing that should happen here is that the farther away a dot is from the ball carrier, the less they should be adjusting to his movements and the more they should be just running in his general direction up the field.


I agree.
 
Stray Doug
offline
Link
 
Me too. See prior mulitple-paragraph post for a more detailed version of that more elegantly put statement.
 
RMiller517
offline
Link
 
Originally posted by Stray Doug
Me too. See prior mulitple-paragraph post for a more detailed version of that more elegantly put statement.


tl;dr
 
Djmr
offline
Link
 
Originally posted by RMiller517
i think the main thing that should happen here is that the farther away a dot is from the ball carrier, the less they should be adjusting to his movements and the more they should be just running in his general direction up the field.


Agree too, could we send the OP as a bug and this to be the fix? Stray Doug did cover this in his long post but to me its a bit, um, vague. If someone suggests a practical way to do this, I'll give it a verification.
 
Stray Doug
offline
Link
 
Well, ultimately we're making a suggestion of how it can be solved/improved... basically right now it appears the defenders are reacting solely based on the ballcarrier's vector (not necessarily the case, but what it appears to be).

Instead, I think it should be 4 variables at least that are considered:
- ballcarrier's vector
- defender's max speed
- defender's distance from ballcarrier
- defender's downfield angle relative to ballcarrier

Obviously vision plays in here as well, the better vision I have, the better angle I'm likely to take... but I'd think low vision should just be a "more likely to take wrong vector" and generally err on the side of taking an overly conservative vector, i.e. a bad decision is more likely to just give up some extra yards than a TD.

The reasoning for marking this a bug is that while technically we don't believe there is an error in the code, we do think it is affecting results on the field to a sufficient extent (due to the "logic" error compared to how defensive dots "ought" to react). Normally this would be a suggestion (area for improvement) but because it's impacting the game in a meaningful enough way (play results) we're thinking it should be a bug.

I still think that's fuzzy enough that we probably want Catch to weigh in on the proper determination on this one, no? If others agree just go ahead and flag it for admin verify.
 
kuaggie
offline
Link
 
Originally posted by Stray Doug
Well, ultimately we're making a suggestion of how it can be solved/improved... basically right now it appears the defenders are reacting solely based on the ballcarrier's vector (not necessarily the case, but what it appears to be).

Instead, I think it should be 4 variables at least that are considered:
- ballcarrier's vector
- defender's max speed
- defender's distance from ballcarrier
- defender's downfield angle relative to ballcarrier

Obviously vision plays in here as well, the better vision I have, the better angle I'm likely to take... but I'd think low vision should just be a "more likely to take wrong vector" and generally err on the side of taking an overly conservative vector, i.e. a bad decision is more likely to just give up some extra yards than a TD.

The reasoning for marking this a bug is that while technically we don't believe there is an error in the code, we do think it is affecting results on the field to a sufficient extent (due to the "logic" error compared to how defensive dots "ought" to react). Normally this would be a suggestion (area for improvement) but because it's impacting the game in a meaningful enough way (play results) we're thinking it should be a bug.

I still think that's fuzzy enough that we probably want Catch to weigh in on the proper determination on this one, no? If others agree just go ahead and flag it for admin verify.


I agree that we should send this to Catch. This appears to make broken tackles the end-all be-all of running backs....the question is whether Bort wants it to be that way (i.e. tackle-breaking is more powerful in GLB than it is in real life).
 
MC_Hammer
offline
Link
 
Probably should be sent on to Catch imo as well.
 
Djmr
offline
Link
 
Sending this to Catch then, I agree
 
Catch22
offline
Link
 
I think this is related to #159 so I'm just going to merge this thread with that one for now. If fixing 159 turns out to not correct this problem then we'll have to evaluate it separately.
 
Page:
 


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