User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > QB's vision laser gets stuck mid-play - DUPLICATE THREAD - CLOSED
Page:
 
csull36
offline
Link
 
Originally posted by VolBrian
Shouldn't pause where? You asked the QB to check the FB three times in a row. He does this. His vision cone doesn't move because you held the FB in to block and he's standing directly in front of the QB. If the FB was only listed once in his progressions the cone would have kept moving to the next check.


He shouldn't pause to check for a player that is not even running a route! How does this not make sense to you?
 
csull36
offline
Link
 
Originally posted by VolBrian
Originally posted by csull36

WR2 WR2 FB FB FB


With this in mind, notice that the QB is following through the progressions correctly, it just looks stuck since the FB stays in to block and he is the final three in the order right in front of the QB. After he has gone through all 5 progressions, he "unfreezes" so to speak and looks for the open man according to his own tactics.

In the future, make sure you aren't allowing your FB to be held in on pass routes that he is listed so heavily in the progression.

Not likely a bug


The fact that I have him look at the FB for more than one progression (which is a viable OC strategy) just accentuates the bug. There would obviously be a pause (although less noticeable) for instances where a player is only checked once. But are you trying to say that we should never have the hold player x in to block checked if we have them running any routes in our AI? That defeats the entire purpose of the checkbox in the first place.
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by csull36
If a QB holds in a player to block, that player should then be eliminated from his progressions


This is a suggestion.

Originally posted by csull36
instead of a "glitch" where the qb does nothing for a few ticks.


It is not a "glitch", the QB is doing exactly what you told him to do.

Originally posted by csull36
He shouldn't pause to check for a player that is not even running a route! How does this not make sense to you?


You have conflicting actions in your AI. If you did not use custom progressions, he would have skipped the FB because the FB is not in a route. Since you used custom progressions, the QB is going to check exactly what you told him to do. Since you know how to run an offense, you should know better than to tell your QB to check a FB that you are telling to pass block. As you clearly did not intend for your QB to check a pass blocking FB, I'm sorry this happened to you, but custom progressions are there to grant you complete control of who the QB looks at, even if you are telling the QB to look at a HB, FB, or TE you have told to pass block.
Edited by VolBrian on Sep 24, 2010 14:43:40
Edited by VolBrian on Sep 24, 2010 14:42:14
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by csull36
But are you trying to say that we should never have the hold player x in to block checked if we have them running any routes in our AI? That defeats the entire purpose of the checkbox in the first place.


Only on plays you plan to target that player with consecutive custom checks.
 
csull36
offline
Link
 
Originally posted by VolBrian
Originally posted by csull36

If a QB holds in a player to block, that player should then be eliminated from his progressions


This is a suggestion.

Originally posted by csull36

instead of a "glitch" where the qb does nothing for a few ticks.


It is not a "glitch", the QB is doing exactly what you told him to do.

Originally posted by csull36

He shouldn't pause to check for a player that is not even running a route! How does this not make sense to you?


You have conflicting actions in your AI. If you did not use custom progressions, he would have skipped the FB because the FB is in a route. Since you used custom progressions, the QB is going to check exactly what you told him to do. Since you know how to run an offense, you should know better than to tell your QB to check a FB that you are telling to pass block. As you clearly did not intend for your QB to check a pass blocking FB, I'm sorry this happened to you, but custom progressions are there to grant you complete control of who the QB looks at, even if you are telling the QB to look at a HB, FB, or TE you have told to pass block.


Look, I could care less about what happened on this play, but it's something that should be fixed, and you're showing a lot of ignorance as to how the system works. I did not "tell" the FB to pass block. I am "telling" him to run a route and "telling" my QB to look at him. However, due to overload blitzes, I like to keep the audible boxes checked. You know what an audible is right? It is a deviation from the called play. The FB has changed from what I "told" him to do. Consequently, the QB should also change based on the audible. It is really simple.


 
csull36
offline
Link
 
Originally posted by VolBrian
Originally posted by csull36

But are you trying to say that we should never have the hold player x in to block checked if we have them running any routes in our AI? That defeats the entire purpose of the checkbox in the first place.


Only on plays you plan to target that player with consecutive custom checks.


lol, you do realize that the checkbox applies to ALL plays, you cannot select it for individual plays. Have you ever looked at an AI?
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by csull36
Look, I could care less about what happened on this play, but it's something that should be fixed, and you're showing a lot of ignorance as to how the system works. I did not "tell" the FB to pass block. I am "telling" him to run a route and "telling" my QB to look at him. However, due to overload blitzes, I like to keep the audible boxes checked. You know what an audible is right? It is a deviation from the called play. The FB has changed from what I "told" him to do. Consequently, the QB should also change based on the audible. It is really simple.


lol, I'm fully aware of audibles man. Look, I don't know how else to put this, but you just can't use custom progressions in the way that you are trying to do so and expect the QB to do something different from what you are specifically telling him to do. Whether you are allowing the QB to audible him in to pass block, specifically select him to do so in the play itself, or leave it up to your basic settings is irrelevant here. The key is your custom progressions. The QB will look at the receivers you tell him to look at no matter what. If you allow the audible to be called, he's still gonna look if the FB is kept in. That's the way Bort designed it to work. Changing it to default off of your chosen custom progressions would be a suggestion, not a bug, and would defeat the point of custom progressions imo.

Either way, the QB staring at the FB is not a bug because you have told him to do so, and the QB following the progressions you gave him to follow is also working as intended.
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by csull36
lol, you do realize that the checkbox applies to ALL plays, you cannot select it for individual plays. Have you ever looked at an AI?


There are other ways to select your FB to stay in to pass block as you should well know.
 
csull36
offline
Link
 
Originally posted by VolBrian
Originally posted by csull36

Look, I could care less about what happened on this play, but it's something that should be fixed, and you're showing a lot of ignorance as to how the system works. I did not "tell" the FB to pass block. I am "telling" him to run a route and "telling" my QB to look at him. However, due to overload blitzes, I like to keep the audible boxes checked. You know what an audible is right? It is a deviation from the called play. The FB has changed from what I "told" him to do. Consequently, the QB should also change based on the audible. It is really simple.


lol, I'm fully aware of audibles man. Look, I don't know how else to put this, but you just can't use custom progressions in the way that you are trying to do so and expect the QB to do something different from what you are specifically telling him to do. Whether you are allowing the QB to audible him in to pass block, specifically select him to do so in the play itself, or leave it up to your basic settings is irrelevant here. The key is your custom progressions. The QB will look at the receivers you tell him to look at no matter what. If you allow the audible to be called, he's still gonna look if the FB is kept in. That's the way Bort designed it to work. Changing it to default off of your chosen custom progressions would be a suggestion, not a bug, and would defeat the point of custom progressions imo.

Either way, the QB staring at the FB is not a bug because you have told him to do so, and the QB following the progressions you gave him to follow is also working as intended.




What don't you understand about "AUDIBLE"

I'm pretty sure it's not working as intended.
 
csull36
offline
Link
 
Originally posted by VolBrian
Originally posted by csull36

lol, you do realize that the checkbox applies to ALL plays, you cannot select it for individual plays. Have you ever looked at an AI?


There are other ways to select your FB to stay in to pass block as you should well know.


That have nothing to do with this scenario.
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by csull36


What don't you understand about "AUDIBLE"

I'm pretty sure it's not working as intended.


I understand you want the QB to audible out of your custom progressions along with the backs pass blocking, but that's not currently part of the game and therefore a suggestion.

Because of this, it makes your QB's cone stick on the FB through 3 checks not a bug.
 
TruthHammer
Lead Bugs Mod
offline
Link
 
Originally posted by VolBrian
Originally posted by TruthHammer
Functionally, it is working as intended, but...
Originally posted by VolBrian
it just looks stuck


this is why it IS a bug.


What should he do? The FB is standing directly in front of the QB, the progressions call for him to look at the FB on three consecutive checkdowns, the QB stands there and does what the OC said and stares at the FB for a few seconds. No bug about it.


You're arguing function with me, and as I already said, functionally it is working as intended. My point is that if the display appears to show something different than what is actually happening - and in the above quote, you already admitted that it does, he is not really looking where the pointer is - then this is a bug.
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by TruthHammer
You're arguing function with me, and as I already said, functionally it is working as intended. My point is that if the display appears to show something different than what is actually happening - and in the above quote, you already admitted that it does, he is not really looking where the pointer is - then this is a bug.


I think you misunderstood that then. The custom progressions called for the QB to check WR2 twice, which he does, and then check the FB three times straight, which he does. The QB had apparently audibled the FB in to pass block, so the FB is directly in front of the QB when he checks to him. Checking to him three times consecutively is why the QB's "vision laser" appears to "get stuck mid-play". If the FB was only listed once, the QB would have checked once and passed on to the next check in the progression. So, the display is showing exactly what the offensive settings have called for, even if they were unintentionally set to do so.

The Vision cone is working exactly as it is supposed to according to the custom progression.
Edited by VolBrian on Sep 24, 2010 19:00:07
 
tautology
offline
Link
 


So, working as intended (as coded), but not working as expected or hoped.

It makes little sense for a QB to check to a man that he audibled to stay in, whether once, twice or 5 times. And I think you either have to call that a bug or just bad coding.


I have a feeling Bort would agree (just guessing).
 
TruthHammer
Lead Bugs Mod
offline
Link
 
Originally posted by VolBrian
Either way, the QB staring at the FB is not a bug because you have told him to do so.


The replay does not show the QB staring at the FB. It shows him staring at the spot that WR2 just left. Stare at an empty spot in the middle of the field is not in the progression.
 
Page:
 


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