Confirmed Repeatable crash in December 1450

[streanor]

Integrity​

I have verified my game files (on Steam)​

Yes

I have disabled all mods​

Yes

Required​

Summary​

Repeatable crash in December 1450

Description​

Playing Aragon game. Released a province in Catalonia to avoid Sindicat Remenca until after getting iberian wedding. Got a queen regency in 1450 and have been waiting for it to fire with MTTH of 12 months. In December of 1450 game consistently crashes to desktop, possibly related to Iberian Wedding without having decided whether to go peasant republic.

Steps to reproduce​

Load up game and play until end of month. Possible it can be replicated by releasing a province to avoid sindicat remenca and then getting iberian wedding.

Game Version​

1.36.2

OS​

Mac

Additional​

Bug Type​

• Crash to Desktop

Attachments​

View attachment aragon.eu4

Screenshot​

 

[strqfzd911]

Alright so I had a look at your save. The issue isn't actually due to the iberian wedding, it occurs when the Ottoman AI annexes Byzantium which has Athens as a hereditary pronoia.

Note: If you want to continue the save, I have had some success in getting past december with the ottomans annexing them around June next year with no crash, weirdly, so if you are persistent enough you can keep playing.

For the devs: Here's how to reproduce it:

If you go into spectator mode and click onto the Ottomans, you'll see that they are just about to stackwipe the byzantine army which causes them to send the peace-deal in the next month which full annexes them. I was able to reproduce the crash by sending the peace-deal which demands full annexation for Byzantium + Athens.

I tested a few scenarios:

1) I let one day pass so the byzantine army is stackwiped, then I send a peacedeal to byzantium which demands their full annexation + Athens. Result: Game Crash
2) I send a peacedeal to byz demanding their full annexation but don't take athens. Result: Game Crash again
3) I send a peacedeal to byz demanding only Athens. Result: No Crash

I'm guessing the game can't handle removing Athens' diplomatic status as a Pronoia if their overlord doesn't exist anymore... Based on what I gathered from the crash log. I've attached the exception and screencap of the error log when annexing byz.

 

[Nixou]

Something similar happened to me, except the crash happens in 1451 while playing Mongolia: games completely crashes. Hopefully the kink will be ironed out quicly, it's not fun playing with a ticking time bomb that threatens to render the game unplayable early on.

 

[Seiryn]

Alright so I had a look at your save. The issue isn't actually due to the iberian wedding, it occurs when the Ottoman AI annexes Byzantium which has Athens as a hereditary pronoia.

Note: If you want to continue the save, I have had some success in getting past december with the ottomans annexing them around June next year with no crash, weirdly, so if you are persistent enough you can keep playing.

For the devs: Here's how to reproduce it:

If you go into spectator mode and click onto the Ottomans, you'll see that they are just about to stackwipe the byzantine army which causes them to send the peace-deal in the next month which full annexes them. I was able to reproduce the crash by sending the peace-deal which demands full annexation for Byzantium + Athens.

I tested a few scenarios:

1) I let one day pass so the byzantine army is stackwiped, then I send a peacedeal to byzantium which demands their full annexation + Athens. Result: Game Crash
2) I send a peacedeal to byz demanding their full annexation but don't take athens. Result: Game Crash again
3) I send a peacedeal to byz demanding only Athens. Result: No Crash

I'm guessing the game can't handle removing Athens' diplomatic status as a Pronoia if their overlord doesn't exist anymore... Based on what I gathered from the crash log. I've attached the exception and screencap of the error log when annexing byz.

Hey, my game is crashing a very similar way , with byzantium about to be annexed.
Unfortunately my exception.txt is way less useful, I assume because I'm on linux.
Can you check if this is the same issue ?

 

[Qloc_Crepuscular_Rays]

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

 

[maximous.asterious]

I'm here to say that the issue is still there. I just started a new campaign as France, and the game doesn't allow me to continue as it crashes each time in 1451, just as Ottomans are about to annex Byzantium. I play on Linux.

 

[DoctorSnakes]

I think I have the same exact problem. I get a repeatable crash playing as Norway in 1451, and the Ottomans also seem to just about be full annexing Byzantium. I am also playing on Linux.

 

[DoctorSnakes]

Also, I tried strqfzd911's idea but was not able to progress the save much farther, so this is a pretty game-breaking bug which stops me from progressing any further. Please fix ASAP!

 

[Intellectual Tux]

Similar issue over here. Linux too.

 

[honkajoki]

Somewhat related messages from the main forum. 1.36 review thread:

Last week we released patch 1.36.2, fixing several issues reported after 1.36 ‘Byzantium’ release. We’re so far quite happy with the stability and level of quality of this update, so we’ve decided this will be the last patch for it. This doesn’t mean that there aren’t issues that need to be fixed, or that there aren’t going to be any new ones that arise; but we will be tackling them in the 1.37 update, which is planned for the first half of 2024.

Seems to indicate that there shall be no hotfix. The cycle for updates tends to be months from the first dev diary, and that has not appeared yet.

1.36.2 patch thread:

Now I count 11 bug forum threads about CTDs with 1.36.2, not tagged as duplicates. Perhaps more as there are some with no version data and some from older versions that are not tagged as fixed. I sure hope a hotfix is furiously worked on?

That has got no reply. In both of those threads the last posts by devs are from December.

It seems that this bug will be with us for a good while still. Sure hope they'd prove me wrong on that...

 

[Execrable_crown]

I was wondering why the hell I had about 1 out of 3 games randomly be plagued by crashes between 1449 and 1455. Also on Linux. Hope they fix it.

 

[killcreak]

Does anyone at Paradox understand that this bug literally ends your current run and you have to start a new game? Also happens frequently, making the whole game PoS at the moment.

 

[SenileSequoyah]

Seriously, gamebreaking bug that community has managed to precisely identify for months yet still no fix!

 

[Sheldorium2]

This is ridiculous. EU4 has been de facto unplayable on Mac OS for 3 months as the game crahes almost every time the Ottomans annex Byzantium.
If you cant fix the bug you could simply prevent Byzantiums AI from turning Athens into a Pronoia which is a poor decision in the first place.
Yet Paradox has done nothing.

Honestly just remove the "supports mac os" icon on Steam at this point it is a lie.

 

[yunusberk]

Having the same problem it crushes because of Ottomans annexing Byzantium. I'll just start again, hoping it won't happen.

 

[Spekman]

Yeh I can't believe they can just say they're happy with how it's working... I've had 5 diff saves all crash one after another.... might try reverting back to 1.35 until 1.37 comes out.... assuming that should work???

 

[DoctorSnakes]

Yeh I can't believe they can just say they're happy with how it's working... I've had 5 diff saves all crash one after another.... might try reverting back to 1.35 until 1.37 comes out.... assuming that should work???

Yeah, that should work, since pronoiars weren't added until then (which is the source of the crashes).

 

[Spekman]

Yeah, that should work, since pronoiars weren't added until then (which is the source of the crashes).

yup confirmed it works... played through to 1479, and no more Byzantium

 

[ndmaduro]

It's just laughable that the "solution" from Paradox is to "deal with it until we push the next major update". You can't play the KoK content without 1.36. So basically, since launch anyone on Mac can't access the content we've paid for... and we're ok with this?

We should be demanding more from a MAJOR game studio... it's not like this is a small operation that is financially struggling...

Between this launch and their unplayable Stellaris DLC launch just before launch of KoK, I'm about ready to give up on Paradox as a whole and stop giving them any of my money because you can't play their games anyways a large part of the time.

 

[fabioke]

My perfect save ruined