User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > check downs and pro slants - NOT A BUG - CLOSED
Page:
 
Dr. E
offline
Link
 
I'm having an issue in which the check down I have set isn't being used with the Pro Slants. I have the play in two different packages and instead of using my custom selection, it is using the default check downs. Seen it now in two games. Anyone else noticed this bug?
Edited by VolBrian on Oct 14, 2011 12:39:23 (Closed)
 
VolBrian
Rocky Top
offline
Link
 
Could you provide examples/replays along with intended progressions please?

Also, do you allow audibles and if so which ones?
 
climberpete
offline
Link
 
I just checked mine from two different teams, each using different progressions and both looked okay.
 
Dr. E
offline
Link
 
Originally posted by VolBrian
Could you provide examples/replays along with intended progressions please?

Also, do you allow audibles and if so which ones?


Sure, I've noticed it in three games now, but the latest game from this morning was private and I don't recall which one I first noticed, but it was recent. This game http://goallineblitz.com/game/game.pl?game_id=1793105 has 2 though.

http://goallineblitz.com/game/replay.pl?game_id=1793105&pbp_id=8761124
http://goallineblitz.com/game/replay.pl?game_id=1793105&pbp_id=8760904


I've changed the check downs since, but it was probably 1/2/te/hb/fb or 2/te/hb/1/fb. That's what I use most often.

My first thought was that I had a "hole" in my input/outputs and the GLB logic engine was just calling the play. I looked through though and nothing. If the first input/out that was suppose to work in the quarter override didn't run then the base input/output should of gotten it.
Edited by Dr. E on Oct 6, 2011 15:10:43
 
CDZYO
offline
Link
 
Does the QB have any favorite targets set? And, yeah, that looks like the default progression.
 
AngryDragon
offline
Link
 
I have had problems with checkdowns in general for the last couple seasons. Some TE routes the QB will only target the TE if he is first under the custom checkdowns. A good example is the I form HB streak. If you set the TE to the first custom checkdown the QB will almost never look at anybody else.

Other problems are too hard to nail down and prove because so many variables can add to the problem. This really needs borts attention but I just don't have the words to describe all the problems. If I had to sum it up I would say that QBs stick to the first receiver for too long under most conditions. That and quick read works too well and not often enough.

So I would ask that the developer shave some time off of QBs normal reads and add some time to quick reads but make it so they just happen more often. Trust me the gap between normal reads and quick reads is big enough for this to work well.

Just my 2 cents. My team has passed 99% of the time since season 17 and this stuff has been a problem for a while.
Edited by AngryDragon on Oct 6, 2011 15:59:17
Edited by AngryDragon on Oct 6, 2011 15:58:38
Edited by AngryDragon on Oct 6, 2011 15:57:28
 
SG✬21
offline
Link
 
Originally posted by AngryDragon
I have had problems with checkdowns in general for the last couple seasons. Some TE routes the QB will only target the TE if he is first under the custom checkdowns. A good example is the I form HB streak. If you set the TE to the first custom checkdown the QB will almost never look at anybody else.

Other problems are too hard to nail down and prove because so many variables can add to the problem. This really needs borts attention but I just don't have the words to describe all the problems. If I had to sum it up I would say that QBs stick to the first receiver for too long under most conditions. That and quick read works too well and not often enough.

So I would ask that the developer shave some time off of QBs normal reads and add some time to quick reads but make it so they just happen more often. Trust me the gap between normal reads and quick reads is big enough for this to work well.

Just my 2 cents. My team has passed 99% of the time since season 17 and this stuff has been a problem for a while.


ya if you need enough replays of anything just ask dragon. Pass only team pretty much that has seen every pass play countless times.

I to have noticed that the QB sticks to the first receiver way to long no matter what. Even if it set for just 1 progression, he'll watch for every then switch to someone who is 20+ yards down field and now its not as favorable of passing situation. If he'd spend ample amount of time on the first target but not to much then if he doesn't like what he see's he'll switch to the next before he is to far down the field.
 
jpjn94
doc ock
offline
Link
 
Not trying to argue there isn't an issue, but the complaint is just too vague to really narrow down the problem. There is probably an issue with the AI, but I could be wrong; however...

Shows you can choose another receiver on that play http://goallineblitz.com/game/replay.pl?game_id=1793241&pbp_id=8884262
Shows your QB can move on to another receiver http://goallineblitz.com/game/replay.pl?game_id=1793241&pbp_id=8889844


The problems you see and what AngryDragon describes is accurate, but keep in mind what level you're playing at. At lower level your QBs could have a lot lower Vision to help them move through progressions, won't have Quick Read, and may not have Quick Release. Again all of those examples are only opinion and may not actually help the progressions, but there are other issues that could be involved in the problem you're seeing.


Now to agree with AngryDragon, at the lower levels there is an issue with how builds work as they're expected to still play by the same rules the higher leagues play on. So you'll have to have all of those abilities to excel in the passing game at the lower levels. That probably needs to be looked at as at the lower levels you often see plays like this...

http://goallineblitz.com/game/replay.pl?game_id=1818417&pbp_id=9268022

The FB is wide open, it's a Casual game so it's using no progressions and the TE is focused on too long. This is similar to the OP's complaint. So he's replays to look like his game plan followed the basic progressions; granted there could still be issues with the AI.

Just my random late night thoughts...

 
Dr. E
offline
Link
 
Originally posted by CDZYO
Does the QB have any favorite targets set? And, yeah, that looks like the default progression.


No favorites.
 
AngryDragon
offline
Link
 
Originally posted by Dr. E
Sure, I've noticed it in three games now, but the latest game from this morning was private and I don't recall which one I first noticed, but it was recent. This game http://goallineblitz.com/game/game.pl?game_id=1793105 has 2 though.

http://goallineblitz.com/game/replay.pl?game_id=1793105&pbp_id=8761124
http://goallineblitz.com/game/replay.pl?game_id=1793105&pbp_id=8760904


I've changed the check downs since, but it was probably 1/2/te/hb/fb or 2/te/hb/1/fb. That's what I use most often.

My first thought was that I had a "hole" in my input/outputs and the GLB logic engine was just calling the play. I looked through though and nothing. If the first input/out that was suppose to work in the quarter override didn't run then the base input/output should of gotten it.


Looking at OPs examples I would assume both are default progressions. The way the QB bounced back to the TE in the second example without extreme pressure makes me think that at least the second example was default. The first only has the QB stick with the TE which could be default or custom if the TE was the first target.

In the two examples given I am not seeing what normally drives me bonkers. Of course that is why I have kept quiet on this topic for so long. It really is hard to find consistent examples of this stuff. I still blame the QB targeting the primary receiver too long. The most common situation is the QB sticking with the primary until he is under pressure. At that point custom progressions go out the window. There are other situations where some of the older plays seem to have progressions pre-programmed and fighting them with custom checkdowns is just not worth it.

Personally, I try to know the default 2nd read for most the plays and just use default progressions. I have a couple game plan packages that I tend to use custom checkdowns and the plays and checkdown choices change from game to game.

Not sure if that helps your cause OP but I totally feel your pain on this issue.
 
VolBrian
Rocky Top
offline
Link
 
I actually am in agreement with the above suggestions that the QB is targeting the first guy too long, but it's not something we can really process here. I think a suggestion thread for some tweaks to that might be in order.

As far as the OP, I would be happy to grab a look at your OAI and test things out to see what's what, but by your own admission the progressions have already been changed so I'm not really sure how we can proceed with investigating this as a possible bug.
 
Dr. E
offline
Link
 
Originally posted by VolBrian
I actually am in agreement with the above suggestions that the QB is targeting the first guy too long, but it's not something we can really process here. I think a suggestion thread for some tweaks to that might be in order.

As far as the OP, I would be happy to grab a look at your OAI and test things out to see what's what, but by your own admission the progressions have already been changed so I'm not really sure how we can proceed with investigating this as a possible bug.


Can't, it will have to be tested or, just leave the thread active in the appropriate spot for more comments should they come. But, I'll gladly grant you access if you still want to give it a look by fresh eyes to make sure it's not something in the AI?
Edited by Dr. E on Oct 7, 2011 14:20:53
 
VolBrian
Rocky Top
offline
Link
 
Sure, I'll be happy to. Will be Monday morning before I get to it.

As for testing, this isn't something we can create a test request for ourselves based on so little evidence that we are unable to prove. In other words, we would to have it as a filed bug in order to do so and it can't get that far at this point. Kind of a "catch 22" no? yukyukyukyukyuk
 
Dr. E
offline
Link
 
Originally posted by VolBrian
Sure, I'll be happy to. Will be Monday morning before I get to it.

As for testing, this isn't something we can create a test request for ourselves based on so little evidence that we are unable to prove. In other words, we would to have it as a filed bug in order to do so and it can't get that far at this point. Kind of a "catch 22" no? yukyukyukyukyuk


GM sent.
 
Dr. E
offline
Link
 
Originally posted by VolBrian
Sure, I'll be happy to. Will be Monday morning before I get to it.

As for testing, this isn't something we can create a test request for ourselves based on so little evidence that we are unable to prove. In other words, we would to have it as a filed bug in order to do so and it can't get that far at this point. Kind of a "catch 22" no? yukyukyukyukyuk


Back yet? Gave you access.
 
Page:
 


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