User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Issue with FG distance in AI - CLOSED - NOT A BUG
Page:
 
spindoctor02
offline
Link
 
In our latest scrim, we had the AI set to kick FGs on 4th down when between the 35 yard line and the goal, when its more than 4th and 2. This input is 2nd from the top of the AI, behind only a 4th and short input. None of the special circumstances are checked, so if we are between the 35 and the goal, we should be kicking FGs.

First Occurrence: Q1 12:39 4th & 9.5 on OPP 35 - Punt
http://goallineblitz.com/game/replay.pl?game_id=1703669&pbp_id=8892577

Second Occurrence: Q4 11:42 4th & 7 on OPP 35 - Punt
http://goallineblitz.com/game/replay.pl?game_id=1703669&pbp_id=8895736

Third Occurrence: Q4 2:26 4th & 18.5 on OPP 35 - FG
http://goallineblitz.com/game/replay.pl?game_id=1703669&pbp_id=8896223

I tested all thee situations in the AI tester, and all came back with FG as the only possible matching outcome. I also checked, and there isn't anything in the Quarter Specific sections that would override the generic FG input.
Edited by TruthHammer on Jun 19, 2011 21:37:29 (Closed - not a bug)
 
kuaggie
offline
Link
 
I know once upon a time the FG distance thing was so bugged bort just told people to manually set it in 5 yard increments instead. You can go with that for now, although I agree this is something to look into. Is this the first game it's happened in?
 
Pwned
offline
Link
 
Send me over some GM access so I can take a look. (include O AI privileges)
 
Androth
offline
Link
 
Originally posted by Pwned IRL
Send me over some GM access so I can take a look. (include O AI privileges)


 
spindoctor02
offline
Link
 
Originally posted by kuaggie
I know once upon a time the FG distance thing was so bugged bort just told people to manually set it in 5 yard increments instead. You can go with that for now, although I agree this is something to look into. Is this the first game it's happened in?


Maybe I wasn't clear, but in the "Max FG Distance" box (or whatever its called), we have that blank, and only have it set for certain yardages. I never liked having the game set for you what the max distance was, as it made it really difficult to make sure you had all your bases covered.

Originally posted by Pwned IRL
Send me over some GM access so I can take a look. (include O AI privileges)


I'll get you some access here shortly.
 
Novus
offline
Link
 
Originally posted by spindoctor02
In our latest scrim, we had the AI set to kick FGs on 4th down when between the 35 yard line and the goal, when its more than 4th and 2. This input is 2nd from the top of the AI, behind only a 4th and short input. None of the special circumstances are checked, so if we are between the 35 and the goal, we should be kicking FGs.

First Occurrence: Q1 12:39 4th & 9.5 on OPP 35 - Punt
http://goallineblitz.com/game/replay.pl?game_id=1703669&pbp_id=8892577

Second Occurrence: Q4 11:42 4th & 7 on OPP 35 - Punt
http://goallineblitz.com/game/replay.pl?game_id=1703669&pbp_id=8895736

Third Occurrence: Q4 2:26 4th & 18.5 on OPP 35 - FG
http://goallineblitz.com/game/replay.pl?game_id=1703669&pbp_id=8896223

I tested all thee situations in the AI tester, and all came back with FG as the only possible matching outcome. I also checked, and there isn't anything in the Quarter Specific sections that would override the generic FG input.


One thing to keep in mind... when listing the yard line on the play-by-play, the game rounds off to the nearest half-yard. However, it's possible that on the first two plays the ball was really at the 35.1 yard line (and thus beyond 35 yards), while on the third play the ball was really at the 34.9 yard line (and thus inside 35 yards). The play-by-play display would round both 35.1 and 34.9 to just "35".

I don't know for sure that this is what happened here, but it is a possible explanation.
 
spindoctor02
offline
Link
 
I did consider the rounding issue, but on one of the plays the ball was originally at the 35.5, and we got a 0.5 yard gain on the next play before the FG, so I doubt we got screwed by the rounding twice...lol.

Also, I have been watching this more closely all season, as being the DC on the team, it always erks me when the offense can't score, so I know exactly where the yardage line is for FGs. Everytime this season prior to this game, when the game listed the LOS as the 35 (or less), we kicked the FG. This was the first time we punted when it listed us at the 35.

I know this isn't the place for this, but if the text output rounds, so should the value in the game code. If the best we can do is select FG range by 5 yard increments, the least Bort could do is make it so we can actually set the AI based on what the game is telling us.
 
Pwned
offline
Link
 
Sent a PM about this.

I'm confused because looking through the AI's two different inputs should be showing, based on these scenarios.

Both FG and Punt should show in the test because all 3 situations fit both inputs I found.

Yet the FG is the only one coming up in the TEST..
 
Novus
offline
Link
 
Originally posted by spindoctor02
I did consider the rounding issue, but on one of the plays the ball was originally at the 35.5, and we got a 0.5 yard gain on the next play before the FG, so I doubt we got screwed by the rounding twice...lol.


It's still possible though, because the play-by-play also rounds off the gains to the nearest half-yard as well. So if your dot gained 0.4, that would move the ball from the 35.5 to the 35.1. But the play-by-play would round the 0.4 to 0.5, while rounding the 35.1 to 35.

Without being able to see the actual in-sim numbers myself though, there's no way to know for sure. But it is a possibility, and thus needs to be considered.

Good point about the rounding though... might make a good suggestion. The AI should look at the rounded number, not at the actual number, since no real-life coach is going to say, "Well, if we were just an inch further forward I'd say go for a FG, but let's just send out the punt team instead, 'cos that inch makes all the difference."
 
spindoctor02
offline
Link
 
Originally posted by Novus
Originally posted by spindoctor02

I did consider the rounding issue, but on one of the plays the ball was originally at the 35.5, and we got a 0.5 yard gain on the next play before the FG, so I doubt we got screwed by the rounding twice...lol.


It's still possible though, because the play-by-play also rounds off the gains to the nearest half-yard as well. So if your dot gained 0.4, that would move the ball from the 35.5 to the 35.1. But the play-by-play would round the 0.4 to 0.5, while rounding the 35.1 to 35.

Without being able to see the actual in-sim numbers myself though, there's no way to know for sure. But it is a possibility, and thus needs to be considered.

Good point about the rounding though... might make a good suggestion. The AI should look at the rounded number, not at the actual number, since no real-life coach is going to say, "Well, if we were just an inch further forward I'd say go for a FG, but let's just send out the punt team instead, 'cos that inch makes all the difference."


If the issue is solely a rounding issue, then here is a suggestion that should fix the problem.

http://goallineblitz.com/game/forum_thread.pl?thread_id=4636914

If this is actually a bug, then it should be an easy fix.
 
Novus
offline
Link
 
Originally posted by spindoctor02
If the issue is solely a rounding issue, then here is a suggestion that should fix the problem.

http://goallineblitz.com/game/forum_thread.pl?thread_id=4636914

If this is actually a bug, then it should be an easy fix.


+1'd.

I'll shut up now and get out of the way. Just wanted to point out the rounding possibility.
 
TruthHammer
Lead Bugs Mod
offline
Link
 
I'm sure this is just a rounding issue, but since several other bugs mods have started investigating already, I'll defer to them.
 
spindoctor02
offline
Link
 
Originally posted by TruthHammer
I'm sure this is just a rounding issue, but since several other bugs mods have started investigating already, I'll defer to them.


Pwned_IRL checked out my AI. That's all the interaction I've had with the different bugs mods so far.
 
Pwned
offline
Link
 
Originally posted by spindoctor02
Pwned_IRL checked out my AI. That's all the interaction I've had with the different bugs mods so far.


Everything I saw checked out.

Tested all the situations from the link and verified the AI.

My only thought, was there any way a different AI was used for that game?
 
rocklee711
offline
Link
 
I know I'm real late to the party here but just curious on how long you've been using that input in the AI and not having the max FG distance marked and special circumstances taken out of the FG kicking.

Because I initially agree with Kuaggie and from talking to my longtime OC that not having that max FG distance marked could leave it open to not kicking it in some instances.
 
Page:
 


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