User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > LT tries to sack own QB - NOT A BUG - CLOSED
Page:
 
robponce
offline
Link
 
Originally posted by braxtron
So, any update on this problem?


Originally posted by changelog, June 23rd

- Additional logic added to pass blocker selection to address some exploity blitzes and improper G/OT switching vs 3 man lines


We're slowly getting there it seems.

Hopefully this helps a little. We'll see. No idea what Bort actually put in, but do know he's aware and working on the issue.
 
braxtron
offline
Link
 
Originally posted by robponce
We're slowly getting there it seems.

Hopefully this helps a little. We'll see. No idea what Bort actually put in, but do know he's aware and working on the issue.


Thanks for the update. I hadn't seen that from June 23. I really hope issues like this one aren't around next season.
 
braxtron
offline
Link
 
Is there any way to run this exact 'possibly buggy' play (along with the exact same defensive play) on the new test server and see if the problem was fixed?
 
braxtron
offline
Link
 
Originally posted by braxtron
Is there any way to run this exact 'possibly buggy' play (along with the exact same defensive play) on the new test server and see if the problem was fixed?


 
VolBrian
Rocky Top
offline
Link
 
Originally posted by braxtron

Is there any way to run this exact 'possibly buggy' play (along with the exact same defensive play) on the new test server and see if the problem was fixed?



No, not really. You could run this play 100,000 times and not see this happen again. I suspect this is one of the situations where this is just something crazy that happened one time but not necessarily a bug because it's a one time deal. Could have just been a mix of different things as far as play choice, team and player tactics, blitzes, etc. etc. etc.

If it reoccurs or has already reoccurred, I"m sure we would know it at this is weird enough to be brought here to this forum, however, there is no real way to test this and no way to even talk about a fix as there's no repetitive issue that can be addressed.

I continue to leave this thread open though in case/hopes of it happening again and being brought here.
 
toobad4u_00
offline
Link
 
Originally posted by braxtron
This is either a bug or bad coding. Could someone please enlighten me as to which it is?


I vote bad coding.. working as intended. Which is, contrary to popular belief here, a BUG.
 
VolBrian
Rocky Top
offline
Link
 
Originally posted by toobad4u_00
I vote bad coding.. working as intended. Which is, contrary to popular belief here, a BUG.


It's nothing until it's replicated in the sim. Can't be a bug, can't be bad coding unless players are actually doing this more than this one instance.
 
toobad4u_00
offline
Link
 
Originally posted by VolBrian
It's nothing until it's replicated in the sim. Can't be a bug, can't be bad coding unless players are actually doing this more than this one instance.


We see variations of poor blocking schemes used in almost every game.. whether it causes this much issue or not is irrelevant. It seems in this case the LT correctly sees that the first person that will get to the QB will be the CB, which he should have never seen in the first place under any circumstance and it should also be taken into account that he could never have possibly taken an angle to cut off the CB so he should never try to do so anyways.... should not be part of his vision check period. I submit that it is part of the quirky vision check system bort has in place and is thus part of a simulation bug that he will say is working as intended but it is still a stupid bug.
Edited by toobad4u_00 on Jul 8, 2010 14:11:18
 
pdiddy4
offline
Link
 
Originally posted by VolBrian
It's nothing until it's replicated in the sim. Can't be a bug, can't be bad coding unless players are actually doing this more than this one instance.


It is impossible to know how many times this "problem" (I won't call it a bug) has happened as it would be impossible to look at every play from every game for this issue. What is logical, at least to me, is that if this was caught by someone perusing the play-by-play, it is likely that this "problem" has happened more than once. In other words, the likelihood that this happened once and was caught by someone randomly looking at plays is infinitesimally small. i.e. this has probably happened before/again, and went unnoticed or unreported.
Edited by pdiddy4 on Jul 12, 2010 12:57:12
 
VolBrian
Rocky Top
offline
Link
 
Possibly or maybe even probably so, but the problem is that without those replays, we have no way of knowing the frequency of the issue or being any closer to know what is causing it or caused it.

Until we have at least two instances of it, we can only assume it was a one-time thing.
 
Time Trial
offline
Link
 
1) Your TE is blocking on the wrong side.
2) My Tackle was not on the field
3) Big Heart.
 
VolBrian
Rocky Top
offline
Link
 
Ok, it's been 10 days with no activity on this thread and much longer since any replays were even mentioned. Closing this down as no further examples available and not a bug.
 
Page:
 


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