User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > RESOLVED BUGS > wide open HB looked at but not thrown to - WILL NOT RESOLVE #130
Page:
 
cosmoxl
offline
Link
 
http://goallineblitz.com/game/replay.pl?game_id=1123824&pbp_id=6551681

what's the problem here?
Edited by Catch22 on Apr 25, 2010 12:35:15
Edited by Sik Wit It on Apr 18, 2010 22:43:25 (needs qa - sik)
Edited by Squab on Apr 14, 2010 20:33:43 (LIKELY NOT A BUG)
 
Bukowski
offline
Link
 
Ouch.
 
Link
 
I believe the QB and the HB got in a fight the night before...

you didn't hear about this on espn?
 
Squab
offline
Link
 
Hm. I don't think this is a bug really. The WR was also open, and was much closer. The HB would have gotten the ball, but wouldn't have gone far since it would have taken so long for the ball to get over there.

He probably should have thrown it to the HB early on there, but didn't, I would assume because of the "Open Man" tactic. Plus the WR called for the ball

I don't think it's a bug, just an unfortunate instance.
 
cosmoxl
offline
Link
 
Originally posted by Squab
Hm. I don't think this is a bug really. The WR was also open, and was much closer. The HB would have gotten the ball, but wouldn't have gone far since it would have taken so long for the ball to get over there.

He probably should have thrown it to the HB early on there, but didn't, I would assume because of the "Open Man" tactic. Plus the WR called for the ball

I don't think it's a bug, just an unfortunate instance.


well, it stinks.
 
Squab
offline
Link
 
I know, like I said, that's very unfortunate. At least you won the game though.
 
Eamz
offline
Link
 
Not that you want to post your QB settings for all to see, but could it be due to that?

As Squab mentioned, probly not a bug, but I'd be interested to know if you have it favored to Route Distance and/or Dump Pass (I know it's not a Dump Pass, but it could factor into it)
 
tragula
title
offline
Link
 
There are many reason why a QB will skip an open receiver like that:
1. HB catching skills are too low (which increases risk factor)
2. HB route just didn't developed enough, barely crossed the LOS when the WR got the QB attention.
3. Failed vision check
4. Maybe QB setting (I am not very hot for this option)
 
Link
 
Unless you are the QB we never really know what his settings are so here's the deal.

- If you used single plays in the OAI vs Packages then you would have to see how you set your check downs.
- If you used packages then you would have to rely more on your QB settings.
- You QB is set to specific receiver's
- Your QB Vision is at Cap 1 maybe Cap 2
- Your QB doesn't like being told what to do.

If you watch the replay enough you will see the HB is about a 1/2 yard back in distance from the HB so it should have went his way hands down. The WR might have that gay VA on that makes the QB throw the ball his way. You were hosed.
 
Guppy, Inc
offline
Link
 
If this isnt a bug, then whats the purpose of the QB line? its probably a failed vision check, but i see this type of play far too often where the qb skips a wide open player even tho he was in the progression. i'd like to see more examples and have catch/bort let us know why it happens.
 
kuaggie
offline
Link
 
QB Tactics- run route vs. Open man?
 
SoCalWhoDat
offline
Link
 
Originally posted by kuaggie
QB Tactics- run route vs. Open man?


I have to say that what I've found in these types of situations is that it doesn't matter if your QB is set to 100% Open Man. If the HB's route is technically a "long" route and you have him as the 1st or 2nd progression option, the QB will simply look him off with no intention of ever throwing it to him, regardless of pass-rush pressure or how open he is. Almost as if there's something in place to override an extreme open man setting on certain longer routes. On "medium" to "short" designated routes, the QB tends to get it out more quickly.

Could be wrong, but these passes have been a problem for us as well and the only time I've seen it rectified is when I take away the HB as the first or second progression choice on those longer routes.

edit: if i wasn't at work, I'd be able to link some examples......i'll try and log on later and update this post.....don't hold your breath though
Edited by sleepingazure on Apr 15, 2010 03:29:42
 
cosmoxl
offline
Link
 
OK guys. glad this is getting a little traction.

QB settings were 75 toward open man.

the WR who called for the ball does NOT have "go to guy" VA.

the HB who was passed up made several other difficult catches this game - IOW, he's a good target.

the QB has 87 vision.

as you can see by looking at the QB progression line, my custom progression was WR3, HB....and so on. That was the "under swing" play, so the HB "route" is short. the QB should not be waiting for a route completion distance on that play.

I'm thinking that because WR3 was first in the progression and because he called for the ball, the QB defaulted back to him. That's probably a good policy to have, but it stinks in cases like this.

 
cosmoxl
offline
Link
 
http://goallineblitz.com/game/replay.pl?game_id=1123825&pbp_id=7384809

bump. check out the TE in this play. QBs passing up wide open receivers has to stop. as best I can tell there was *nobody* covering the TE, yet he doesn't get the ball. same QB as before.
 
Sik Wit It
offline
Link
 
That last example is REALLY bad. This is one of those gray areas for bugs mods, since it's maybe not technically a bug, but rather bad mechanics. I'd really like to see this looked at though, and I think a lot of GLBers share my sentiments, so I'll send to Catch.
 
Page:
 


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