[1307.18] 'ignore plotted course' doctrine problem

[pkj0330]

'ignore plotted course' is set to 'inherited 'No' in the mission doctor line, it changes to 'yes'.
I try to set it to 'No' again, it changes to 'Yes'.

I attach a YouTube link.
https://youtu.be/mesLmoRhes4

And I also attach the scenario file.

[DaveFromCTX]

'ignore plotted course' is set to 'inherited 'No' in the mission doctor line, it changes to 'yes'.
I try to set it to 'No' again, it changes to 'Yes'.

I attach a YouTube link.
https://youtu.be/mesLmoRhes4

And I also attach the scenario file.

FYI be prepared to be told this is fixed and it not be fixed.

https://www.matrixgames.com/forums/view ... 0#p5078490

[thewood1]

I think it has never been listed as fixed in any of the release updates. I didn't see it listed. I think this is wrapped up in the leader behavior issues that the devs have been working to resolve for a while now.

There are several issue like this that appear to be taking a while to fix. Subs not attacking on auto fire, some aircraft not turning on radars to attack, modern SAMs not turning on radar to attack, leader behavior on strike missions, and maybe a few others. The best way to live life is if its not in the patch notes, it usually didn't get addressed yet.

[rosolano079]

Subs not attacking on auto fire, some aircraft not turning on radars to attack, modern SAMs not turning on radar to attack, leader behavior on strike missions ….

I suspect, just based on my observations while playing and testing, that these specific issues are all directly related to player-ordered engagements.

It looks to me that if the AI is left completely to its own devices, everything works as intended. It’s when the player manually orders an engagement, or changes side posture, something breaks in the engagement logic.

If that’s the case, I’m not surprised it’s been difficult to address. AI engagement logic must be incredibly complex.

[thewood1]

Not sure on the underlying detail, but they all seemed to crop up within a short time of each other.

[DaveFromCTX]

Subs not attacking on auto fire, some aircraft not turning on radars to attack, modern SAMs not turning on radar to attack, leader behavior on strike missions ….

I suspect, just based on my observations while playing and testing, that these specific issues are all directly related to player-ordered engagements.

It looks to me that if the AI is left completely to its own devices, everything works as intended. It’s when the player manually orders an engagement, or changes side posture, something breaks in the engagement logic.

If that’s the case, I’m not surprised it’s been difficult to address. AI engagement logic must be incredibly complex.

Issue reference by me was strike mission, no human intervention.

[pkj0330]

The settings have changed even though i set 'no' at side doctrine.

This problem happened a long time ago. I don't remember exactly when the problem started.