Game crashing on events

[JayJJoker]

Since I dont wonna make a repost and upload all the files

Game crashing on events

Information I have verifed my game files (Steam only) Yes I have disabled all mods Yes I am running the latest game update Yes Required Summary Game crashing on events Description The game is crashing on events. Some of them are from persia...

forum.paradoxplaza.com

My game seems to be crashing due to some events, might be caused by the new dlc, but it was still happening when I dispabled the persia dlc.

Any help/thought would be appreciated

 

[AndrewT]

Game Version​

1.9.2.1

Can I ask why you are not on the current game version, which is 1.11.2? Because if this is a bug in 1.9.2.1 it has probably already been fixed in a later version.

 

[JayJJoker]

Sorry I looked at the past betas on steam and one of the posts below it was 1.9.2.1 and thought that 1.9.2.1 was the latest

i have amended the above post and I am 110% on 1.11.2 (Peacock)

 

[AndrewT]

Any mods in use?

Is this crash repeatable from a particular save or saves? Or more random?

 

[JayJJoker]

No mods used, before making the reort i unsubscribed from every mod i had, deleted the game and any lingering files then reinstalled.
The report if from the same save game (the one attached at the beginning post), except for the last 3 posts as they are with a new save, and the last one is with the persia dlc turned off and new save.

The game will crash just randomly as I play and when i look into the err log it is always caused by some event being triggered and missing something thus throwing a exception and CTD

 

[AndrewT]

Well, the error log often has cosmetic errors in it, they may or may not actually be the trigger for your crash.

I ran your 'last_save.ck3 hands-off for 5 game years with no crashes, despite there being many errors like this in my log

[13:27:30][jomini_script_system.cpp:276]: Script system error!
Error: Event target link 'compare_value' returned an unset scope
Script location: file: events/dlc/bp2/bp2_yearly_1_events.txt line: 6535

So the cause is elsewhere, it seems.

"setting_framerate_cap"={
version=0
value="off"
}

Right click on ck3.exe , properties, compatibility. Tick "disable fullScreen optimisations" untick every other box in that dialog, Apply and exit.
Then in the launcher Game Settings menu, select fullScreen display mode, Vsync off, cap refresh rate at 60.


If those don't help:
DXDIAG is a program you run from the Windows search box on the task bar. After running it will open a window and start collecting info with a progress bar in the lower-left corner. When it completes click the 'save all information' button and save it to a file then attach that file here.

Please attach here your Documents/Paradox Interactive/CK3/pdx_settings.txt .
From your Documents/Paradox Interactive/CK3/logs/ folder, attach here system.log , error.log , exceptions.log

 

[JayJJoker]

Hey so i didnt find 'cap refresh rate' so I assume you are talking about cap FPS? I did that and the game did run smooth for about an hour of play but then it did crash in the end. The attached system and err logs are attached, but i do not have a excpetions.log in that folder. Also system.log looks to be empty.

This is a screenshot of all the files in Documents/Paradox Interactive/CK3/logs

I have also attached the DxDiag.txt and pdx_settings as requested

 

[JayJJoker]

I know you didnt ask for these, but attached are all the files from the latest crash in Documents\Paradox Interactive\Crusader Kings III\crashes\ck3_20231210_135949

 

[AndrewT]

Hey so i didnt find 'cap refresh rate' so I assume you are talking about cap FPS?

When in the launcher Game Settings menu you disable Vsync, you get a Refresh Rate option (which does indeed set a line in the pdx_settings.txt file called setting_framerate_cap). Please set that to 60.

Assuming that doesn't help, you probably have the bios/CPU issue described here:

Victoria 3 | 12th/13th/14th Generation Intel Processors

Hello all! An update, 12th and 13th Generation Intel Processors are related to a Crash to Desktop (CTD) happening frequently, this is related to architecture changes by Intel and specifically E-cores. We are working with Intel to address these...

forum.paradoxplaza.com

Please try that out!