User Pass
Home Sign Up Contact Log In
Page:
 
Bladow
offline
Link
 
CB's have speedster attributes as well first step change direction, are those being adjusted as well?
 
bluepike
offline
Link
 
Excellent news overall. I'm happy to hear this is being looked at as I commented to another owner that my CB's were getting beaten way too often for their attributes and he pointed me in this direction.

Realistically, is this something we'd see in a couple days or a couple weeks? Not asking for a solid date of course as I know testing and adjustments will be made, just an idea.
 
dpell
offline
Link
 
In real football the offense wins the majority of passing battles. Why? Because they know what's going to happen. Where the route is going, who the hot receiver is, etc. So if a 70/50/50 CB and 70/50/50 WR are matched up in theory the WR should be getting open quite a bit and getting balls thrown his way. Right now in GLB the CB if he's set to close/aggressive coverage will be on the WR tighter than Bort's red sweater and never pay for playing tight coverage. He'll win 90+% of those battles. Most plays not a single WR is getting open when equally matched teams meet. So the passes are going to TE's and HB's.

No one wants CB's to become ineffective, simply to have more realistic reaction times. If the CB's react a little slowly or bite on a move so their success rate is only 60-70%, multiply that by two WR's on the field, and at least 50% of plays one WR will get open. That's about the right ratio because then the QB has to see him and throw it there, then the WR has to catch the ball, etc.

Last edited Aug 5, 2008 21:24:07
 
Midknight
offline
Link
 
CBs don't have to be as fast as WR's and usually aren't. They have the advantage of field position. I think Borts focusing to much on speed to balance matchups. I think vision/jumping/strength should be larger focuses when covering/fighting passes. WR who are really fast should be more likely to pick up the FS coverage if the FS has good vision. 2 cents
 
Painmaker
offline
Link
 
Originally posted by Bort

I hope they help out. These have been problems since day 1 of the game, and I think we just managed to bring them out through a combinations of things this season.


Thanks Bort, these are all great fixes.
 
SmithersOT
offline
Link
 
Good job! I am looking forward to seeing it in game
 
kenmoody
offline
Link
 
Bort, it sounds like these fixes are not yet in place. Any approximate ETA for them to go live? And will there be an announcement in the Recent Updates thread?

Many thanks for you tireless efforts!
 
Guppy, Inc
offline
Link
 
we have an early game tomorrow and I hope these are in place by then. we got upset last game because of this issue.
 
Sabrewolf
offline
Link
 
Originally posted by Bort
CB's were basically getting an immediate jump on the ball when thrown. I'm adding a delay on the jump based on vision agility and coverage distance. The result is that sometimes the CB gets a great jump on the ball and knocks it down while other times he waits a split second too long and doesn't get there in time. Combined with the above = botched coverage, basically.

My initial thought is this might hurt more Defenses than it might help, but willing to see the outcome of the testing. The CBs are supposed to anticipate and work to the ball action and I agree that a small delay might be warranted. I can't wait to see how the vision topic will affect the WRs that are IN coverage and those that are less-than-average builds that are wide open.


Originally posted by Bort
Fast CB's with poor agility playing on close vs Fast WR's often dash forward at the snap to get within the "close" cushion and are then unable to turn around quick enough to keep up with the speedy WR. I've made them back up a little at the snap instead and wait for the WR to make his move.

This is a step closer to the fix, yes. But countless posts were talking about the cushion that CBs LINED UP with and STAYED with - meaning the WR never passed them and they never pursued as they did last season. I know it's been addressed recently by some people AND Bort, but I didn't see a response from Bort that this was included in his testing and issues.


Originally posted by Bort
Anyway, just an update because I know people are waiting on this and I wanted to let everybody know I'm working on it. I want to make sure it's right before pushing it out there, though!

Thanks again, Bort! Glad to know you're on top of it. Nice job.

 
DONKEIDIC
pinto
offline
Link
 
Originally posted by Sabrewolf
Originally posted by Bort

Fast CB's with poor agility playing on close vs Fast WR's often dash forward at the snap to get within the "close" cushion and are then unable to turn around quick enough to keep up with the speedy WR. I've made them back up a little at the snap instead and wait for the WR to make his move.

This is a step closer to the fix, yes. But countless posts were talking about the cushion that CBs LINED UP with and STAYED with - meaning the WR never passed them and they never pursued as they did last season. I know it's been addressed recently by some people AND Bort, but I didn't see a response from Bort that this was included in his testing and issues.


Originally posted by Bort
Just wanted to post letting everybody know I haven't been around posting much today because I've been running tons of tests and modifying stuff to try and address this. I did a dump of the whole live database, so I'm able to test with any currently live teams (well, at least as they existed a day ago).

I've found a few things so far:

Fast CB's back up too fast compared to slow WR's on streak routes, due to the fact their their acceleration is a constant. I've made them match acceleration in this case and it seems to work so far. I've put a 20 speed 20 agility guy against a 70 speed 50 agility CB and the CB is all over him in general.

Agile WR's don't have a way to fake out equally agile CB's and get open. I'm increasing the effect of the head fake and juke SA's, and adding some reduced reaction time for defenders based on vision and agility and coverage distance. The result is that on some plays the CB will stay with the WR and on others he will not make the turn with the receiver until a split second too late.

CB's were basically getting an immediate jump on the ball when thrown. I'm adding a delay on the jump based on vision agility and coverage distance. The result is that sometimes the CB gets a great jump on the ball and knocks it down while other times he waits a split second too long and doesn't get there in time. Combined with the above = botched coverage, basically.

Fast CB's with poor agility playing on close vs Fast WR's often dash forward at the snap to get within the "close" cushion and are then unable to turn around quick enough to keep up with the speedy WR. I've made them back up a little at the snap instead and wait for the WR to make his move.

QB's with decent vision hardly ever miss an open man on a checkdown, which means they will ALWAYS take advantage of the situation. I'm making them slightly more likely to miss the open guy unless they have really high vision.

Risk calculations did not take the catching ability of the receiver into account as a very big part of the calculation. Being open is the major part. I'm tweaking that a little to be willing to pass to a guy if he's just way better than his defender, even if he's not wide open.

Anyway, just an update because I know people are waiting on this and I wanted to let everybody know I'm working on it. I want to make sure it's right before pushing it out there, though!


Second paragraph: Fast CB's back up too fast compared to slow WR's on streak routes, due to the fact their their acceleration is a constant. I've made them match acceleration in this case and it seems to work so far. I've put a 20 speed 20 agility guy against a 70 speed 50 agility CB and the CB is all over him in general.

 
Sabrewolf
offline
Link
 
Originally posted by DONKEIDIC
Second paragraph: Fast CB's back up too fast compared to slow WR's on streak routes, due to the fact their their acceleration is a constant. I've made them match acceleration in this case and it seems to work so far. I've put a 20 speed 20 agility guy against a 70 speed 50 agility CB and the CB is all over him in general.


I caught that. Was just hoping to also get clarification on why they were lining up the way they were. The quote DONKEIDIC gave only justified the "after the snap" part of the scenario. But will take it for what it's worth. Still should be better than what was happening the last couple games.
 
datongw
offline
Link
 

Originally posted by Bort

Fast CB's with poor agility playing on close vs Fast WR's often dash forward at the snap to get within the "close" cushion and are then unable to turn around quick enough to keep up with the speedy WR. I've made them back up a little at the snap instead and wait for the WR to make his move.


CB's first step should never be forward, even in bump and run, it's lining up close, jam and release. I've never seen a real life CB run up to the receiver after the ball is snapped to get into "close" cushion, just line up tight before the ball is snapped.
 
Link
 
Ya um, I'm glad this is being talked about but my specific problem hasn't been brought up I don't think.

http://goallineblitz.com/game/replay.pl?game_id=95361&pbp_id=1212178

On plays like that, it looks like my player is just being tossed out of the way. I have vision and agility softcapped at 48 with speed over 60, so this shouldn't be happening.

Also, plays like this:

http://goallineblitz.com/game/replay.pl?game_id=95361&pbp_id=1211212

It looks like I don't even have 5 points in agility.
 
voltageaav
offline
Link
 
Unless that happens on every play, that's not all that bad. The Defense isn't supposed to react perfectly even though 50 vision should help.
 
Kevin Smith
offline
Link
 
What I donīt undertand is why make route-running dependant on "speedster" SAs instead of, say, "Route Running"? Doesnīt make sense to me. So, we have an SA especially for shaking DBs, someone puts a ton of points in it, and you make it so that the other SA tree does it much better? Sounds like a recipe for some more whining.
 
Page:
 


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