Confirmed CK III - AI - Army Pathfinding Broken in 1.3

[SavvyLad]

Short summary of your issue
AI - Army Pathfinding Broken in 1.3

Game Version
1.3

What OS are you playing on?
Windows

What platform are you using?
Steam

Do you have mods enabled?
No

Have you tried verifying your game files (Steam only)?
Yes

How much "pain" is this causing you?
10

Please explain the issue you experienced in the most condensed way possible
I have seen two examples of this already and had enough. First it was in the Crusade for Jerusalem. The bulk of the men were from the Pope, and ALL of his forces decided to pathfind THROUGH the Iraqi desert to the Persian Gulf near Basra. They intended to sail ALL THE way around the ENTIRE ARABIAN PENINSULA just to land in the southern Levant via the Red Sea.

So instead of just landing in Acre or Gaza, etc, they all died of starvation/heat/loss of supplies in Iraq, entirely bypassing the target area of the Kingdom of Jerusalem...

The second incident is with my ally, the King of Sardinia. He is holy warring for the Duchy of Tunis. Instead of just landing there and fighting, his intent is to sail OUT of the Mediterranean entirely, hug the coast of Spain, and disappear into the North Atlantic...nowhere near Tunis or any of the fighting...

Please explain how to reproduce the issue
Unknown - it doesn't happen always. One case was in a Crusade, and another was a normal holy war. Maybe look for religious conflicts in general, that involve allies.

Is there anything else you think could help us identify/replicate the issue?
No, but this never happened pre-1.3

I have attached a save game
Yes

Upload Attachment
File(s) attached

 

[SavvyLad]

Forgot save:

 

[wanoO]

I can confirm this also happened in my game on beta 1.3.1 ironman. The first crusade followed roughly the same path:
Black Sea > Caucasus > Black Sea > Causcasus (yes the AI went back and forth) > Persia > Around Arabian peninsula > Landing south of Mecca
Over 12K dead in attrition (out of 20K), Crusade ended as they finally landed since Jerusalem hadn't been taken (couldn't do it on my own).
The AI seemed to ignore the lack of supplies as well and even some of the smaller stacks that didn't follow the Pope were starving in the Caucasus.
The crusade was triggered in ~950AD soon after my invasion triggered them to start. Never seen the AI do something this dumb pre-1.3, calculations are clearly broken somewhere.

The second Crusade turned out fine. AI (mostly) landed where it should, had enough men to take Jerusalem.

 

[Emir Amray Najidid of Fez]

Greetings SavvyLad!

March for Crusade to retake the Holy Land it's not easy, but obviously it should be that devastating for the army. Thank you for your Keen eye. I'll send the letter to the Pope. Maybe he employ better guides for the army.

Best Regards!

 

[Little Ian]

Just saw this. Pope declared Crusade for Jerusalem, marched into Persia and into the desert for awhile, eventually embarking in the Persian Gulf and sailing around the full Arabian peninsula to land as shown by pictures in OP.

 

[vandevere]

The Pathfinder can be unnecessarily loopy. An example off the top of my head, my Rally Point was in Provence, and the Pope calls me into a war. I raise my levies and get them together for the trip to Rome. Is it a simple matter of crossing the Ligurian Sea?

Hell no!

I have to take my ships all the way down Italy, and Sicily, go around the Boot, then go up the Adriatic Sea. If I'm lucky, I'll be able to land at either Ancona or Fermo, and get to Rome that way. Meanwhile, the Pope's getting sieged down by the Muslims, and my troops are getting Scurvy, and dropping like flies.

There's no justifiable reason for all of this looping.

 

[daniel.demasi]

I've had a few instances where AI have done this, starting to move, then stopping, starting again, stopping. It can be extremely frustrating if they happen to be your Allies, and they just get stuck, maybe deciding to move when you are all dead.