User Pass
Home Sign Up Contact Log In
Forum > Europe West AAA League > Europe West AAA #1 > Is it me or is the AL not doing what it is suppose to be doing?
Page:
 
Drachir
offline
Link
 
This season has been puzzling to me as several of my teams have been going for it on 4th down when nowhere in the AL does it say to go for it on 4th down and it specifies 100% punt beyond the FG range and 100% FG in field goal range.

During the preseason with one of my other teams Aussie Cardinals that I own not once did it even attempt a punt and went for it on 4th down six times.

I wasn't too concerned about it until I noticed today that our first possession we went for it on 4th down when we were in FG range and it would have set the tone for the game.

I also noticed that Burnt Orange Rising went for it on 4th down two times in one drive in the 1st quarter. Not sure if they had this planned or not.
 
im4ut999
offline
Link
 
BOR does have it in their AI to go on 4th and short.....

Have you used the AI tester? Could be something buried in the qtr specific AI calls...or could be a missing down setting in another play setting....
 
CoolChuck
offline
Link
 
We had several really strange things happen to our AI today. I'm going to post a few of them on the bugs forum.
 
mraadt
offline
Link
 
In our AAA World Cup, one game had us kicking 66 and 62 yard field goals. I couln't find this anywhere in our AI. I even put in the exact situation into the AI tester and it keeps coming up punt. Oh well, we didn't want to win that game anyway.
 
ultrajer
offline
Link
 
Originally posted by im4ut999
BOR does have it in their AI to go on 4th and short.....

Have you used the AI tester? Could be something buried in the qtr specific AI calls...or could be a missing down setting in another play setting....


So does the Blackhawks
 
Drachir
offline
Link
 
Originally posted by mraadt
In our AAA World Cup, one game had us kicking 66 and 62 yard field goals. I couln't find this anywhere in our AI. I even put in the exact situation into the AI tester and it keeps coming up punt. Oh well, we didn't want to win that game anyway.


At first glimpse of this a common mistake is someone puts FG range at say 55 thinking it would be a 55 yard FG when actually it would be a 72 yard FG because they forgot to add the 17 yards to it for placement of the kick and the endzones which is standard football protocol and the way Bort has it set up. This is probably the mistake you are making.
 
Drachir
offline
Link
 
Originally posted by im4ut999
BOR does have it in their AI to go on 4th and short.....

Have you used the AI tester? Could be something buried in the qtr specific AI calls...or could be a missing down setting in another play setting....


I am going to have to test it with the AL and see what it says....Because this is very frustrating but to be honest i have a pretty basic AL nothing to complex...
 
briano32
offline
Link
 
Originally posted by Drachir
Originally posted by mraadt

In our AAA World Cup, one game had us kicking 66 and 62 yard field goals. I couln't find this anywhere in our AI. I even put in the exact situation into the AI tester and it keeps coming up punt. Oh well, we didn't want to win that game anyway.


At first glimpse of this a common mistake is someone puts FG range at say 55 thinking it would be a 55 yard FG when actually it would be a 72 yard FG because they forgot to add the 17 yards to it for placement of the kick and the endzones which is standard football protocol and the way Bort has it set up. This is probably the mistake you are making.


Are you sure about that?

Originally posted by
Max Field Goal Range, from the place hold to the uprights, LOS + 17 yds (leave blank for "auto")


I took this to mean that the 17 yards is already factored into the input.

 
Drachir
offline
Link
 
Originally posted by briano32
I took this to mean that the 17 yards is already factored into the input.



Positive...Test your AL and you will see...Mine is set at 30 yard line for Aussie because of the level cap...If you test your offensive AL at 31 yard line opponents and you have the AL set to punt ouf of FG range you will come up with PUNT as the only output...

It was a big problem for us a couple of seasons ago because the OC put 55 yards for max distance and it was attempting those 65+ yard FG's.
 
Drachir
offline
Link
 
Anyway I got the problem solved and still don't have a clue what was causing it to be an issue....It kept showing NO matching input when I put the situation that we had today where we had it on the Opponents 30 yard line with 4th down and 1.5 yards to go....I just played around with it for a few until it showed what it should be showing...
Edited by Drachir on Oct 21, 2009 11:56:26
 
Redass Ranch
offline
Link
 
Originally posted by Drachir
Originally posted by briano32

I took this to mean that the 17 yards is already factored into the input.



Positive...Test your AL and you will see...Mine is set at 30 yard line for Aussie because of the level cap...If you test your offensive AL at 31 yard line opponents and you have the AL set to punt ouf of FG range you will come up with PUNT as the only output...

It was a big problem for us a couple of seasons ago because the OC put 55 yards for max distance and it was attempting those 65+ yard FG's.


There is a second setting within the Input/Output that also effects when to kick FG or not to kick.

Ball Spot (yard line)... setting this to your specifications will help this, but not solve it.

Edited by Redass Ranch on Oct 21, 2009 12:03:49
 
baumusc
offline
Link
 
Originally posted by Drachir
Anyway I got the problem solved and still don't have a clue what was causing it to be an issue....It kept showing NO matching input when I put the situation that we had today where we had it on the Opponents 30 yard line with 4th down and 1.5 yards to go....I just played around with it for a few until it showed what it should be showing...


When it shows no matching input the sim will do some crazy shit. Same with on defense. I found that out the hard way a couple of seasons ago.
 
mraadt
offline
Link
 
Originally posted by Drachir
Originally posted by briano32

I took this to mean that the 17 yards is already factored into the input.



Positive...Test your AL and you will see...Mine is set at 30 yard line for Aussie because of the level cap...If you test your offensive AL at 31 yard line opponents and you have the AL set to punt ouf of FG range you will come up with PUNT as the only output...

It was a big problem for us a couple of seasons ago because the OC put 55 yards for max distance and it was attempting those 65+ yard FG's.



That's the problem, I tested the AI over and over from that yard line. Every time I tested it, it punted. Only kicked it in the game. But I'll definitely look again.
 
EagleOtto
offline
Link
 
Originally posted by Drachir
Positive...Test your AL and you will see...Mine is set at 30 yard line for Aussie because of the level cap...If you test your offensive AL at 31 yard line opponents and you have the AL set to punt ouf of FG range you will come up with PUNT as the only output...

It was a big problem for us a couple of seasons ago because the OC put 55 yards for max distance and it was attempting those 65+ yard FG's.


I asked support last season, they swore 55 yards meant a 55 yard field goal, meaning you would only kick at the 38 or closer...
(We had were at 40 yardline and punted).

Something has always been weird with FG stuff, I learned never to ever use the 'in FG range' and 'near field goal range' special circumstances
 
Cmdr.Groaning
offline
Link
 
I've had problems with custom slots bleeding into regular depth chart roster, having a WR in custom slot FB1 then seeing WR lead blocking as FB from the I 4th/short, but it worked that one time, with depth chart roster and formation page set right. Other glitches like this. Setting HB1 to weak I formations page but not changeing to HB2 when very next play is Strong I set to HB2, and HB2 is plenty rested. All kinds of custom slot glitches.
And there was 1 time when we kicked a FG on 4th/med when AI input was punt because our LV43 K just couldn't be consistant enough for a 50+ yrd FG, he made it though.
 
Page:
 


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