User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > 55.5 yd Field Goal, with 45 as max
Page:
 
Forbin
offline
Link
 
I was sure that it was something in the AI, because I just updated it and added a few situations, but I have been unable to find any inconsistencies, and the tester correctly outputs "No Matching Input", which would mean a punt, as it's beyond the max FG range.


The play:
http://www.freewebs.com/forbin007/game.JPG

The AI setting:
http://www.freewebs.com/forbin007/ai.JPG

The AI tester:
http://www.freewebs.com/forbin007/tester.JPG

I do have specific settings to either go for it or kick a FG, depending on field position, but 7.5 yards is well out of the range to go for it in that position, and the longest FG we have set in the AI is 52.
 
tremele
offline
Link
 
Add 17 yards per field goal. Right now you have it set to kick 62 yards.
 
justafish2002
offline
Link
 
Originally posted by tremele
Add 17 yards per field goal. Right now you have it set to kick 62 yards.


Wrong read the description: You add 17 yards BEFORE you input the distance.

The "Bug": Not a bug. The Basic AI was activated (due to no input) and to said kick a FG.
 
SCACE
offline
Link
 
Originally posted by tremele
Add 17 yards per field goal. Right now you have it set to kick 62 yards.


No, putting 45 yards in the box means it shouldn't kick 45 yard field goals unless you have an input overriding. There could be a FG input where you don't have the setting "within FG range".

Or, with time winding down, you may extend the range. You may have also specified yardage in the FG input that overrides what you put in the box.

Would need to see more AI to determine the cause.
 
Razup
offline
Link
 
No matching inputs doesn't mean punt. If you want it to punt when out of FG range, set up an input for 4th down, out of fg range, and an output that says punt.
 
hemprobot
offline
Link
 
What Razup said, you need an input to catch punts outside FG distance. The sim doesn't do that, or anything else, automatically.
 
SCACE
offline
Link
 
Originally posted by hemprobot
What Razup said, you need an input to catch punts outside FG distance. The sim doesn't do that, or anything else, automatically when you choose to use the advanced AI.


 
hemprobot
offline
Link
 
Just so.
 
Forbin
offline
Link
 
Originally posted by Razup
No matching inputs doesn't mean punt. If you want it to punt when out of FG range, set up an input for 4th down, out of fg range, and an output that says punt.


I suppose the issue is that I had not previously relied on the AI to make a decision for me. I wasn't aware that the "FG Range" setting was so totally useless. I've already got 10 or 15 FG/Punt inputs for specific situations. Another few won't hurt.

I don't get why that setting is so useless. I'd think the primary use for it would be to tell the AI when to kick and when to punt. It makes very little sense to even have such a setting if it's going to completely ignore the "Maximum Field Goal Range" and kick it according to the kicker's attributes.

I guess the only purpose of that setting is to go with the mostly useless "Within FG Range" option and its companions.

So, not a bug, just another poorly implemented feature.

Thanks, guys.
 
SCACE
offline
Link
 
Originally posted by Forbin
Originally posted by Razup

No matching inputs doesn't mean punt. If you want it to punt when out of FG range, set up an input for 4th down, out of fg range, and an output that says punt.


I suppose the issue is that I had not previously relied on the AI to make a decision for me. I wasn't aware that the "FG Range" setting was so totally useless. I've already got 10 or 15 FG/Punt inputs for specific situations. Another few won't hurt.

I don't get why that setting is so useless. I'd think the primary use for it would be to tell the AI when to kick and when to punt. It makes very little sense to even have such a setting if it's going to completely ignore the "Maximum Field Goal Range" and kick it according to the kicker's attributes.

I guess the only purpose of that setting is to go with the mostly useless "Within FG Range" option and its companions.

So, not a bug, just another poorly implemented feature.

Thanks, guys.


Obviously we don't know your settings, but I've had zero issues with kicking a FG at the right time...the only broken setting I've found (which to my knowledge isn't fixed yet) is the Near FG Range setting which keeps triggering even once you're in FG range.
 
Forbin
offline
Link
 
Originally posted by SCACE
Obviously we don't know your settings, but I've had zero issues with kicking a FG at the right time...the only broken setting I've found (which to my knowledge isn't fixed yet) is the Near FG Range setting which keeps triggering even once you're in FG range.


If you're saying that the "Max FG Range" setting works how I assumed it should, then this is indeed a bug. Perhaps it's related to the randomly occurring bug where the AI decides to run a play that's not even in your AI - It does happen, and I have confirmed it on multiple occasions myself.

This is the first time I've seen a punt or FG happen in the wrong instance. I've not touched any settings related to kicking or punting since very early in the season, when I bumped the range up 5 yards for Georgetown. All last season, the AI worked perfectly for Georgetown, and for 14 games this season. It was not something I changed.
 
BoneZ69
offline
Link
 
no i think what he is saying is that his input for the FG was set for his OPP side of the 50 but in stead of being on that side he was in his OWN side of the 50 and the AI went to that play when it shouldn't of
am i right Forbin

just look at this replay http://goallineblitz.com/game/replay.pl?game_id=153767&pbp_id=9549842

i have the AI set for FG on OPP 38 and it kicked it on OWN 38 and the AI tester is saying that is the play to go to don't know why it is doing that but it is odd
was thinking that i did something wrong but now i don't feel so bad now that i know that it didn't only happen to me

i just looked at the SS and that isn't even what happened to me like i said i have AI set to kick FG when the ball is between the OPP40 and OPP 35 and it kicked it on the OWN 38 just look at the replay and you will see who in there right mind would set to kick that far out
Last edited Oct 22, 2008 00:33:16
 
Forbin
offline
Link
 
Originally posted by BoneZ69
no i think what he is saying is that his input for the FG was set for his OPP side of the 50 but in stead of being on that side he was in his OWN side of the 50 and the AI went to that play when it shouldn't of
am i right Forbin

just look at this replay http://goallineblitz.com/game/replay.pl?game_id=153767&pbp_id=9549842

i have the AI set for FG on OPP 38 and it kicked it on OWN 38 and the AI tester is saying that is the play to go to don't know why it is doing that but it is odd
was thinking that i did something wrong but now i don't feel so bad now that i know that it didn't only happen to me

i just looked at the SS and that isn't even what happened to me like i said i have AI set to kick FG when the ball is between the OPP40 and OPP 35 and it kicked it on the OWN 38 just look at the replay and you will see who in there right mind would set to kick that far out


Nowhere near the same issue..

Your case sounds like a classic example of an AI error. The basic AI doesn't kick 79 yard field goals.
 
Specialed
offline
Link
 
Originally posted by BoneZ69
i just looked at the SS and that isn't even what happened to me like i said i have AI set to kick FG when the ball is between the OPP40 and OPP 35 and it kicked it on the OWN 38 just look at the replay and you will see who in there right mind would set to kick that far out


Got Lane Kiffin as a OC?
 
BoneZ69
offline
Link
 
Originally posted by Specialed

Got Lane Kiffin as a OC?


no i am the OC i think this is a bug in the system not an error of mine it just don't make sense why it would do that
 
Page:
 


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