[2022] After 1-2 hours of play, the game will suddenly slow down and freeze(Linux)

So this never happens while actively playing? Because that makes it sound like some sort of hibernation thing ...


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

Also in Steam please click on Steam-Help-System Info, and paste everything there into a text file and attach that here.  

That error log looks pretty bad! And there are some incompatible mods in use apparently?

I can't open that PDF file for some reason.


Please do a full **clean** re-install:

- move any valued save games elsewhere
- "uninstall" in Steam-CK3
- unsubscribe from ALL mods in the Steam Workshop for this game

- manually delete both the Steam/SteamApps/common/CK3 AND Documents/Paradox Interactive/CK3 folders
In particular make sure there are no files or folders left under either the Steam CK3 or Documents CK3 locations, before installing again.

- re-install game in Steam, run a Steam Verify when done.
- start the game with no mods active and test with a new campaign, NOT any existing one.

Is it any better then?  

Presumably the endless repeats of this are causing your problem:

20:22:04][jomini_script_system.cpp:209]: Script system error!
Error: Failed to fetch variable for 'ep1_03_achievement_unlocked' due to not being set
Script location: file: common/achievements/ep1_achievements.txt line: 40

I don't see that on vanilla CK3 in Windows or Mac ... are we sure everything in both the Stea-CK3 and Documents-CK3 folders before installing again?  

Best to delete those old saves then.

You will not of course be the only person not having Royal Court, yet I have not seen that script error reported by other users. Yet I have to say it looks like a bug of some sort ... unfortunately my Ubuntu installation is a VM so I can start but not actually play this game to see if I get them too.

This has only happened since 1.5.1.1, is that right? Older versions don't do this to you?  

As this point I can only assume this is a bug, either in the Linux build overall or only when run on an unsupported OS. I don't suppose you'd consider moving to Ubuntu?

If not, I'm frankly not sure what to suggest as we can't escalate the issue as is. Can you play on 1.5.1 and see if the next patch resolves this issue for you?