User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Tight coverage isn't tight at all
Page:
 
Bort
Admin
offline
Link
 
Originally posted by RAPB
We noticed that by the end of last season. One of our corners seemed to play medium coverage instead of close.

If I had to guess: the SIM somehow compares the speed/agility values of WR and CB. If the mismatch is whatever the SIM considers "too large", the CB is giving cushion.


That's part of it; Also, finding a middle point where the CB can meet up with the WR and not get blown by is fairly hard, especially when the WR is really fast and the CB doesn't know the route.

If he runs forward to get to the 1-2 yd cushion point, he'll get blown by as he tries to turn around and keep running the direction he was originally backing up on; this was a problem many times the last couple seasons, which I've been monkeying with for a while. He has to try and let him "catch up" somewhere in the middle or get burned every time, unless he has crazy agility.

This generally only applies on streak type routes.
 
musky5
offline
Link
 
bump-and-run coverage needs to be added
Last edited Nov 8, 2008 18:59:42
 
InRomoWeTrust
Lead Mod
offline
Link
 
Is there anyway the CB could mimic the speed of the WR? Like if the CBs speed is over a certain range (let's say +5 for this example) the CBs speed decreases to the WRs value until he breaks coverage (ball is thrown, etc.). Same could go w/ agility maybe.
 
Adderfist
offline
Link
 
I don't see why you can't just have the CB's line close to the WR's pre-snap.

The other thing you could do is add an option so coverage is like this

Prevent (7 yards)
Long (5 yards)
Medium (3 yards)
Close (1 yard)

Let the players decide how shit their corner is. I would rather be beat deep once or twice a game, than give up eight or nine catches at 8 yards a pop, Those keep drives alive.
 
SCACE
offline
Link
 
Originally posted by Adderfist
I don't see why you can't just have the CB's line close to the WR's pre-snap.

The other thing you could do is add an option so coverage is like this

Prevent (7 yards)
Long (5 yards)
Medium (3 yards)
Close (1 yard)

Let the players decide how shit their corner is. I would rather be beat deep once or twice a game, than give up eight or nine catches at 8 yards a pop, Those keep drives alive.


would love to see that.
 
skibodragula
McFroggin
offline
Link
 
I still say its in the build...I have seen my CB crew stick like white on rice and somedays not..I also have seen monster cb's get roasted by my WR's...its a little of both I think..good idea though
 
Adderfist
offline
Link
 
Originally posted by skibodragula
I still say its in the build...I have seen my CB crew stick like white on rice and somedays not..I also have seen monster cb's get roasted by my WR's...its a little of both I think..good idea though


Originally posted by Adderfist
http://goallineblitz.com/game/replay.pl?game_id=262000&pbp_id=441798

Tight, Safe.

Doesn't look like tight coverage to me at all. He's giving him a 10 yard cushion.


75 speed/agi, 60 vis, 5 super vis, 5 shutdown coverage.

Any other theories?
 
maizenhops
offline
Link
 
i think its dumb to have it coded based on the wrs speed vs cbs speed.if i want to play tight, let me play tight.if our cbs arent fast/agile enough to keep up let us get burnt and we'll make adjustments.
 
kevindurant35
offline
Link
 
Originally posted by musky5
bump-and-run coverage needs to be added


 
Link
 
Originally posted by musky5
bump-and-run coverage needs to be added



Agreed. Tight should = bump and run.


If the CB has higher strength than the WR and higher agility (with equal or higher speed than the agility number), then the CB should cause a 1 or 2 second delay to the route.

Likewise, if the WR has higher strength and higher agility (with equal or higher speed than the agility number), then the WR should bump the CB out of the way and be given a 3 yard head start a decent % of the time (say 10-15%).


Example:

CB: 25 strength, 70 speed, 60 agility
WR: 15 strength, 90 speed, 50 agility

This receiver should get bumped a good % of the time if the CB playing tight


Likewise:

CB: 25 strength, 90 speed, 60 agility
WR: 35 strength, 70 speed, 70 agility

This CB should get bumped out of the way a good % of the time if playing the WR tight.


This is a way you could counter pure speed receivers or WEAK CB's
Last edited Nov 9, 2008 08:10:44
 
TCR
offline
Link
 
Originally posted by kalkmanc
i think its dumb to have it coded based on the wrs speed vs cbs speed.if i want to play tight, let me play tight.if our cbs arent fast/agile enough to keep up let us get burnt and we'll make adjustments.


This and this is also why the SS and FS are in the game.Sad part about this is usually the safety's will chose the wrong person to cover no matter the settings.I had mine set for medium coverage in our last game and they chose to come underneath and pick up the WR's instead of playing back.The whole secondary issue is wacky right now.

All a receiver needs these days is speed and agility forget about catching and possesion skils.I speak from both sides of the ball since I have both sets of players, the passing game is becoming impossible to defend.
 
TCR
offline
Link
 
Originally posted by SteelersInsider
Originally posted by musky5

bump-and-run coverage needs to be added



Agreed. Tight should = bump and run.


If the CB has higher strength than the WR and higher agility (with equal or higher speed than the agility number), then the CB should cause a 1 or 2 second delay to the route.

Likewise, if the WR has higher strength and higher agility (with equal or higher speed than the agility number), then the WR should bump the CB out of the way and be given a 3 yard head start a decent % of the time (say 10-15%).


Example:

CB: 25 strength, 70 speed, 60 agility
WR: 15 strength, 90 speed, 50 agility

This receiver should get bumped a good % of the time if the CB playing tight


Likewise:

CB: 25 strength, 90 speed, 60 agility
WR: 35 strength, 70 speed, 70 agility

This CB should get bumped out of the way a good % of the time if playing the WR tight.


This is a way you could counter pure speed receivers or WEAK CB's


Agreed, give us something on the defensive side of the ball.A speed receiver will have no other attributes other than speed and agility.This would at the least make other attributes count for something.
 
DarthVisor
offline
Link
 
Originally posted by kalkmanc
i think its dumb to have it coded based on the wrs speed vs cbs speed.if i want to play tight, let me play tight.if our cbs arent fast/agile enough to keep up let us get burnt and we'll make adjustments.


+1
 
Rush Hour700
offline
Link
 
exactly i seen this same thing...let our Corners play close......

if they get beat ok.....

Also fix the safety BS....why do i see my FS whos playing a deep zone trying to jump the slot on a 3 yard curl? and my outside corner taking his WR deep 1 on 1?

and why is the SS so glued to the TE...wtf
 
TCR
offline
Link
 
Let my safteys play the way I have the settings and come up and knock the snot out of the receivers when they catch the ball.I guarantee they want hang on to the ball with some of the strength and tackling the safteys have.Seems to be another unfair advantage to the offense.

edit for spelling.
Last edited Nov 9, 2008 09:49:42
 
Page:
 


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