User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Where is the FB going on this play?
Page:
 
tragula
title
offline
Link
 
Originally posted by blankspace
It could either be a failed vision check (you guys obviously hate this answer) or just a very bad block selection from coding.


I thought that a failed vision check will make the FB continue in his original path, not sent him to block a guy he can only see from the corner of his eye.
Edited by tragula on Oct 27, 2009 07:52:31
 
blankspace
offline
Link
 
Originally posted by tragula
Originally posted by blankspace

It could either be a failed vision check (you guys obviously hate this answer) or just a very bad block selection from coding.


I thought that a failed vision check will make the FB continue in his original path, not sent him to block a guy he can only see from the corner of his eye.


It's hard to say because I obviously don't know the exact coding, but for some reason I want to say that if your player fails a vision check, he might not continue his original path. He might pass another vision check to go block another defender that's closer to him than the original defender he was suppose to block.

This isn't the right answer, just a theory.
 
blankspace
offline
Link
 
Originally posted by Sixx
Originally posted by blankspace

It could either be a failed vision check (you guys obviously hate this answer) or just a very bad block selection from coding.


I can buy the failed vision check, but what I don't buy, is the player failing it so bad that he can't see the defender who is right in front of him. If this is a failed vision check then the "vision check fail" is bugged, imo.

No reason a player shouldn't see a guy that is right in front of him and is only 6 feet away.


Completely understood and 100% agreed if my statement were fact. I'm just a bugs mod that tries to throw ideas out just like the next person. I do know that dots don't have eyes so it's not really that he can't see him, it's just programmed that way. If the vision check is true, perhaps the FB would have a greater chance of making a passed vision check if the selected defender to block is closer to him, and vice-versa if he was farther way.
 
Link
 
Originally posted by blankspace
Originally posted by tragula

Originally posted by blankspace


It could either be a failed vision check (you guys obviously hate this answer) or just a very bad block selection from coding.


I thought that a failed vision check will make the FB continue in his original path, not sent him to block a guy he can only see from the corner of his eye.


It's hard to say because I obviously don't know the exact coding, but for some reason I want to say that if your player fails a vision check, he might not continue his original path. He might pass another vision check to go block another defender that's closer to him than the original defender he was suppose to block.

This isn't the right answer, just a theory.



Good theory, it makes sense to work that way with mulitple checks per tick
 
.spider.
Lead Mod
offline
Link
 
It has to be blocking priority because before he could get to the LB the LG got pancaked leaving him "free" and the FB must have DT higher on the priority list and took off for him.

Code issue IMO
 
RMiller517
offline
Link
 
Thread locked by moderator.
 
Page:
 


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