[2023] Crusader Kings 3 fails to load [Linux]

The only supported distro for our games is Ubuntu, so there may be limits on how much we can help you here.

Has this game ever worked on this machine?

CK2 is free to play on Steam now - does it have the same problem?

When you say there are no logs - there must be log and text files in /home/user/.paradoxinteractive/Crusader\ Kings\ III/ and in the /logs/ folder under that?


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

TuxedoPenguin79 said: CK2 does not have the same issue, it did fail to launch, however all I had to do was replace a single file.

That shouldn't be necessary - what file was that? And how did you know to do that?

TuxedoPenguin79 said: I found the .paradoxinteractive folder, however there was no CK3 folder, only a CK2 one, despite the fact i've played other Paradox games on this machine.

Hmm, not sure what to make of that. What exact games were they? Non-PDS games from us don't all use those folders.

Can you switch between Wayland and X11, as a test?

Aside that than, system memory is a bit low at under 6gb - unload every other app you can before starting the game.  

Oh, are you using Proton, not the native Linux editions of these games (all except Vic2 have that)? If so that explains the lack of log files!

Can you try the native Linux editions please?  

TuxedoPenguin79 said: The file was libtbb.so.2 I was having issues launching it, so I checked ProtonDB, and replacing the file was recommended as a fix, so I tried it out, surely enough, it worked,

You just needed an updated version? That would be odd for a game that hasn't been updated for some years!



When you run ./ck3 from the terminal, what output do you get there?  

I am sory, I have no idea what is wrong on this Linux installation to cause this to you. Without any game log files we see no clues anywhere as to even the general area of the problem.

Is there anything of use in the Linux system logs perhaps, that record what is happening as the game attempts to start up?  

Well, we don't support the Deck either, so ... ! Yet, anyway.  

Can you get any technical help from Arch or Garuda sources ? There surely must be Linux logs somewhere that record what happens when ck3 tries to start and fails!  

TuxedoPenguin79 said: Do you have any idea of why the terminal isn't picking up logs on why it crashes, or why the log files aren't being created?

I do not, I'm sorry! My Linuix knowledge is pretty rusty by now, I haven't supported it as an OS for nearly 10 years by this point.

TuxedoPenguin79 said: The best thing I can think to do is to try and launch CK3 with Wine (or Proton), and open up the "virtual system" files to see if there are any logs created there.

Well sure, but that only uses Windows facilities, so any problems seen then are likely to be very different! It may be the only way forward for you here though.  

TuxedoPenguin79 said: That explains a bit. I'm honestly quite surprised, if you have an old spare machine i'd recommend slapping Linux on it to help with support, or just run a Linux distro through a virtual machine.

I do run a VM with Ubuntu 22.04 on it, but that's not going to help you with your problem on Arch. The game loads up fine on it, although the virtual video system is not good enough to actually play.

TuxedoPenguin79 said: Good news! Despite there being like, 7 Paradox interactive folders, all in different locations, there was one in Documents that actually contained logs, which ones do you need to diagnose the issue?

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

And the contents of the latest crash folder that may be there.