• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

TheGaminThomas

Recruit
Jun 11, 2021
4
1
[16:05:54][E][jomini_script_system.cpp:284]: Script system error!
Error: global_variable_list_size trigger [ Could not find list from read name flag laamps_tally ]
Script location: file: common/scripted_triggers/00_laamp_triggers.txt line: 877 (laamp_youth_cultural_tradition_trigger)
file: common/on_action/childhood_on_actions.txt line: 291 (on_16th_birthday)

Hi I had problems with my game crashing and submitted a request and they said that this was an unusual error and that i should submit it here for further assistance.
 
I suspect they meant you to post in Bug Reports - we here in tech support are not experts on gameplay or system scripts.

Is this just happening in one particular campaign? Any mods involved?
 
I see. However just because you see an error in that log doesn't mean it is causing your crashes; there are often (indeed almost universally) cosmetic errors shown there that cause no game problem.

Have these crashes always happened since you've had the game, or is used to be okay up to some point?

After a crash can you load up the save and carry on past that crash point, or it always crashes at that same time, event or action in the game?



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.
IF dxdiag.txt fails to attach here, rename it to dxdiag.log , or zip it up.

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.txt
 
I see. However just because you see an error in that log doesn't mean it is causing your crashes; there are often (indeed almost universally) cosmetic errors shown there that cause no game problem.

Have these crashes always happened since you've had the game, or is used to be okay up to some point?

After a crash can you load up the save and carry on past that crash point, or it always crashes at that same time, event or action in the game?



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.
IF dxdiag.txt fails to attach here, rename it to dxdiag.log , or zip it up.

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.txt
Hi I found out the issue was due to my RAM and the game would crash whenever big wars or other highly intensive events would happen. Thanks for your help.
 
  • 1Like
Reactions: