User Pass
Home Sign Up Contact Log In
Forum > Goal Line Blitz > This is bothering me about CB coverage.
Page:
 
Bort
Admin
offline
Link
 
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.
 
danchrism
offline
Link
 
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.


pwnt
 
Link
 
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.


So is the CB's speed limited, or not limited (when in coverage)? You're saying he is, and telling csull his statement is false. Is it false because he said "always" and you say it's not "always" because the "speed limit flag" would be turned off "if he's too far away"? And once the ball is caught the "speed limit flag" is automatically turned off?
 
Asheme
offline
Link
 
Originally posted by SteelCity Mafia
So is the CB's speed limited, or not limited (when in coverage)? You're saying he is, and telling csull his statement is false. Is it false because he said "always" and you say it's not "always" because the "speed limit flag" would be turned off "if he's too far away"? And once the ball is caught the "speed limit flag" is automatically turned off?

There are entirely too many quotes ITP.

CB speed is limited so CBs don't out/overrun the WR, but that limit breaks once the WR gets away from the CB, is what Bort is saying.
 
Link
 
Originally posted by Asheme
Originally posted by SteelCity Mafia

So is the CB's speed limited, or not limited (when in coverage)? You're saying he is, and telling csull his statement is false. Is it false because he said "always" and you say it's not "always" because the "speed limit flag" would be turned off "if he's too far away"? And once the ball is caught the "speed limit flag" is automatically turned off?

There are entirely too many quotes ITP.

CB speed is limited so CBs don't out/overrun the WR, but that limit breaks once the WR gets away from the CB, is what Bort is saying.


So then this would give an advantage to WR's who have invested in Quick Cut (unless the CB has invested in Change Direction and it kicks in as well)? Once the WR breaks, the CB isn't going to speed up to catch him unless the WR gets too far away. So, what would too far away be?

Reason I'm asking is our pass defense is horrid compared to seasons past, and we have the exact same starting personnel (with an upgrade at SS over my SS, my SS is built more like a FS or CB). We went from making the conference championship in AAA last season, to only having 1 win that's worth counting this season. And I'm thinking that all the speed our CB's have is a total waste because it will never be used because of the "speed limit flag". If it's only being turned off if you get too far away (depending what too far is) or after the ball is caught, then speed on CB's don't have to be that high. It seems like if you built a zone coverage CB, you're likely to be much better off.
 
Bort
Admin
offline
Link
 
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.
 
azzurri10
offline
Link
 
Hooty hoo!
 
TuNice
offline
Link
 
Originally posted by azzurri10
Hooty hoo!


7 day ban imo
 
tsherr
offline
Link
 
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
 
csull36
offline
Link
 
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.


Wait, you just said I was false, and then confirmed exactly what I said. While in coverage, The CB's speed is limited by the WR's speed. Basically the point is that people are curious as to why cbs seem to trail much slower wrs long after the fake or cut was made. Perhaps the "limit speed" flag is not turned on or off in the most optimal manner in order to facilitate a realistic sim of cb coverage?
 
jsully75
offline
Link
 
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.
 
csull36
offline
Link
 
Originally posted by SteelCity Mafia
Once the WR breaks, the CB isn't going to speed up to catch him unless the WR gets too far away. So, what would too far away be?



Originally posted by tsherr

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


These quotes basically outline the question.

Is the limit "speed flag" being unnecessarily kept active even when the defender is a few ticks behind (but not "beat" or "too far back" according to the current definition)? Once the initial fake or cut is made that creates distance, shouldn't the "limit speed" flag be immediately deactivated to allow the cb to use his catch up speed?
 
PackMan97
offline
Link
 
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.
 
jsully75
offline
Link
 
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.


This is def not something new, I went back and watched some stuff from last season and it happened then as well, it was just less often that you saw the separation created to start. Even last season a much faster CB could not catch up to a slower WR if he had a step or two on him (or her).

One place where this is glaringly obvious is in LB coverage on TE's. After one game I got a PM from another owner saying "wow, your TE crushed us all day, what is his speed, like 100? Our LB had 90 speed and couldn't catch him." The funny thing was the TE had 67 speed and once he had a step or two on the LB he was never caught up with.
Last edited Jan 29, 2009 07:59:47
 
imnott
offline
Link
 
Originally posted by 5thyearcock
Yeah, at the very least, the speed cap should be released when the ball is thrown, or set on a timer based on the CB's vision.

Or if the CB bites on a fake and the WR is going deep, almost all CB's would start full speed for the WR.


this
 
Page:
 


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