If this is fixed, then CBs will just overrun the WRs when the ball is thrown because they have "too low agility". It's a neverending cycle.
Forum > Goal Line Blitz > This is bothering me about CB coverage.
kurieg
offline
offline
Originally posted by PackMan97
Originally posted by Bort
Originally posted by csull36
Namely, the fact that a CB in coverage is always limited by the WRs speed.
False. The CB's speed is limited by the WR's speed unless he gets behind him or is too far away (gets beat). The bug was related to the "limit speed" flag not getting turned off properly on some catches.
Define "behind"?
There are a lot of routes in which the CB is in between the WR and the endzone, but the route is a slant or cross so as the WR is travelling, the CB is chasing.
The "behind" calculation should take the WR's direction of travel and use a line perpendicular to that to define in front of/behind. Maybe you already do this, but I see a lot (especially crossing routes) in which the CB never catches up to the WR even if they are faster.
This. I think this is hosed. It's not just CBs, though, it's also people covering TEs in crossing routes.
Originally posted by Bort
Originally posted by csull36
Namely, the fact that a CB in coverage is always limited by the WRs speed.
False. The CB's speed is limited by the WR's speed unless he gets behind him or is too far away (gets beat). The bug was related to the "limit speed" flag not getting turned off properly on some catches.
Define "behind"?
There are a lot of routes in which the CB is in between the WR and the endzone, but the route is a slant or cross so as the WR is travelling, the CB is chasing.
The "behind" calculation should take the WR's direction of travel and use a line perpendicular to that to define in front of/behind. Maybe you already do this, but I see a lot (especially crossing routes) in which the CB never catches up to the WR even if they are faster.
This. I think this is hosed. It's not just CBs, though, it's also people covering TEs in crossing routes.
jsully75
offline
offline
Originally posted by cabrasher
If this is fixed, then CBs will just overrun the WRs when the ball is thrown because they have "too low agility". It's a neverending cycle.
yes, but that is a build problem, not a problem with the players not behaving up to the potential of the hard earned SP used to build a player (not including the blood, sweat, and tears.)
If this is fixed, then CBs will just overrun the WRs when the ball is thrown because they have "too low agility". It's a neverending cycle.
yes, but that is a build problem, not a problem with the players not behaving up to the potential of the hard earned SP used to build a player (not including the blood, sweat, and tears.)
cabrasher
offline
offline
Originally posted by jsully75
Originally posted by cabrasher
If this is fixed, then CBs will just overrun the WRs when the ball is thrown because they have "too low agility". It's a neverending cycle.
yes, but that is a build problem, not a problem with the players not behaving up to the potential of the hard earned SP used to build a player (not including the blood, sweat, and tears.)
I put "too low agility" in quotes for a reason.
Originally posted by cabrasher
If this is fixed, then CBs will just overrun the WRs when the ball is thrown because they have "too low agility". It's a neverending cycle.
yes, but that is a build problem, not a problem with the players not behaving up to the potential of the hard earned SP used to build a player (not including the blood, sweat, and tears.)
I put "too low agility" in quotes for a reason.
jsully75
offline
offline
Originally posted by cabrasher
Originally posted by jsully75
Originally posted by cabrasher
If this is fixed, then CBs will just overrun the WRs when the ball is thrown because they have "too low agility". It's a neverending cycle.
yes, but that is a build problem, not a problem with the players not behaving up to the potential of the hard earned SP used to build a player (not including the blood, sweat, and tears.)
I put "too low agility" in quotes for a reason.
is that like some kind of "tool" code that I don't know about?
Originally posted by jsully75
Originally posted by cabrasher
If this is fixed, then CBs will just overrun the WRs when the ball is thrown because they have "too low agility". It's a neverending cycle.
yes, but that is a build problem, not a problem with the players not behaving up to the potential of the hard earned SP used to build a player (not including the blood, sweat, and tears.)
I put "too low agility" in quotes for a reason.
is that like some kind of "tool" code that I don't know about?
PackMan97
offline
offline
Originally posted by kurieg
Originally posted by PackMan97
Originally posted by Bort
False. The CB's speed is limited by the WR's speed unless he gets behind him or is too far away (gets beat). The bug was related to the "limit speed" flag not getting turned off properly on some catches.
Define "behind"?
There are a lot of routes in which the CB is in between the WR and the endzone, but the route is a slant or cross so as the WR is travelling, the CB is chasing.
The "behind" calculation should take the WR's direction of travel and use a line perpendicular to that to define in front of/behind. Maybe you already do this, but I see a lot (especially crossing routes) in which the CB never catches up to the WR even if they are faster.
This. I think this is hosed. It's not just CBs, though, it's also people covering TEs in crossing routes.
Ya, I've seen it a bunch where if the TE/WR gets just a step or two ahead the man covering NEVER closes the gap, just decides I'm gonna give a 2-3 yard cushion.
Originally posted by PackMan97
Originally posted by Bort
False. The CB's speed is limited by the WR's speed unless he gets behind him or is too far away (gets beat). The bug was related to the "limit speed" flag not getting turned off properly on some catches.
Define "behind"?
There are a lot of routes in which the CB is in between the WR and the endzone, but the route is a slant or cross so as the WR is travelling, the CB is chasing.
The "behind" calculation should take the WR's direction of travel and use a line perpendicular to that to define in front of/behind. Maybe you already do this, but I see a lot (especially crossing routes) in which the CB never catches up to the WR even if they are faster.
This. I think this is hosed. It's not just CBs, though, it's also people covering TEs in crossing routes.
Ya, I've seen it a bunch where if the TE/WR gets just a step or two ahead the man covering NEVER closes the gap, just decides I'm gonna give a 2-3 yard cushion.
Asheme
offline
offline
Originally posted by jsully75
yes, but that is a build problem, not a problem with the players not behaving up to the potential of the hard earned SP used to build a player (not including the blood, sweat, and tears.)
It's not just that, the fix was put in because CBs who were much faster than the WR they were covering got penalized for the extra speed.
http://goallineblitz.com/game/forum_thread.pl?thread_id=2262&page=6
3rd post down.
yes, but that is a build problem, not a problem with the players not behaving up to the potential of the hard earned SP used to build a player (not including the blood, sweat, and tears.)
It's not just that, the fix was put in because CBs who were much faster than the WR they were covering got penalized for the extra speed.
http://goallineblitz.com/game/forum_thread.pl?thread_id=2262&page=6
3rd post down.
ZeroTolerance
offline
offline
Bort, anything on the plays where CBs sprint out of the back of the end zone like they are afraid of being beat on a pass into the 1st row?
GP1
offline
offline
Originally posted by Asheme
Originally posted by jsully75
yes, but that is a build problem, not a problem with the players not behaving up to the potential of the hard earned SP used to build a player (not including the blood, sweat, and tears.)
It's not just that, the fix was put in because CBs who were much faster than the WR they were covering got penalized for the extra speed.
http://goallineblitz.com/game/forum_thread.pl?thread_id=2262&page=6
3rd post down.
We understand. But youre fixing something broken by breaking something else. If a CB is a step or two behind a WR, and the CB has faster speed, he should be able to catch up. Not stay steps behind.
Bort's previous fix needs to be updated to close the gap of "too far away"
Originally posted by jsully75
yes, but that is a build problem, not a problem with the players not behaving up to the potential of the hard earned SP used to build a player (not including the blood, sweat, and tears.)
It's not just that, the fix was put in because CBs who were much faster than the WR they were covering got penalized for the extra speed.
http://goallineblitz.com/game/forum_thread.pl?thread_id=2262&page=6
3rd post down.
We understand. But youre fixing something broken by breaking something else. If a CB is a step or two behind a WR, and the CB has faster speed, he should be able to catch up. Not stay steps behind.
Bort's previous fix needs to be updated to close the gap of "too far away"
Last edited Jan 29, 2009 14:55:21
tsherr
offline
offline
Originally posted by jsully75
Originally posted by tsherr
Originally posted by Bort
FWIW, the speed limit thing has been in for a couple seasons now, after the fast CB vs a slow WR problem was first posted. Better passing this season is mostly because there are more opportunities for fakes and hitting open receivers earlier, due to creative route running and other updates.
But I've seen a fair number of plays where the CB follows the WR about three yards back like the one posted with the SS covering the CB ( http://goallineblitz.com/game/replay.pl?game_id=357223&pbp_id=11130788 ) - if a player is playing loose, then it makes sense that he'd stay three yards down field from the WR to prevent the WR from getting passed him, but if he's following the WR, then he should be closing to stick with him, shouldn't he?
T
that SS was set on close.
Then on that play the sim handled the SS incorrectly - if the WR was faster than the SS, he should have pulled away - I guess it's possible that the SS was the same speed as the WR, but it seems unlikely. Why wouldn't the SS close on the WR so as to be right there to make the tackle or the PD if the pass came his way?
T
Originally posted by tsherr
Originally posted by Bort
FWIW, the speed limit thing has been in for a couple seasons now, after the fast CB vs a slow WR problem was first posted. Better passing this season is mostly because there are more opportunities for fakes and hitting open receivers earlier, due to creative route running and other updates.
But I've seen a fair number of plays where the CB follows the WR about three yards back like the one posted with the SS covering the CB ( http://goallineblitz.com/game/replay.pl?game_id=357223&pbp_id=11130788 ) - if a player is playing loose, then it makes sense that he'd stay three yards down field from the WR to prevent the WR from getting passed him, but if he's following the WR, then he should be closing to stick with him, shouldn't he?
T
that SS was set on close.
Then on that play the sim handled the SS incorrectly - if the WR was faster than the SS, he should have pulled away - I guess it's possible that the SS was the same speed as the WR, but it seems unlikely. Why wouldn't the SS close on the WR so as to be right there to make the tackle or the PD if the pass came his way?
T
im317
offline
offline
im sorry, but if the WR gets past my CB then my CB should be running as fast as possible until he has regained the lead on the WR dictated by my coverage settings, and even if he cant catch him he should still run so that if someone else half tackles him but its broken the slow down means that the CB if he doesn't stop running can make the tackle.
in short, the CB should never stop trying to pass the WR unless the ball is overthrown or the WR overruns the ball.
in short, the CB should never stop trying to pass the WR unless the ball is overthrown or the WR overruns the ball.
Last edited Jan 29, 2009 18:09:57
jsully75
offline
offline
Originally posted by tsherr
Originally posted by jsully75
Originally posted by tsherr
Originally posted by Bort
FWIW, the speed limit thing has been in for a couple seasons now, after the fast CB vs a slow WR problem was first posted. Better passing this season is mostly because there are more opportunities for fakes and hitting open receivers earlier, due to creative route running and other updates.
But I've seen a fair number of plays where the CB follows the WR about three yards back like the one posted with the SS covering the CB ( http://goallineblitz.com/game/replay.pl?game_id=357223&pbp_id=11130788 ) - if a player is playing loose, then it makes sense that he'd stay three yards down field from the WR to prevent the WR from getting passed him, but if he's following the WR, then he should be closing to stick with him, shouldn't he?
T
that SS was set on close.
Then on that play the sim handled the SS incorrectly - if the WR was faster than the SS, he should have pulled away - I guess it's possible that the SS was the same speed as the WR, but it seems unlikely. Why wouldn't the SS close on the WR so as to be right there to make the tackle or the PD if the pass came his way?
T
As I said, I GM on both those teams, the SS is about 20 SP faster than the WR.
Originally posted by jsully75
Originally posted by tsherr
Originally posted by Bort
FWIW, the speed limit thing has been in for a couple seasons now, after the fast CB vs a slow WR problem was first posted. Better passing this season is mostly because there are more opportunities for fakes and hitting open receivers earlier, due to creative route running and other updates.
But I've seen a fair number of plays where the CB follows the WR about three yards back like the one posted with the SS covering the CB ( http://goallineblitz.com/game/replay.pl?game_id=357223&pbp_id=11130788 ) - if a player is playing loose, then it makes sense that he'd stay three yards down field from the WR to prevent the WR from getting passed him, but if he's following the WR, then he should be closing to stick with him, shouldn't he?
T
that SS was set on close.
Then on that play the sim handled the SS incorrectly - if the WR was faster than the SS, he should have pulled away - I guess it's possible that the SS was the same speed as the WR, but it seems unlikely. Why wouldn't the SS close on the WR so as to be right there to make the tackle or the PD if the pass came his way?
T
As I said, I GM on both those teams, the SS is about 20 SP faster than the WR.
cabrasher
offline
offline
Hmm.....was there a phantom fix that we weren't told about today? I'm actually starting to see CBs catch up with WRs now after getting blown by.
Watch CB1 in both of these. It's a new capped league and he has 82 speed/50 agility, not sure about the WR, but he seems to catch up with him and close the gap after he was beaten.
http://goallineblitz.com/game/replay.pl?game_id=341520&pbp_id=11663134
http://goallineblitz.com/game/replay.pl?game_id=341520&pbp_id=11662901
Watch CB1 in both of these. It's a new capped league and he has 82 speed/50 agility, not sure about the WR, but he seems to catch up with him and close the gap after he was beaten.
http://goallineblitz.com/game/replay.pl?game_id=341520&pbp_id=11663134
http://goallineblitz.com/game/replay.pl?game_id=341520&pbp_id=11662901
You are not logged in. Please log in if you want to post a reply.






























