Warrior General Games

The worse part is when you make the yardage, and then it says....... "______ and inches".

Part of the issue is that all the yardage is rounded anyway to nearest half yard, so trying to put in decimals would be pointless, because the 3.5 yards could be 3.25 or 3.74. You would be safer sticking with the whole numbers, since setting 3.5 could nail you half the time.

Originally posted by vladykins
Part of the issue is that all the yardage is rounded anyway to nearest half yard, so trying to put in decimals would be pointless, because the 3.5 yards could be 3.25 or 3.74. You would be safer sticking with the whole numbers, since setting 3.5 could nail you half the time.

Huh...???

If as you say "all the yardage is rounded anyway to nearest half yard"... then what are you talking about 3.25 or 3.74 for?
Where does 3.25 or 3.74 even come in if "ALL the yardage is rounded anyway to nearest half yard"?

Originally posted by dahman32
If .5's Exist as Yardage in Games, Sync AI to Recognize Them

Tired of seeing 3.5 yards to go, and then having to create some funky math scheme so it recognizes the .5, even though the AI does not.

And before someone says it "3 or 4 does not equal 3.5"


-Edited rant-



I believe the AI does recognize .5 in the settings dahman.
Mine is set up for example

1st and 0-2
1st and 2.1-5
1st and 5.1-10
1st and 10.1-20 etc etc.

Seems to recognize all ydg. with no phantom calls.

Originally posted by TribesJunkie
I believe the AI does recognize .5 in the settings dahman.
Mine is set up for example

1st and 0-2
1st and 2.1-5
1st and 5.1-10
1st and 10.1-20 etc etc.

Seems to recognize all ydg. with no phantom calls.



I actually thought it did as well, and then some random wonky situations were not, the computing AI gets confused.
But I think where you are getting is the 2.1 rounded to 2 the 5.1 rounded to 5 and the 10.1 rounded to 10

When you start adding 2.5, 5.5, and 10.5, what does that round to?

Originally posted by TribesJunkie
I believe the AI does recognize .5 in the settings dahman.
Mine is set up for example

1st and 0-2
1st and 2.1-5
1st and 5.1-10
1st and 10.1-20 etc etc.

Seems to recognize all ydg. with no phantom calls.



Originally posted by dahman32
I actually thought it did as well, and then some random wonky situations were not, the computing AI gets confused.
But I think where you are getting is the 2.1 rounded to 2 the 5.1 rounded to 5 and the 10.1 rounded to 10

When you start adding 2.5, 5.5, and 10.5, what does that round to?

The AI works off of whole numbers only. It does not recognize decimal points.

Originally posted by dahman32
Originally posted by vladykins

Part of the issue is that all the yardage is rounded anyway to nearest half yard, so trying to put in decimals would be pointless, because the 3.5 yards could be 3.25 or 3.74. You would be safer sticking with the whole numbers, since setting 3.5 could nail you half the time.

Huh...???

If as you say "all the yardage is rounded anyway to nearest half yard"... then what are you talking about 3.25 or 3.74 for?
Where does 3.25 or 3.74 even come in if "ALL the yardage is rounded anyway to nearest half yard"?




OK, let me say it simple.

It is first and 10, so you have exactly 10 yards to make a first down. You run a play that goes 6.4 yards, leaving you with 3.6 yards to go. The text will round it to 2nd and 3.5 yards. If you have a second play that goes exactly 3.5 yards, you'll get text that says 3rd and inches, not a first down.

So, you know the AI only accepts whole numbers. If you allow it to accept .5, you still have an issue because you'll say "my AI was to run on 3.5 and lower, but it did not fire on the second play listed above!" Based on the text, you would be correct, but in actuality, you were still .1 yards over 3.5, so your AI correctly didn't kick in.

Essentially, if you want more granularity with the AI, you also need to have the text itself more exact. Which just complicates the AI even more than it already does.

Does this make more sense?

Originally posted by vladykins
OK, let me say it simple.

It is first and 10, so you have exactly 10 yards to make a first down. You run a play that goes 6.4 yards, leaving you with 3.6 yards to go. The text will round it to 2nd and 3.5 yards. If you have a second play that goes exactly 3.5 yards, you'll get text that says 3rd and inches, not a first down.

So, you know the AI only accepts whole numbers. If you allow it to accept .5, you still have an issue because you'll say "my AI was to run on 3.5 and lower, but it did not fire on the second play listed above!" Based on the text, you would be correct, but in actuality, you were still .1 yards over 3.5, so your AI correctly didn't kick in.

Essentially, if you want more granularity with the AI, you also need to have the text itself more exact. Which just complicates the AI even more than it already does.

Does this make more sense?

So to summarize, you are saying you cannot trust what GLB is saying? hmmm, interesting

Scenario... you have a 4th and 1.2, a 4th and 1.6, and a 4th and 1.9...
which one is 4th and 1, which is 4th and 1.5, and which is 4th and 2?

Or are they all 4th and 1 or 4th and 2... because the game pronounces "4th and 1.5" as to be an presumably existent event.

The first would show 4th and 1, the second 4th and 1.5, and the third 4th and 2.

It's the joys of rounding in GLB that have frustrated folks forever, especially when they have, say, 3rd and 3, get three yards, but they don't get a first down.

Originally posted by vladykins

The first would show 4th and 1, the second 4th and 1.5, and the third 4th and 2.

It's the joys of rounding in GLB that have frustrated folks forever, especially when they have, say, 3rd and 3, get three yards, but they don't get a first down.

So if it is rounded to the nearest .5 in the sim, then why do you think it would be more frustrating if it's rounded in the AI as well, to match?

Originally posted by dahman32
Originally posted by vladykins


The first would show 4th and 1, the second 4th and 1.5, and the third 4th and 2.

It's the joys of rounding in GLB that have frustrated folks forever, especially when they have, say, 3rd and 3, get three yards, but they don't get a first down.

So if it is rounded to the nearest .5 in the sim, then why do you think it would be more frustrating if it's rounded in the AI as well, to match?

Because then you get folks asking for more detail in the sim, because it said 3.5 but it was actually 3.6 and didn't fire (my original point. Then more detailed AI to cover that, followed by more detailed text in the sim, etc.

Originally posted by vladykins
Because then you get folks asking for more detail in the sim, because it said 3.5 but it was actually 3.6 and didn't fire (my original point. Then more detailed AI to cover that, followed by more detailed text in the sim, etc.



http://makeameme.org/media/created/THERE-IS-NO-3gt9hk.jpg
There is no 3.6


Deer:

Why can't I have yellow grass if I see it over there?


Cow:

Because if they give you that yellow grass that you see, then they fear you might start asking for purple grass, which you don't see.

Originally posted by whodey08
The AI works off of whole numbers only. It does not recognize decimal points.

Are you certain about this?
I've not had a problem with conflicts or bad calls using what I put up there ^^^

Originally posted by TribesJunkie
Are you certain about this?
I've not had a problem with conflicts or bad calls using what I put up there ^^^



100% certain

+1 on the OP.

I hate when its 4th and 2.5 and I gain 2.5 and no first down.. make it in tenths then. So much easier but hey this is GLB and nothing logical has ever been fixed...