Instead of just 0 or 1 yard , add a half yard (or inches) selection on the input scenarios.

Not suggesting 1.5 , 2.5 , 3.5 ect ect. just a 0.5 , or "inches" , between the 0 and the 1 yard selections.

+1

I have mine entered using decimals, under the assumption that it already read that

Originally posted by wormser1971
I have mine entered using decimals, under the assumption that it already read that

try it with a 0 - 0.5 input , and run it through tester. I doubt you will get a match.

My suggestion is really only for the purpose of going for it on 4th and inches (but less than a yard)

could also be used on defense , but doubt anyone would worry about running a different D against 4th and inches than they would against 4th and 1. Offenses just may be more willing to go for it on 4th and inches than they would be on 4th and 1


addendum: the sim this season is not relevant to suggestion, I know it is very easy to pickup 1 yrd this season

Yes! Yes! Yes!

The Game doesn't not what to do when it sees .5 to go or on a .5 Yard Line. I have been begging for this to be fixed. It's what I named "Phantom Calls" and have you ever been watching a Game and be like, That's not my Defensive Play or I didn't call that Offensive Play.....? Well I have and what the sim does is revert back to your Basic AI Settings so I make sure these are set a certain way just for that reason. But bottom line Bane, They won't even admit what I know so I doubt they do what your suggesting,lol.

from a thread I started in the FAQ:

Originally posted by Antonine
All depends on if the sim does or does not read decimals from the OAI. If it does, we could use 4th& 0-0.5 to cover these very short yardage situations. But I've not seen (or looked for) a definitive answer about using .5 markers in the OAI inputs.

Originally posted by Bane
do you use an input of 0 - 0.5 , and then test that?

Originally posted by Antonine
Yes. Just made a test OAI with 2 inputs and 2 outputs. First input is 0-0.5 yards, all downs with 1 output ("Hail Mary" package).
Second input is 0.5-99 yards with 1 output ("Goalline" package). Tested it on AI tester. Any yardage up to 0.5 brings up Hail Mary, any yardage of 0.6 and above brings up Goalline. So the AI tester understands it, at least.


So it appears that the AI tester is able to read decimals, but the actual AI does not?

The reason all my OAI inputs read (for example)
input: 2nd and 0-3
input: 2nd and 3-6
input: 2nd and 6-100

is so there is no "phantom" plays as described by sehorn31 in the post above. I don't leave any gaps. I do same in my DAI's.

Originally posted by sehorn31
The Game doesn't not what to do when it sees .5 to go or on a .5 Yard Line. I have been begging for this to be fixed. It's what I named "Phantom Calls" and have you ever been watching a Game and be like, That's not my Defensive Play or I didn't call that Offensive Play.....? Well I have and what the sim does is revert back to your Basic AI Settings so I make sure these are set a certain way just for that reason. But bottom line Bane, They won't even admit what I know so I doubt they do what your suggesting,lol.

So your experience is that the sim cannot understand 0.5 yards in an AI, even though the AI tester does understand it? I must admit, despite using 0.5 yard increments in my OAI sometimes, I've never paid close enough attention to whether the sim actually calls the right plays at those times. I haven't seen phantom calls (plays from outside my packages) though, I'm pretty sure.

Originally posted by Antonine
So your experience is that the sim cannot understand 0.5 yards in an AI, even though the AI tester does understand it? I must admit, despite using 0.5 yard increments in my OAI sometimes, I've never paid close enough attention to whether the sim actually calls the right plays at those times. I haven't seen phantom calls (plays from outside my packages) though, I'm pretty sure.

Well known fact, confirmed by admins. The AI works in integers only.

So if you have separate inputs for 0-0.5 and 0.5-1, does it go with whichever is highest up in the AI for anything between 0 and 1 (even if that first input is 0-0.5, it reads it as 0-1), and never looks at the second input?

+1

+1

+1