User Pass
Home Sign Up Contact Log In
Page:
 
Sik Wit It
offline
Link
 
I really don't know what to say about this. It's really weird. We have 2 OCs, and for some reason we always go for it on 4th down near midfield when one guy's offense AI is ran. It hasn't happened with the other guy's offense in.

The thing is we tested it every time, and the tester always says punt.

http://goallineblitz.com/game/replay.pl?game_id=878634&pbp_id=10284984

Here's the tester output:
http://img35.imageshack.us/img35/4623/picture1sxp.png

What the hell is happening here? What really gets me is this never happens in one guy's offense, and has happened about 3 or 4 times already this season with the other guy's offense. The tester always says punt. Is it possible one of our OC's AI is just bugged or something?
 
Sixx
offline
Link
 
What's the quarter specific inputs for the ai that's not working?
 
Sik Wit It
offline
Link
 
Do you mean what was under "Unmatched Inputs"?

It was mostly a bunch of red zone stuff.
 
Jaxon Voom
offline
Link
 
Are you sure there's no 4th & Short input hidden away that you've forgotten about? The fact it's always near midfield would indicate there is.
 
Sixx
offline
Link
 
Originally posted by Sik Wit It
Do you mean what was under "Unmatched Inputs"?

It was mostly a bunch of red zone stuff.


Do you have any inputs set in 1st, 2nd, 3rd or 4th quarter? If so one of these could be overriding the punt call.
 
Sik Wit It
offline
Link
 
Originally posted by Jaxon Voom
Are you sure there's no 4th & Short input hidden away that you've forgotten about? The fact it's always near midfield would indicate there is.


There are 4th & short inputs, but the example I posted was 4th and long. Plus if it was activating, it would show up as the output in the AI tester, wouldn't it?
 
Sik Wit It
offline
Link
 
Originally posted by Sixx
Originally posted by Sik Wit It

Do you mean what was under "Unmatched Inputs"?

It was mostly a bunch of red zone stuff.


Do you have any inputs set in 1st, 2nd, 3rd or 4th quarter? If so one of these could be overriding the punt call.


We have some quarter-specific inputs, but NONE for the 1st quarter.
 
Sixx
offline
Link
 
Originally posted by Sik Wit It
Originally posted by Jaxon Voom

Are you sure there's no 4th & Short input hidden away that you've forgotten about? The fact it's always near midfield would indicate there is.


There are 4th & short inputs, but the example I posted was 4th and long. Plus if it was activating, it would show up as the output in the AI tester, wouldn't it?


Seeing that one AI is calling the punt correctly but the other one isn't, I'd say you have an input set wrong.

As for the tester, I wouldn't trust it 100%, it's already been proven to be wrong.
 
bhall43
offline
Link
 
Originally posted by Sixx
Seeing that one AI is calling the punt correctly but the other one isn't, I'd say you have an input set wrong.

As for the tester, I wouldn't trust it 100%, it's already been proven to be wrong.


Its always in the same place. between our own 45 and the 50 yard line. anything outside of 4th and 3 is completely random. Worked into our favor 1 out of 3 times so far. Twice has been running plays that make absolutely no sense. Been tested over and over again as punt. Looked through my entire AI several times and nowhere is there an incorrect input. In fact its the same AI used last season as a whole and this didn't happen to us once last season.

Its just a straight up bug in the AI.
 
Novus
offline
Link
 
Originally posted by Sik Wit It
There are 4th & short inputs, but the example I posted was 4th and long. Plus if it was activating, it would show up as the output in the AI tester, wouldn't it?


Y'know, it's possible that you have an output that is NAMED "Punt," but if you open up that output, it might not actually BE a Punt. Common mistake. That would explain why the AI Tester comes up "Punt." That's what the output is named, but that's not the actually play that's called for.

Open up EVERY Output named "Punt" in your AI and make sure they're all actually punts and not something else instead.
 
Jaxon Voom
offline
Link
 
Originally posted by bhall43
Originally posted by Sixx

Seeing that one AI is calling the punt correctly but the other one isn't, I'd say you have an input set wrong.

As for the tester, I wouldn't trust it 100%, it's already been proven to be wrong.


Its always in the same place. between our own 45 and the 50 yard line. anything outside of 4th and 3 is completely random. Worked into our favor 1 out of 3 times so far. Twice has been running plays that make absolutely no sense. Been tested over and over again as punt. Looked through my entire AI several times and nowhere is there an incorrect input. In fact its the same AI used last season as a whole and this didn't happen to us once last season.

Its just a straight up bug in the AI.


Is your Punt input above the other inputs? It reads from the top so if you have inputs above the punt that match the game situation, it may read them first and perform that one instead. I'd take a look if you wanted.
 
bhall43
offline
Link
 
Originally posted by Novus
Y'know, it's possible that you have an output that is NAMED "Punt," but if you open up that output, it might not actually BE a Punt. Common mistake. That would explain why the AI Tester comes up "Punt." That's what the output is named, but that's not the actually play that's called for.

Open up EVERY Output named "Punt" in your AI and make sure they're all actually punts and not something else instead.


good thinking...however...its only happening from the 45 to the 50 on our own side. it punts every other time it should. and there is only one punt setting.
 
bhall43
offline
Link
 
Originally posted by Jaxon Voom
Is your Punt input above the other inputs? It reads from the top so if you have inputs above the punt that match the game situation, it may read them first and perform that one instead. I'd take a look if you wanted.


got a couple guys looking it over right now...probably just going to try flipping the entire AI upside down from the way it is to see if that fixes it unless hazy can find something internally wrong...

the point being here is that the AI Tester is fucked.
 
Sik Wit It
offline
Link
 
Originally posted by Novus
Originally posted by Sik Wit It

There are 4th & short inputs, but the example I posted was 4th and long. Plus if it was activating, it would show up as the output in the AI tester, wouldn't it?


Y'know, it's possible that you have an output that is NAMED "Punt," but if you open up that output, it might not actually BE a Punt. Common mistake. That would explain why the AI Tester comes up "Punt." That's what the output is named, but that's not the actually play that's called for.

Open up EVERY Output named "Punt" in your AI and make sure they're all actually punts and not something else instead.


But if that was the case, then we'd never punt. And we punt sometimes (although not that often )
 
cosmoxl
offline
Link
 
if the AI tester isn't always right, then it needs to be fixed ASAP.
 
Page:
 


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