User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > wierd pass coverage bugs where the defender starts running at the guy while he does a streak
Page:
 
The Commish
offline
Link
 
happened about 10-15 times in my game today
 
tautology
offline
Link
 
Originally posted by dsl20
Originally posted by Bort

It does have to do with trying to close the gap when on "close" type coverage, and when he does, he doesn't have the agility to turn around a full 180 right away (nobody really does). I'm not sure what the appropriate fix is, though, as far as the logic goes. If I make him not move forward and instead always wait for the man to reach him, he will get burned all day by hooks or curls. This isn't exactly a new thing - I've been wrestling with it for 7 seasons. Anyone have any ideas?


Well, when CB's in real life are playing "Close" defense on a WR, they normally don't start the play 4 yards away from the LOS. They are helmet to helmet with the WR at the LOS, and cover from there. Maybe if the CB's could start the play closer to the LOS, then they wouldn't have to run up to the spot they should have started the play in.


This would proably help, but with certain WR/CB matches there would still be an issue, I believe.
 
dsl20
offline
Link
 
Originally posted by tautology
Originally posted by dsl20

Originally posted by Bort


It does have to do with trying to close the gap when on "close" type coverage, and when he does, he doesn't have the agility to turn around a full 180 right away (nobody really does). I'm not sure what the appropriate fix is, though, as far as the logic goes. If I make him not move forward and instead always wait for the man to reach him, he will get burned all day by hooks or curls. This isn't exactly a new thing - I've been wrestling with it for 7 seasons. Anyone have any ideas?


Well, when CB's in real life are playing "Close" defense on a WR, they normally don't start the play 4 yards away from the LOS. They are helmet to helmet with the WR at the LOS, and cover from there. Maybe if the CB's could start the play closer to the LOS, then they wouldn't have to run up to the spot they should have started the play in.


This would proably help, but with certain WR/CB matches there would still be an issue, I believe.


I agree, that if you have a slower CB covering a faster WR, then that would be burn city, but that is the risk you run playing close coverage. If your CB can't keep up with the WR, then they need to play off a bit, just like in real life.
 
Bort
Admin
offline
Link
 
My "compare y axes" method seems to work fairly well so far in testing. It basically just tells the defender to slowly back up (do no move forward) until the receiver is within an acceptable range and then follow as usual. It applies when the receiver is heading towards the defender within a certain angle range, but not when he's moving away from him.

I need to test it with a variety of routes, though, to make sure it doesn't do something stupid on slants, etc.
 
Gyuri1
offline
Link
 
Originally posted by Bort
It does have to do with trying to close the gap when on "close" type coverage, and when he does, he doesn't have the agility to turn around a full 180 right away (nobody really does). I'm not sure what the appropriate fix is, though, as far as the logic goes. If I make him not move forward and instead always wait for the man to reach him, he will get burned all day by hooks or curls. This isn't exactly a new thing - I've been wrestling with it for 7 seasons. Anyone have any ideas?


This may be an inelegant fix, but what about if CBs had a vision check, which, if they passed it, would allow them to divine the route being run by the WR and adjust their vector accordingly. For example, a CB covering a streak route would have the chance (the tick before he would ordinarily move to close the route) to read the route, and, if he passes the vision check, instead of closing off the WR too early, he would continue along the planned route adjusting his speed (if he has the appropriate agility/speed) to match the WR. Though I guess this could cause problems if the WR breaks off a creative route.

EDIT: Nvm, Bort's solution seems much better.
Last edited Jan 17, 2009 17:36:33
 
Bort
Admin
offline
Link
 
Originally posted by Gyuri1
Originally posted by Bort

It does have to do with trying to close the gap when on "close" type coverage, and when he does, he doesn't have the agility to turn around a full 180 right away (nobody really does). I'm not sure what the appropriate fix is, though, as far as the logic goes. If I make him not move forward and instead always wait for the man to reach him, he will get burned all day by hooks or curls. This isn't exactly a new thing - I've been wrestling with it for 7 seasons. Anyone have any ideas?


This may be an inelegant fix, but what about if CBs had a vision check, which, if they passed it, would allow them to divine the route being run by the WR and adjust their vector accordingly. For example, a CB covering a streak route would have the chance (the tick before he would ordinarily move to close the route) to read the route, and, if he passes the vision check, instead of closing off the WR too early, he would continue along the planned route adjusting his speed (if he has the appropriate agility/speed) to match the WR. Though I guess this could cause problems if the WR breaks off a creative route.

EDIT: Nvm, Bort's solution seems much better.


Hm...psychic CB's? I dunno...though I guess I could actually see it being maybe a really rare occurrence or something, or maybe based on a play being run over and over? I don't think it really applies to the problem at hand here, though.
 
Nixx
offline
Link
 
Originally posted by Bort
My "compare y axes" method seems to work fairly well so far in testing. It basically just tells the defender to slowly back up (do no move forward) until the receiver is within an acceptable range and then follow as usual. It applies when the receiver is heading towards the defender within a certain angle range, but not when he's moving away from him.

I need to test it with a variety of routes, though, to make sure it doesn't do something stupid on slants, etc.


Also how about plays at the goal line? Often the CB will leave so much space (even though they are on tight coverage) that the WR has an easy catch for TD. This isn't exactly the same issue as brought up in the original post, but it's a similar problem, just giving too much room in front of the CB instead of letting them get behind.

Example: http://goallineblitz.com/game/replay.pl?game_id=288596&pbp_id=6378895
Last edited Jan 17, 2009 18:15:35
 
bacardi
offline
Link
 
Originally posted by Bort
My "compare y axes" method seems to work fairly well so far in testing. It basically just tells the defender to slowly back up (do no move forward) until the receiver is within an acceptable range and then follow as usual. It applies when the receiver is heading towards the defender within a certain angle range, but not when he's moving away from him.

I need to test it with a variety of routes, though, to make sure it doesn't do something stupid on slants, etc.

sweet! looking forward to seeing this live
 
pottsman
offline
Link
 
This is an actual bug? My CB's been burned on this in and out all season, I thought it was just low vision/agility (even though both are fairly high).
 
Painmaker
offline
Link
 
Just saw this thread... maybe influence CB decisions based on the direction of a WR's overall movement vector (sum their x- and y-axis if you don't already calculate this value) as well as the rate of change for the WR's direction of movement. Would help them know to close on a hook or curl but not on a streak set to run right past them. CB vision can also be a factor in how early a CB perceives or reacts to a change in "direction" or in "direction rate of change".
 
GiantBucs
offline
Link
 

Originally posted by Bort


Hm...psychic CB's? I dunno...though I guess I could actually see it being maybe a really rare occurrence or something, or maybe based on a play being run over and over? I don't think it really applies to the problem at hand here, though.


Are you saying defensive players don't get a vision check when covering a receiver or TE? They shouldn't so much be psychic as they should be able to stick with the receiver more accurately if they can read the route. If a CB has high vision and is in close coverage a fly pattern should be easy for him to read and thus turn to follow. If that means passing the vision check gives the CB a 90-100% acceleration rate when turning to follow the receiver to simulate his recognizing the play then that's how it should be done. If vision isn't being applied here then what's the point of defensive players even having vision?
 
supgreg
offline
Link
 
Glad to see something being done.

http://goallineblitz.com/game/forum_thread.pl?thread_id=1764656&page=1

It's just too bad this 6 page thread posted 17 days earlier didn't get the attention. Guess you gotta no somebody, huh?
 
csull36
offline
Link
 
Originally posted by Bort
Originally posted by Gyuri1

Originally posted by Bort


It does have to do with trying to close the gap when on "close" type coverage, and when he does, he doesn't have the agility to turn around a full 180 right away (nobody really does). I'm not sure what the appropriate fix is, though, as far as the logic goes. If I make him not move forward and instead always wait for the man to reach him, he will get burned all day by hooks or curls. This isn't exactly a new thing - I've been wrestling with it for 7 seasons. Anyone have any ideas?


This may be an inelegant fix, but what about if CBs had a vision check, which, if they passed it, would allow them to divine the route being run by the WR and adjust their vector accordingly. For example, a CB covering a streak route would have the chance (the tick before he would ordinarily move to close the route) to read the route, and, if he passes the vision check, instead of closing off the WR too early, he would continue along the planned route adjusting his speed (if he has the appropriate agility/speed) to match the WR. Though I guess this could cause problems if the WR breaks off a creative route.

EDIT: Nvm, Bort's solution seems much better.


Hm...psychic CB's? I dunno...though I guess I could actually see it being maybe a really rare occurrence or something, or maybe based on a play being run over and over? I don't think it really applies to the problem at hand here, though.


No, it's not psychic abilities, it is real football. If you ask any decent CB who played real football for a while, they can sometimes determine the route the wr is running by paying attention to the way the play develops, the body lean of the WR, the formation, etc. I think this definitely falls under the vision category, and in my opinion, CBs with high vision or super vision SA should be able to occasionally divine the WRs route and anticipate the pathing direction.
 
csull36
offline
Link
 
Very glad that something has been done about this by the way. Excellent ideas here about using vectors rather than absolute position in the calculations. This bug has been the most frustrating thing this season...
 
csull36
offline
Link
 
Looks like nothing has changed. Game from this morning:

http://goallineblitz.com/game/replay.pl?game_id=312799&pbp_id=7782627
http://goallineblitz.com/game/replay.pl?game_id=312799&pbp_id=7782824
http://goallineblitz.com/game/replay.pl?game_id=312799&pbp_id=7783189

Seriously, if this isn't fixed, GLB is going to have some serious problems...
 
Page:
 


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