Originally posted by alindyl
Yeah this just came to mind too. Since it is possible to have plays in packages not in your current playbook, perhaps you have a gap in coverage, reverting to a basic tactic and that is the only play available. If perhaps in the playbook you have only 1-2 plays available, it has to call one of those if the Basic ai decides that should be called (which it did often on 1st downs)
In the second half you called HB Slam weak on 1st down every time except once (on a 2nd down).
In the first half It was called on various second downs and once on 1st down late in the second.
I'd check though your AI for anything special happening in the 3rd or 4th quarters on 1st down. And also check 2nd down conditions for gaps in overall or for 1st/2nd Q specific.
Ah perhaps not, since you said in your post while i was typing that you did check your playbook. But i'd still check through those AI conditions, and see what your basic tactic settings are to see if you have anything unusual, like it being set to 100% run or something.
I will. But what I really don't understand is how this has come about. I've not changed my AI since last season, just amended the outputs. In fact the AI has been in place for 4 seasons already, as has the playbook. Off to check Basic AI and every other percentage I can find on any page relating to the team now.
Edit: Ok so the ONLY input in my AI that calls anything other than a package may be the culprit however I don't see why. Its a 4th and 1 play, and checking settings it is set up as Down between 4 and 4, yards between 0 and 1. The play than calls 40% HB Blast using my elusive back and 60% HB Slam Weak using my power back. So this would account for the use of these plays if I had somehow made this the only call...however using the AI tester it is only ever called correctly and is so far down my AI tree it can't be superceding anything.
In addition to this the team that just played actually calls a package here and not specific plays, and they still had this issue. So whatever it is I don't think its this as it only exists in 1 of the two places the error has occurred.
Yeah this just came to mind too. Since it is possible to have plays in packages not in your current playbook, perhaps you have a gap in coverage, reverting to a basic tactic and that is the only play available. If perhaps in the playbook you have only 1-2 plays available, it has to call one of those if the Basic ai decides that should be called (which it did often on 1st downs)
In the second half you called HB Slam weak on 1st down every time except once (on a 2nd down).
In the first half It was called on various second downs and once on 1st down late in the second.
I'd check though your AI for anything special happening in the 3rd or 4th quarters on 1st down. And also check 2nd down conditions for gaps in overall or for 1st/2nd Q specific.
Ah perhaps not, since you said in your post while i was typing that you did check your playbook. But i'd still check through those AI conditions, and see what your basic tactic settings are to see if you have anything unusual, like it being set to 100% run or something.
I will. But what I really don't understand is how this has come about. I've not changed my AI since last season, just amended the outputs. In fact the AI has been in place for 4 seasons already, as has the playbook. Off to check Basic AI and every other percentage I can find on any page relating to the team now.
Edit: Ok so the ONLY input in my AI that calls anything other than a package may be the culprit however I don't see why. Its a 4th and 1 play, and checking settings it is set up as Down between 4 and 4, yards between 0 and 1. The play than calls 40% HB Blast using my elusive back and 60% HB Slam Weak using my power back. So this would account for the use of these plays if I had somehow made this the only call...however using the AI tester it is only ever called correctly and is so far down my AI tree it can't be superceding anything.
In addition to this the team that just played actually calls a package here and not specific plays, and they still had this issue. So whatever it is I don't think its this as it only exists in 1 of the two places the error has occurred.
Edited by Arayel on Nov 15, 2010 13:53:24






























