Confirmed Game Crash 5th March 1581

[Demostravius]

Integrity​

I have verified my game files (on Steam)​

Yes

I have disabled all mods​

Yes

Required​

Summary​

Game Crash 5th March 1581

Description​

Game crashes to desktop on this date every time during my Great Britain run through.

Steps to reproduce​

Simply run the game and it crashes on this date.

Game Version​

1.36.1.0

OS​

Windows

Additional​

Bug Type​

• Crash to Desktop

Attachments​

View attachment minidump.dmpView attachment error.logView attachment UK.eu4

Screenshot​

View attachment error.log

 

[Qloc_Crepuscular_Rays]

Hello there! With your help, we have now confirmed the issue and added it to our database!

 

[grotaclas]

The crash seems to happen due to a bug in autonomous sieging. I tried your save and it seems to help if I give new movement orders to your two armies which are currently doing that("1st army" in quito and the "1st army" which is currently moving from Raritan to Espachomy)

 

[Demostravius]

The crash seems to happen due to a bug in autonomous sieging. I tried your save and it seems to help if I give new movement orders to your two armies which are currently doing that("1st army" in quito and the "1st army" which is currently moving from Raritan to Espachomy)

You are a star! I'll give it a go!

Deleted one army as it was movement locked, and got the other to do something else. It worked!

 

[FrogCrusher]

You are a star! I'll give it a go!

Deleted one army as it was movement locked, and got the other to do something else. It worked!

For your knowledge, if you have a navy, there is a "feature" to unlock locked movement by commanding a movement requiring boat (for example to an Island or by ctrl+click on a coastal province) and then say yes to the popup asking you want to use your boats for the movement

 

[grotaclas]

Deleted one army as it was movement locked, and got the other to do something else. It worked!

The movement lock is no problem in this case, because you can still give them a new movement order. It won't prevent them from going Espachomy, but it will cancel the autonomous sieging(if you accept that in the popup). That seems to be enough to prevent the crash in your game. Maybe the crash has something to do with the fact that the province which the army is trying to reach is not reachable anymore, because you don't have mil access to the provinces behind Espachomy.
For context, you can see in the exception.txt that the crash happens in the function CControllerArea::FindBestPathV2 which gets called from the function CCarpetSiegeArmyMission::CalcBestTargetProvincePath (you need to let it crash on Linux or macOS to see the function names)