Crusader Kings 3, Linux Version, Crash on save. (Arch Linux) [WORKAROUND FOUND]

[NikolajRC]

This problem has not been solved, but I have found a workaround: (Use Steam-Proton to run the Windows version instead), If you are experiencing the same problem on Arch Linux, or any other not officially supported distro see my post below.

Original problem
==========
The Linux version of CK3 has an annoying tendency to randomly crash during saves, be they auto-saves or manual saves. I do not really notice a significant drop-off in performance prior to the crash.

The game does not actually quit, but it does become irresponsive and keeps looping the last few seconds of sound (I have tried just leaving it in this state overnight, it does not become unstuck)

This crash does cause a save-file to be made, which at least shows up as the most recent save in the launcher, but the resulting file is corrupted and can not be loaded (This obviously breaks Ironman, unless I manually back up the saves, but that kind of defeats the whole point)

It does not crash every time it saves, most of the time the saves made work perfectly, I can normally on average play for around 1 to 2 hours until an autosave causes a Crash, so I guess this acts as some sort of impromptu play-session length timer.

To be fair, I am playing the steam release on Arch Linux, and not Ubuntu/Debian, which I doubt the game was even tested on (The steam package provided for Arch Linux, through the pacman package manager (I would include a link to the official Archwiki page for this package, but the forum did not allow me to do that).

Other Paradox titles like CK2 and EU4 work fine on the same computer.

Has anybody else experienced this? Does anybody know what could cause this, and is there any way to fix it/reduce the risk of crashing.

Some more information
--------------
My linux kernel version 5.18.14-arch1-1
I have 8 GB ram and well in excess of 1 TB left, so I am not running out of space

My saves are also stored in my home folder (~/.local/share/Paradox\ Interactive/Crusader\ Kings\ III/save\ games/) . So I don't have any permission issues

I use the latest version of the game on Steam (1.6.1.2)

I can not get the game to print any crash reports or information while running, I have tried running steam from the commandline, but that does not print any information from the game.

(Update) I also tried running the game directly from the commandline without steam, but it does not print anything about the crash

 

[TinyWiking]

To be fair, I am playing the steam release on Arch Linux, and not Ubuntu/Debian, which I doubt the game was even tested on

This is most likely the problem as the game was built for Ubuntu. It hasn't been tested on other Linux builds and since you're using a build we don't support there's not really anything we can do for you. That being said we do have quite a few Linux wizards in the community so there may be someone in the same boat as you that has solved it somehow and is willing to share the workaround.

 

[NikolajRC]

This is most likely the problem as the game was built for Ubuntu. It hasn't been tested on other Linux builds and since you're using a build we don't support there's not really anything we can do for you. That being said we do have quite a few Linux wizards in the community so there may be someone in the same boat as you that has solved it somehow and is willing to share the workaround.

I expected as much, I am still hoping someone else already have a workaround other than installing Ubuntu or Windows in a dual boot or VirtualBox.

 

[AndrewT]

Crashes that happen after some hours' play (in any game on any OS) are usually overheating, but I can't see why that would only happen on save operations. You could check the CPU and GPU temps after say 1 hour of play though.

 

[NikolajRC]

Ok, so I found a workaround: Just play the Windows version instead; this can be done by using a compatibility layer, the best of which is Valve's Steam-Proton.

This was a solution I had originally shied away from because I remember the old Wine Compatibility layer being difficult and annoying to set up.

But Steam-Proton can be set up directly from the steam app; and allows you to download and run the Windows version, which appears to be much more stable, and as an added bonus, now all mods I have tried appear to be working. Even though the compatibility layer technically introduces some delays, I have not noticed any increased lag -- I guess the windows version may have been more optimized in the first place, or maybe modern computers are just so good that it does not matter.

In my case I did not need to change any launch parameters from the default.

If anyone else is having problems with the Linux version (crashing or any other issues), I strongly recommend trying with Proton enabled, this article from How To Geek explains how (Does require uninstalling and reinstalling the game) https://www.howtogeek.com/738967/how-to-use-steams-proton-to-play-windows-games-on-linux/