Hello, I am having issues with my team kicking field goals when they are in field goal range. I dont see much as settings in the tactics can someone please help....
Forum > FAQ's, Player Guides and Newbie Help > Causal Team Field Goals and Defense
Novus
offline
offline
Originally posted by crazyc01109
Hello, I am having issues with my team kicking field goals when they are in field goal range. I dont see much as settings in the tactics can someone please help....
What exactly is the "issue" you're having? Be specific.
Hello, I am having issues with my team kicking field goals when they are in field goal range. I dont see much as settings in the tactics can someone please help....
What exactly is the "issue" you're having? Be specific.
crazyc01109
offline
offline
My offense is not kicking field goals on 4th down when they are in field goal range they just keep going for it...
Originally posted by crazyc01109
17 yds
The FG setting reads:
Max Field Goal Range, from the place hold to the uprights, LOS + 17 yds (leave blank for "auto")
yds
This is always confusing but putting 17 in there means that you would only kick from the "0". You need to set it to 34 for it to kick from the 17.
Someone please correct me if I am wrong, but whatever goes in that Fg Range box includes the 17. So, if you put 50, it kicks a 50, not a 67 yarder...right?
17 yds
The FG setting reads:
Max Field Goal Range, from the place hold to the uprights, LOS + 17 yds (leave blank for "auto")
yds
This is always confusing but putting 17 in there means that you would only kick from the "0". You need to set it to 34 for it to kick from the 17.
Someone please correct me if I am wrong, but whatever goes in that Fg Range box includes the 17. So, if you put 50, it kicks a 50, not a 67 yarder...right?
Edited by ezra_ on Aug 3, 2013 12:58:22
Originally posted by ezra_
The FG setting reads:
Someone please correct me if I am wrong, but whatever goes in that Fg Range box includes the 17. So, if you put 50, it kicks a 50, not a 67 yarder...right?
It's whatever you put in the box + 17
The FG setting reads:
Someone please correct me if I am wrong, but whatever goes in that Fg Range box includes the 17. So, if you put 50, it kicks a 50, not a 67 yarder...right?
It's whatever you put in the box + 17
Originally posted by Indicud
It's whatever you put in the box + 17
No. See the bold in the quote below.
Originally posted by Bort
I've noticed a few things that keep coming up with people's AI settings that's giving them problems.
-------------------
Watch out for multiple inputs that are mutually exclusive, where there is a gap in the middle.
For instance:
input 1: Outside FG range, between own goal and opponent 35: Punt
input 2: Inside FG range, between opponent 35 and opponent goal: Kick FG
If you're on the opponent 38 and your FG range is for the 40 yard line, neither of these will trigger.
Input 1 won't fire because you're not outside FG range.
Input 2 won't fire because you're not between the 35 and opponent goal
So it goes on to the next thing which is probably a pass or something and you go for it.
-------------------
Trying to get too complex too fast:
The intent of the AI stuff was to allow you to add overrides for certain situations that you didn't like in the game's general play calling AI.
I've seen some people put in 100-200 inputs and outputs to try and make a crazy playbook. While this should technically work, you are very likely to run into problems you didn't account for and will then be hard to track down because you have 7 bajillion inputs to look through.
The best way to approach it, in my opinion, is to start simple, with a few things you want to do, such as go for it on 4th down within the 30, or always pass on 2nd and long, etc. Then watch your next game with your settings, and add more input/outputs for situation that come up in the game that you don't like the playcalling for.
If you try to think of every little thing ahead of time, you'll probably end up missing something and scratching your head for 3 hours trying to figure it out.
-------------------
Double check your inputs:
I've seen some inputs created with downs 1-4 entered when people actually wanted only 2nd down, or no scores entered when they wanted it to be only when trailing, etc.
Fields to watch especially:
Down
Score
# Receivers (0 - 6 is the default; make sure you change it or it will match every single play!)
------------------
Field goal range:
Set it to the length of the kick, not the line of scrimmage. A 40 yard kick is from the 23 yard line (LOS + 10 for the endzone + 7 for the place hold).
------------------
Use the AI tester! There's an offense one and I will add a defense one shortly. These will help you test before your game happens so you're not flying blind.
------------------
Hope that helps some of you!
It's whatever you put in the box + 17
No. See the bold in the quote below.
Originally posted by Bort
I've noticed a few things that keep coming up with people's AI settings that's giving them problems.
-------------------
Watch out for multiple inputs that are mutually exclusive, where there is a gap in the middle.
For instance:
input 1: Outside FG range, between own goal and opponent 35: Punt
input 2: Inside FG range, between opponent 35 and opponent goal: Kick FG
If you're on the opponent 38 and your FG range is for the 40 yard line, neither of these will trigger.
Input 1 won't fire because you're not outside FG range.
Input 2 won't fire because you're not between the 35 and opponent goal
So it goes on to the next thing which is probably a pass or something and you go for it.
-------------------
Trying to get too complex too fast:
The intent of the AI stuff was to allow you to add overrides for certain situations that you didn't like in the game's general play calling AI.
I've seen some people put in 100-200 inputs and outputs to try and make a crazy playbook. While this should technically work, you are very likely to run into problems you didn't account for and will then be hard to track down because you have 7 bajillion inputs to look through.
The best way to approach it, in my opinion, is to start simple, with a few things you want to do, such as go for it on 4th down within the 30, or always pass on 2nd and long, etc. Then watch your next game with your settings, and add more input/outputs for situation that come up in the game that you don't like the playcalling for.
If you try to think of every little thing ahead of time, you'll probably end up missing something and scratching your head for 3 hours trying to figure it out.
-------------------
Double check your inputs:
I've seen some inputs created with downs 1-4 entered when people actually wanted only 2nd down, or no scores entered when they wanted it to be only when trailing, etc.
Fields to watch especially:
Down
Score
# Receivers (0 - 6 is the default; make sure you change it or it will match every single play!)
------------------
Field goal range:
Set it to the length of the kick, not the line of scrimmage. A 40 yard kick is from the 23 yard line (LOS + 10 for the endzone + 7 for the place hold).
------------------
Use the AI tester! There's an offense one and I will add a defense one shortly. These will help you test before your game happens so you're not flying blind.
------------------
Hope that helps some of you!
@Romo, I set a team I OC for FG range to 23 (I put that in the box) and after I did that like mid season, the kicker never kicked a FG over 40 yards.
Originally posted by Indicud
@Romo, I set a team I OC for FG range to 23 (I put that in the box) and after I did that like mid season, the kicker never kicked a FG over 40 yards.
It's generally a good idea to trust the guy who wrote the sim.
@Romo, I set a team I OC for FG range to 23 (I put that in the box) and after I did that like mid season, the kicker never kicked a FG over 40 yards.
It's generally a good idea to trust the guy who wrote the sim.
Originally posted by InRomoWeTrust
It's generally a good idea to trust the guy who wrote the sim.
Just going by what I tested lol.
It's generally a good idea to trust the guy who wrote the sim.
Just going by what I tested lol.
You are not logged in. Please log in if you want to post a reply.
