if you want me to take a look add me a GM with offense only and I'll look at it and tell you what's up.
XUMuskie85
offline
offline
Originally posted by Robbnva
Originally posted by XUMuskie85
And in the offensive AI tester is comes up as FG. And there are a million unmatching inputs, but the closest one of course is my 4th and short input, which is just missing the distance to 1st down as it should be.
what does it show when you do test and show unmatched?
It says like 15 different outputs, the closest one though is the 4th and short input, which only has 1 unmatching.
Originally posted by XUMuskie85
And in the offensive AI tester is comes up as FG. And there are a million unmatching inputs, but the closest one of course is my 4th and short input, which is just missing the distance to 1st down as it should be.
what does it show when you do test and show unmatched?
It says like 15 different outputs, the closest one though is the 4th and short input, which only has 1 unmatching.
im4ut999
offline
offline
I think this is so funny all you experts coming here asking what the AI tester says...
The AI tester doesn't cover this because it doesn't take "goal" to go as an input, as has been mentioned in this thread.
There is clear evidence that the AI is not recognizing the difference between "short yardage" and "goal to go" situations...
The only folks that are seeing this issue are guys who want to do something specific on short yardage plays AND have those plays called in goal to go situations.
I have seen at least 2 occurrences of this happening and have reported it as a bug in the past, but nothing has been done. Both cases I recognized because both were "goal to go" from OUTSIDE the 10 yard line (meaning it was most definitely NOT short yardage) and the play called was either an inside run on 4th down (TD scored but obviously not correct call) or GL formation on 2nd down (which was only in the AI for short yardage).
Here are the plays - these are two completely different situations, both being executed due to "goal to go" being accepted as "0-2 yards to go":
4th and goal from the 10.5 (4th and short go for it play was called):
http://goallineblitz.com/game/replay.pl?game_id=92933&pbp_id=5591616
2nd and goal from the 11 (2nd and short use goalline offense was called):
http://goallineblitz.com/game/replay.pl?game_id=92933&pbp_id=5591616
The AI tester doesn't cover this because it doesn't take "goal" to go as an input, as has been mentioned in this thread.
There is clear evidence that the AI is not recognizing the difference between "short yardage" and "goal to go" situations...
The only folks that are seeing this issue are guys who want to do something specific on short yardage plays AND have those plays called in goal to go situations.
I have seen at least 2 occurrences of this happening and have reported it as a bug in the past, but nothing has been done. Both cases I recognized because both were "goal to go" from OUTSIDE the 10 yard line (meaning it was most definitely NOT short yardage) and the play called was either an inside run on 4th down (TD scored but obviously not correct call) or GL formation on 2nd down (which was only in the AI for short yardage).
Here are the plays - these are two completely different situations, both being executed due to "goal to go" being accepted as "0-2 yards to go":
4th and goal from the 10.5 (4th and short go for it play was called):
http://goallineblitz.com/game/replay.pl?game_id=92933&pbp_id=5591616
2nd and goal from the 11 (2nd and short use goalline offense was called):
http://goallineblitz.com/game/replay.pl?game_id=92933&pbp_id=5591616
dpell
offline
offline
I had this happen once. 3 people ahve been through my AI and the tester outputs FG, but my team still went for it on 4th and 6.5(G) to go. I entered the same exact settings into the AI tester and got "100% kick FG" back out.
Something is wonky with the AI at times in short yardage. I'm not using "G" in my AI either. I'm using real numbers. It should have kicked a FG. It's kicked a FG at almost the same exact position in other games. I know if this costs me a game at some point I'm going to be a little pissed off. Seems like this is being ignored as an issue. Everyone just wants to say it's my AI settings. I enter the exact situation from the game and get a FG as an output. Down to the second the play was run. This isn't a user error. It's a bug of some sort.
Something is wonky with the AI at times in short yardage. I'm not using "G" in my AI either. I'm using real numbers. It should have kicked a FG. It's kicked a FG at almost the same exact position in other games. I know if this costs me a game at some point I'm going to be a little pissed off. Seems like this is being ignored as an issue. Everyone just wants to say it's my AI settings. I enter the exact situation from the game and get a FG as an output. Down to the second the play was run. This isn't a user error. It's a bug of some sort.
Robbnva
offline
offline
Originally posted by XUMuskie85
Originally posted by Robbnva
Originally posted by XUMuskie85
And in the offensive AI tester is comes up as FG. And there are a million unmatching inputs, but the closest one of course is my 4th and short input, which is just missing the distance to 1st down as it should be.
what does it show when you do test and show unmatched?
It says like 15 different outputs, the closest one though is the 4th and short input, which only has 1 unmatching.
then you need to fix that 1 unmatch and it will work.
Originally posted by Robbnva
Originally posted by XUMuskie85
And in the offensive AI tester is comes up as FG. And there are a million unmatching inputs, but the closest one of course is my 4th and short input, which is just missing the distance to 1st down as it should be.
what does it show when you do test and show unmatched?
It says like 15 different outputs, the closest one though is the 4th and short input, which only has 1 unmatching.
then you need to fix that 1 unmatch and it will work.
Robbnva
offline
offline
Originally posted by im4ut999
I think this is so funny all you experts coming here asking what the AI tester says...
The AI tester doesn't cover this because it doesn't take "goal" to go as an input, as has been mentioned in this thread.
There is clear evidence that the AI is not recognizing the difference between "short yardage" and "goal to go" situations...
The only folks that are seeing this issue are guys who want to do something specific on short yardage plays AND have those plays called in goal to go situations.
I have seen at least 2 occurrences of this happening and have reported it as a bug in the past, but nothing has been done. Both cases I recognized because both were "goal to go" from OUTSIDE the 10 yard line (meaning it was most definitely NOT short yardage) and the play called was either an inside run on 4th down (TD scored but obviously not correct call) or GL formation on 2nd down (which was only in the AI for short yardage).
Here are the plays - these are two completely different situations, both being executed due to "goal to go" being accepted as "0-2 yards to go":
4th and goal from the 10.5 (4th and short go for it play was called):
http://goallineblitz.com/game/replay.pl?game_id=92933&pbp_id=5591616
2nd and goal from the 11 (2nd and short use goalline offense was called):
http://goallineblitz.com/game/replay.pl?game_id=92933&pbp_id=5591616
dude I have set up multiiple different AI and I can get it to work and ai tester matches it. I have also gone for it on goal situations when I told it to. if you have an input and you do the tester and there is NO MATCH, then you fucked up the AI. I am trying to be nice and I will help anyone who wants it. if I can't do it I will come back in here and support your claim that it is a bug but until then I say no bug, user error.
I think this is so funny all you experts coming here asking what the AI tester says...
The AI tester doesn't cover this because it doesn't take "goal" to go as an input, as has been mentioned in this thread.
There is clear evidence that the AI is not recognizing the difference between "short yardage" and "goal to go" situations...
The only folks that are seeing this issue are guys who want to do something specific on short yardage plays AND have those plays called in goal to go situations.
I have seen at least 2 occurrences of this happening and have reported it as a bug in the past, but nothing has been done. Both cases I recognized because both were "goal to go" from OUTSIDE the 10 yard line (meaning it was most definitely NOT short yardage) and the play called was either an inside run on 4th down (TD scored but obviously not correct call) or GL formation on 2nd down (which was only in the AI for short yardage).
Here are the plays - these are two completely different situations, both being executed due to "goal to go" being accepted as "0-2 yards to go":
4th and goal from the 10.5 (4th and short go for it play was called):
http://goallineblitz.com/game/replay.pl?game_id=92933&pbp_id=5591616
2nd and goal from the 11 (2nd and short use goalline offense was called):
http://goallineblitz.com/game/replay.pl?game_id=92933&pbp_id=5591616
dude I have set up multiiple different AI and I can get it to work and ai tester matches it. I have also gone for it on goal situations when I told it to. if you have an input and you do the tester and there is NO MATCH, then you fucked up the AI. I am trying to be nice and I will help anyone who wants it. if I can't do it I will come back in here and support your claim that it is a bug but until then I say no bug, user error.
Robbnva
offline
offline
FINAL OFFER FOR GM FOR 1 DAY TO FIX YOUR "AND GOAL" AI. ENDS WHEN YOU SEE MY NAME OFFLINE.
XUMuskie85
offline
offline
Originally posted by Robbnva
Originally posted by XUMuskie85
Originally posted by Robbnva
Originally posted by XUMuskie85
And in the offensive AI tester is comes up as FG. And there are a million unmatching inputs, but the closest one of course is my 4th and short input, which is just missing the distance to 1st down as it should be.
what does it show when you do test and show unmatched?
It says like 15 different outputs, the closest one though is the 4th and short input, which only has 1 unmatching.
then you need to fix that 1 unmatch and it will work.
As I said in the 1st post, there is ONE match, which is kick a FG, and then like 15 unmatched. IRregardless, it runs up the middle.
It is definitely not a user issue when it comes up in the tester as kicking a FG and then doesn't do it in the game situation that was outlined in the tester.
Originally posted by XUMuskie85
Originally posted by Robbnva
Originally posted by XUMuskie85
And in the offensive AI tester is comes up as FG. And there are a million unmatching inputs, but the closest one of course is my 4th and short input, which is just missing the distance to 1st down as it should be.
what does it show when you do test and show unmatched?
It says like 15 different outputs, the closest one though is the 4th and short input, which only has 1 unmatching.
then you need to fix that 1 unmatch and it will work.
As I said in the 1st post, there is ONE match, which is kick a FG, and then like 15 unmatched. IRregardless, it runs up the middle.
It is definitely not a user issue when it comes up in the tester as kicking a FG and then doesn't do it in the game situation that was outlined in the tester.
Last edited Aug 22, 2008 21:39:50
Robbnva
offline
offline
guys, make sure your AI has a number in the seconds to go or it won't match and default to your basic AI. If you are losing late in the 3rd quarter or in the 4th quarter and you are in the red zone your team will go for it on 4th down. (it did it all the time last season, which is the reason for these advance tactics)
if you have go for it on 4th down and the team kicks a FG and your input does not have a number in seconds to go, it won't follow that input.
15 minutes is 900 seconds so make sure your inputs have at least 900 seconds.
if you have go for it on 4th down and the team kicks a FG and your input does not have a number in seconds to go, it won't follow that input.
15 minutes is 900 seconds so make sure your inputs have at least 900 seconds.
XUMuskie85
offline
offline
Originally posted by Robbnva
guys, make sure your AI has a number in the seconds to go or it won't match and default to your basic AI. If you are losing late in the 3rd quarter or in the 4th quarter and you are in the red zone your team will go for it on 4th down. (it did it all the time last season, which is the reason for these advance tactics)
if you have go for it on 4th down and the team kicks a FG and your input does not have a number in seconds to go, it won't follow that input.
15 minutes is 900 seconds so make sure your inputs have at least 900 seconds.
I'm pretty sure that doesn't matter because my original "going for it on 4th down" input doesn't have seconds entered, and we have gone for it like 2-4 times a game. In fact, few of my general field position inputs have seconds and I've seen many of them work before.
guys, make sure your AI has a number in the seconds to go or it won't match and default to your basic AI. If you are losing late in the 3rd quarter or in the 4th quarter and you are in the red zone your team will go for it on 4th down. (it did it all the time last season, which is the reason for these advance tactics)
if you have go for it on 4th down and the team kicks a FG and your input does not have a number in seconds to go, it won't follow that input.
15 minutes is 900 seconds so make sure your inputs have at least 900 seconds.
I'm pretty sure that doesn't matter because my original "going for it on 4th down" input doesn't have seconds entered, and we have gone for it like 2-4 times a game. In fact, few of my general field position inputs have seconds and I've seen many of them work before.
im4ut999
offline
offline
Originally posted by Robbnva
guys, make sure your AI has a number in the seconds to go or it won't match and default to your basic AI. If you are losing late in the 3rd quarter or in the 4th quarter and you are in the red zone your team will go for it on 4th down. (it did it all the time last season, which is the reason for these advance tactics)
if you have go for it on 4th down and the team kicks a FG and your input does not have a number in seconds to go, it won't follow that input.
15 minutes is 900 seconds so make sure your inputs have at least 900 seconds.
My AI does match without having time left entered...the AI tester shows this:
Matching Input
Input Named: 2nd and short GL
Possible Outputs
100% GL try (goal_line)
and this worked in this play today:
http://goallineblitz.com/game/replay.pl?game_id=92933&pbp_id=5588832
The same GL offense was called later in a 2nd and G situation from the 11 yard line (yes I was down by 14, but we're not talking about going for it on 4th down here). Yes, it COULD be defaulting to the basic AI, but it doesn't look like it to me...
This may or may not be a bug, but I think only Bort is going to be able to answer that...it needs to be looked at by Bort. It should be quite simple to check...
Put in a 2nd and goal from the 11 without this AI play and see how often the basic AI chooses to to go into GL formation. Add this AI play and compare...
The issue is the goal to go matches short yardage...
guys, make sure your AI has a number in the seconds to go or it won't match and default to your basic AI. If you are losing late in the 3rd quarter or in the 4th quarter and you are in the red zone your team will go for it on 4th down. (it did it all the time last season, which is the reason for these advance tactics)
if you have go for it on 4th down and the team kicks a FG and your input does not have a number in seconds to go, it won't follow that input.
15 minutes is 900 seconds so make sure your inputs have at least 900 seconds.
My AI does match without having time left entered...the AI tester shows this:
Matching Input
Input Named: 2nd and short GL
Possible Outputs
100% GL try (goal_line)
and this worked in this play today:
http://goallineblitz.com/game/replay.pl?game_id=92933&pbp_id=5588832
The same GL offense was called later in a 2nd and G situation from the 11 yard line (yes I was down by 14, but we're not talking about going for it on 4th down here). Yes, it COULD be defaulting to the basic AI, but it doesn't look like it to me...
This may or may not be a bug, but I think only Bort is going to be able to answer that...it needs to be looked at by Bort. It should be quite simple to check...
Put in a 2nd and goal from the 11 without this AI play and see how often the basic AI chooses to to go into GL formation. Add this AI play and compare...
The issue is the goal to go matches short yardage...
TreMetal
offline
offline
Originally posted by Robbnva
ok I put in the following
4th and goal is the input name
opponent 5 and opponent goal
between 4 and 4 downs
yards to go 0 to 5
score difference and special circumstance is blank
output I did HB rush up the middle.
AI tester I put in 4th quarter, 60 second remaining on opponent's 4 yard line 4th down and 4 to go trailing by 0
and the response is
Matching Input
Input Named: 4th and goal
Possible Outputs
100% New Output (inside_run)
Change that to say 1-5.. of course in the AI tester you cannot input "4th and goal", but IN THE GAME 4th and goal is equivalent to 4th and 0.
ok I put in the following
4th and goal is the input name
opponent 5 and opponent goal
between 4 and 4 downs
yards to go 0 to 5
score difference and special circumstance is blank
output I did HB rush up the middle.
AI tester I put in 4th quarter, 60 second remaining on opponent's 4 yard line 4th down and 4 to go trailing by 0
and the response is
Matching Input
Input Named: 4th and goal
Possible Outputs
100% New Output (inside_run)
Change that to say 1-5.. of course in the AI tester you cannot input "4th and goal", but IN THE GAME 4th and goal is equivalent to 4th and 0.
TreMetal
offline
offline
Also, this would be pretty easy to test in a scrimmage game by adding a "1st and 0" to kick a FG (for instance). Then see if you kick a field goal anytime you get a first down within the opponents 10 yard line.
XUMuskie85
offline
offline
I just got a PM back from support saying they have noticed it too and are working on determining the problem and fixing it. Yay
RandomBeast
offline
offline
thanks for the update XU.
Robb, your test totally misses the point. The bug is that "goal to go" is treated as 0 yards by the AI. If your AI covers everything withing 0-5 yards it would match either way.
Say you set up a 4th and short input 0-3 yards to run inside. And set that as top priority (as if you would go for it on all short yardage downs) Then set up a 4th down FG input below that.
The AI on 4th and G from the 6 will run inside instead of kick.
Robb, your test totally misses the point. The bug is that "goal to go" is treated as 0 yards by the AI. If your AI covers everything withing 0-5 yards it would match either way.
Say you set up a 4th and short input 0-3 yards to run inside. And set that as top priority (as if you would go for it on all short yardage downs) Then set up a 4th down FG input below that.
The AI on 4th and G from the 6 will run inside instead of kick.
Last edited Aug 23, 2008 08:59:18
You are not logged in. Please log in if you want to post a reply.






























