User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > Defense AI occasionally not followed
Page:
 
Link
 
Originally posted by tautology

The "and goal" bug is ubiquitous, as SteelersInsider has said. If you have situational calls based on down and distance near the goal line, you encounter this problem eventually.


The problem was that "4th & G" was treated as "4th & 0" once in a while, however, it is not always being treated as 4th & 0. This is why Bort had hard time reproducing the bug since it doesn't always fail. Maybe Bort has already fixed the bug and that's no one talking about it now. But I remember when it first happened, there were about 4 or 5 posts about it. It's not a "every team sees it" bug since it requires certain setting in AI and it doesn't always happen.

Think about it, both problems are pretty similar that it doesn't always fail under same condition. The main difference is that the "and goal' bug is easier to notice while the current issue is harder.
 
Link
 
Originally posted by buffalobills_tw
Originally posted by tautology


The "and goal" bug is ubiquitous, as SteelersInsider has said. If you have situational calls based on down and distance near the goal line, you encounter this problem eventually.


The problem was that "4th & G" was treated as "4th & 0" once in a while, however, it is not always being treated as 4th & 0. This is why Bort had hard time reproducing the bug since it doesn't always fail. Maybe Bort has already fixed the bug and that's no one talking about it now. But I remember when it first happened, there were about 4 or 5 posts about it. It's not a "every team sees it" bug since it requires certain setting in AI and it doesn't always happen.

Think about it, both problems are pretty similar that it doesn't always fail under same condition. The main difference is that the "and goal' bug is easier to notice while the current issue is harder.



I think the 4th and goal one didn't always happen because sometimes it really was 4th and 1 or 4th and 2 like teams wanted to go for it. Then there weren't many teams that went for it anyway. So you are narrowing down the teams alot.

Then most took that out of their play book altogether. So the situations where it could possibly still happen are 4th and goal from the 4.5 to the 2.5 yard line (if the condition was to go if 4th and less than 2). So now we are talking about very few situations where the "bug" could arise. That is why you don't hear about it anymore. People have their AI set up better.

And for me, it wasn't "occasional", it happened wrong every time and I easily figured out what happened the 2nd time it screwed up and went for it on 4th and goal from the 8.

Not even close to the same problem.
 
Link
 
P.S. I'm probably going to cost myself 2 good players for next year by arguing this point, so I'm not very bright.

 
tautology
offline
Link
 
Originally posted by buffalobills_tw
Originally posted by tautology


The "and goal" bug is ubiquitous, as SteelersInsider has said. If you have situational calls based on down and distance near the goal line, you encounter this problem eventually.


The problem was that "4th & G" was treated as "4th & 0" once in a while, however, it is not always being treated as 4th & 0. This is why Bort had hard time reproducing the bug since it doesn't always fail. Maybe Bort has already fixed the bug and that's no one talking about it now. But I remember when it first happened, there were about 4 or 5 posts about it. It's not a "every team sees it" bug since it requires certain setting in AI and it doesn't always happen.

Think about it, both problems are pretty similar that it doesn't always fail under same condition. The main difference is that the "and goal' bug is easier to notice while the current issue is harder.


Hmmm...I never heard that it was hard to track down, it happened every single time in my experience...if you had settings that would expose it.
The AI tester and the Sim had different outputs, and that, perhaps, made the problem more confusing than it needed to be.
I never followed up to see if that was resolved...do you know if it was?
I simply removed any chance of going for it inside the 10, which largely prevents the problem, though it is a little limiting strategically during earlier parts of the game where it might matter. Late in the game, you can work around it with relative safety.
 
Link
 
Originally posted by SteelersInsider

I think the 4th and goal one didn't always happen because sometimes it really was 4th and 1 or 4th and 2 like teams wanted to go for it. Then there weren't many teams that went for it anyway. So you are narrowing down the teams alot.

Then most took that out of their play book altogether. So the situations where it could possibly still happen are 4th and goal from the 4.5 to the 2.5 yard line (if the condition was to go if 4th and less than 2). So now we are talking about very few situations where the "bug" could arise. That is why you don't hear about it anymore. People have their AI set up better.

And for me, it wasn't "occasional", it happened wrong every time and I easily figured out what happened the 2nd time it screwed up and went for it on 4th and goal from the 8.

Not even close to the same problem.


Maybe it happened every time to you, but certainly not for others and Bort. If you read the link, Bort had trouble reproducing the bug at the time. It is not as reproducible as you claim.

Again, back to the topic, do you see any input wrong that OP provided? If not, this is a legit bug when defense AI tester shows something different to in-game play under same situation.
 
Link
 
Originally posted by tautology

Hmmm...I never heard that it was hard to track down, it happened every single time in my experience...if you had settings that would expose it.
The AI tester and the Sim had different outputs, and that, perhaps, made the problem more confusing than it needed to be.
I never followed up to see if that was resolved...do you know if it was?
I simply removed any chance of going for it inside the 10, which largely prevents the problem, though it is a little limiting strategically during earlier parts of the game where it might matter. Late in the game, you can work around it with relative safety.


I think Bort probably fixed the problem and that's why nobody sees it anymore. With so many new teams and inexperience owner/GM, I seriously double everyone knows this bug and works around it in their AI.

That bug did not fail every time, in the link I post, Bort had following comment. He tried several times and yardage reported correctly instead of zero as some saw. If it is so reproducible, he would have seen the wrong yardage being used in his tests.

Originally posted by Bort

I've tested more than once and it counts yardage correctly (when adding a print statement to print what it's using) in the sim when within the 10.

I'm wondering if the problem is not being approached from the right angle, as in we're missing something else in the equation that doesn't have to do with yardage, etc.


Last edited Oct 13, 2008 18:38:50
 
Link
 
Originally posted by buffalobills_tw
Originally posted by SteelersInsider


I think the 4th and goal one didn't always happen because sometimes it really was 4th and 1 or 4th and 2 like teams wanted to go for it. Then there weren't many teams that went for it anyway. So you are narrowing down the teams alot.

Then most took that out of their play book altogether. So the situations where it could possibly still happen are 4th and goal from the 4.5 to the 2.5 yard line (if the condition was to go if 4th and less than 2). So now we are talking about very few situations where the "bug" could arise. That is why you don't hear about it anymore. People have their AI set up better.

And for me, it wasn't "occasional", it happened wrong every time and I easily figured out what happened the 2nd time it screwed up and went for it on 4th and goal from the 8.

Not even close to the same problem.


Maybe it happened every time to you, but certainly not for others and Bort. If you read the link, Bort had trouble reproducing the bug at the time. It is not as reproducible as you claim.

Again, back to the topic, do you see any input wrong that OP provided? If not, this is a legit bug when defense AI tester shows something different to in-game play under same situation.



I hear what you are saying, your point is, the user is saying he didn't make a mistake. Based on the fact that he didn't make a mistake, it must be a bug. Everyone else has used the same logic.

It is unfortunate that hazy thinks his gameplans are so valuable that he doesn't trust his GM to take a look when he is having an error.

There really are no secrets to AI plays in this game though. You can watch other teams and copy exactly what they are doing.
 
tautology
offline
Link
 
The post above does not refute what I said...but this argument is pointless.

(A print statement that shows the yardage used is not the same as the sim behaving in the expected manner. The failure rate was 100% in my case, and 0% when I "fixed" it.)
 
Link
 
Originally posted by SteelersInsider

I hear what you are saying, your point is, the user is saying he didn't make a mistake. Based on the fact that he didn't make a mistake, it must be a bug. Everyone else has used the same logic.

It is unfortunate that hazy thinks his gameplans are so valuable that he doesn't trust his GM to take a look when he is having an error.

There really are no secrets to AI plays in this game though. You can watch other teams and copy exactly what they are doing.


Again, you misunderstand the two different things:

(1) What OP thought his AI would do
(2) What defense AI tester reported what play should be called

The case here is (2). It's not what OP thought, it is what defense AI tester reported that was different to in-game play. Other than inputting wrong data, defense AI tester should be consistent to in-game play, shouldn't it? Again, do you see any inputs wrong that OP provided? Do you have to see a snapshot of something to agree that his defense AI tester inputs are correct?
Last edited Oct 13, 2008 18:49:58
 
jdbolick
offline
Link
 
SteelersInsider, your problem is in assuming that it's always a user mistake instead of assuming that "bugs" are likely a user mistake.
 
Link
 
Originally posted by buffalobills_tw
Originally posted by tautology


Hmmm...I never heard that it was hard to track down, it happened every single time in my experience...if you had settings that would expose it.
The AI tester and the Sim had different outputs, and that, perhaps, made the problem more confusing than it needed to be.
I never followed up to see if that was resolved...do you know if it was?
I simply removed any chance of going for it inside the 10, which largely prevents the problem, though it is a little limiting strategically during earlier parts of the game where it might matter. Late in the game, you can work around it with relative safety.


I think Bort probably fixed the problem and that's why nobody sees it anymore. With so many new teams and inexperience owner/GM, I seriously double everyone knows this bug and works around it in their AI.

That bug did not fail every time, in the link I post, Bort had following comment. He tried several times and yardage reported correctly instead of zero as some saw. If it is so reproducible, he would have seen the wrong yardage being used in his tests.

Originally posted by Bort


I've tested more than once and it counts yardage correctly (when adding a print statement to print what it's using) in the sim when within the 10.

I'm wondering if the problem is not being approached from the right angle, as in we're missing something else in the equation that doesn't have to do with yardage, etc.





I never tried to put it back in. I will try to test it in my remaining games again, but it is hard to tell your RB or WR to run out of bounds at the 4 or 6 yard line on 3rd down and goal.

And maybe the CPU "took" 4 or 6 as the yards to go number, but when the "check" was for whether that 4 or 6 yards would produce a 1st down, then I think that is where the error is. It needs to check for a 1st down OR a TD. Seems to be only checking for a 1st down now. Then it would go back and push a 0 when it when to the output.
 
Link
 
Originally posted by jdbolick
SteelersInsider, your problem is in assuming that it's always a user mistake instead of assuming that "bugs" are likely a user mistake.


No, I only assume 99%.
 
Link
 
Originally posted by tautology
The post above does not refute what I said...but this argument is pointless.

(A print statement that shows the yardage used is not the same as the sim behaving in the expected manner. The failure rate was 100% in my case, and 0% when I "fixed" it.)


mm, it was different in my case that it only happened once in a while before I fixed my AI. I agree we should go back to focus on the current issue that I think OP showed a legit case.
 
Link
 
Originally posted by jdbolick
SteelersInsider, your problem is in assuming that it's always a user mistake instead of assuming that "bugs" are likely a user mistake.


has your team experienced this problem?

mine hasn't. And I watch ever play.

Every play of every game has followed my exact orders over the past 2 seasons except for the goal line thing.

That doesn't mean I haven't had things not go as I had hoped. It just turns out that every time it failed, it was ME that failed.

And then I've seen a similar 99% failure rate out here in the bug forum. Ask Forbin.
 
Link
 
Originally posted by buffalobills_tw
Originally posted by tautology

The post above does not refute what I said...but this argument is pointless.

(A print statement that shows the yardage used is not the same as the sim behaving in the expected manner. The failure rate was 100% in my case, and 0% when I "fixed" it.)


mm, it was different in my case that it only happened once in a while before I fixed my AI. I agree we should go back to focus on the current issue that I think OP showed a legit case.



so it happened to your team also?
 
Page:
 


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