How to stop AI from attempting ridiculously long field goals

[DarthRambo]

Watching cpu vs cpu games for obe of my cfms. The wind at their back, the Bears attempted a 61, 61, and 60yd field goals. Plus a fake fg inside the red zone when only down 17-0 in the 3rd quarter! Wtf??

Is there any way to fix their logic with some workaround? Super frustrating to watch such a great game turn into crap. The first two 61yd attempts were in the first quarter. Gave up good field position and the Packers scored a touchdown after each miss. And now they were down 17-0 after the first quarter.

I don't see a way to remedy this huge issue in my mind. If anyone has any suggestions I'd love to try something!

[ICE_790120q]

Re: How to stop AI from attempting ridiculously long field goals

I've noticed that as well. I've lowered the FG power but that doesn't seem to do the trick other than getting short kicks but yes, they will continue to attempt those very, very long kicks (58+) which IRL are usually reserved for end of half or last minute tie/win situations.

I think the problem is that unrealistic wind scenario where most of the time is against or for (usually never sideways) and always around 8mph. Seems the CPU AI is tied to having the wind on their back to attempt those long FGs.

[sinthros]

Re: How to stop AI from attempting ridiculously long field goals

Probably nothing you can do about it unless you're on PC and can mod it with Frosty. This is one of the (many) issues Sabo has helped to remedy. I could never go back to playing the regular game without his mod tbh.

[Cavs2016]

Re: How to stop AI from attempting ridiculously long field goals

Had a 67 yarder attempted on me. Granted there was wind assistance, but the context of the kick didn’t make sense. Wasn’t the end of a half or anything. Missed pretty badly.

I do like one 57+ yarder that was attempted on me at the end of the half. Didn’t think he had the leg so I set my FG return man out. Ran it all the way back

[BigOrangeVol4Life]

Re: How to stop AI from attempting ridiculously long field goals

This game would be so much better if the CPU didn't attempt these ridiculous field goals you speak of and also ran its receivers past the first down marker on 3rd down. If it's 3rd down and 9, don't run a play that picks up 5.

[PGaither84]

Re: How to stop AI from attempting ridiculously long field goals

This game would be so much better if the CPU didn't attempt these ridiculous field goals you speak of and also ran its receivers past the first down marker on 3rd down. If it's 3rd down and 9, don't run a play that picks up 5.

Bill Walsh wrote that if it is 3rd and 7 or more, your route should get half or more of the needed yards and the receiver is expected to pick up the rest.

He continued by explaining that a completion on 3rd down which came up short but had a chance also feels better than an incomplete pass which fires up the defense.

Also, back in the day, even Bill Belichick's defensive playbooks with the Giants referred to the first 5 yards as the "no coverage zone" and they were happy to give up dink and dunk passes and swarm to the ball.

That is a part of the bend but don't break philosophy where it doesn't matter if they get down to the 1 yard line, just don't let them score a TD and live for the next play.

Those are two thing I teach my team of amateur adults and we have won multiple league championships as well.

Sure, if a route combination/play can get 9+ on 3rd and 9, then make that throw, but a route combination such as SMASH and LEVELS is designed to force a high-low read against zone and get leverage against man. If they play soft to stop the high read, then the 5 yard curl or 5 yard in should catch it in space and pick up the remaining 4 with RAC yards.

Then there is also the philosophy of getting the ball to your play makers and how a ball carrier is expected to make the first man miss and only go down against a swarm or being forced out.

Oh, and even if you come up short, there are situations in games where it becomes 4 down territory. Why punt from their 40 or 41 yard line and net 20-30 yards when you can go for 4th and 4 or less where your guy came up short? I am a sim style player who is willing to go for it almost as often as statistics suggest you should.

[TX.Leaguer]

Re: How to stop AI from attempting ridiculously long field goals

Bill Walsh wrote that if it is 3rd and 7 or more, your rpute should get half or more of the needed yards and the receiver is expected to pick up the rest.



He continued by explaining that a completion of 3rd down which came up short but had a chance also feels better than an incomplete pass which fires up the defense.



Also, back in the day, even Bill Belichick's defensive playbooks with the Giants refered to the first 5 yards as the "no coverage zone" and they were happy to give up dink and dunk passes and swarm to the ball.



That us a part of the bend but don't break philosophy where it doesn't matter if they get down to the 1 yard line, just don't let them score a TD and live for the next play.



Those are two thing I teach my team of amatuer adults and we have won multiple league championships as well.



Sure, if a route combination/play can get 9+ on 3rd and 9, then make that throw, but a route combination such as SMASH and LEVELS is desinged to force a high-low read against zone and get leverage against man. If they play soft to stop the high read, then the 5 yard curl or 5 yard in should catch it in space and pick up the remaining 4 with RAC yards.



Then there is also the philosophy of getting th ball to your play makers and how a ball carrier is expected to make the first man miss and only go down against a swarm or being forced out.



Oh, and even if you come up short, there are situations in games where it becomes 4 down territory. Why punt from their 40 or 41 yard line and net 20-30 yards when you can go for 4th and 4 or less where your guy came up short? I am a sim style player who is willing to go for it almost as often as statistics suggest you should.

Well said. Countless times on Sunday you’ll see completions less than the marker on 3rd downs.

[TheBleedingRed21]

Re: How to stop AI from attempting ridiculously long field goals

This is in the logic files on what the CPU calls. Unfortunately consoles won’t really be able to fix this properly.

[JayD]

Re: How to stop AI from attempting ridiculously long field goals

This is due to the wind having an over exaggerated affect on kicking distance. You'll notice that the CPU will only attempt ridiculously long field goals when the wind is at their backs.

[burth179]

Re: How to stop AI from attempting ridiculously long field goals

This game would be so much better if the CPU didn't attempt these ridiculous field goals you speak of and also ran its receivers past the first down marker on 3rd down. If it's 3rd down and 9, don't run a play that picks up 5.

Well, to be fair, I find myself saying this when I watch real football more often than I should on 3rd and long. So I wouldn't say it's totally unrealistic, teams do this somewhat often in real life if the defense forces them to take the check down.

[DarthRambo]

Re: How to stop AI from attempting ridiculously long field goals

This is due to the wind having an over exaggerated affect on kicking distance. You'll notice that the CPU will only attempt ridiculously long field goals when the wind is at their backs.

Yeah this seems to be what triggers it. Just ridiculous to me that something this bad can be in the game. Game testers should watch a bunch of cpu vs cpu games before releasing a game. This will clearly show you all flaws in AI logic, and gameplay.

Sent from my LG-G710 using Operation Sports mobile app

[tg88forHOF]

Re: How to stop AI from attempting ridiculously long field goals

This game would be so much better if the CPU didn't attempt these ridiculous field goals you speak of and also ran its receivers past the first down marker on 3rd down. If it's 3rd down and 9, don't run a play that picks up 5.

So, the "run routes past the sticks on 3rd and 9" is an example of where you'd prefer less realism then? Because that doesn't just happen in the real league, it's common, and often the correct call by the coach, and correct read by the QB.

It's cool if that's the case, just pointing out this is another "everybody wants realism until they get it" moment if so.