Launcher options not appearing on Linux?

Issue Type (Required):

Launcher

Issue Description (Required):

Using whatever version of proton, the launcher doesn’t have any of the fancy buttons and more importantly, it doesn’t have the “Options” one. I’m still figuring out if the user_config works for the number of worker threads (which it doesn’t seem like from my testings) because I can’t change it in the launcher, since the button isn’t present.
Is it normal ? Is there a way to overcome this issue ? I can’t find anything on the forum or the steam one, I just wanted other people inputs concerning this.
I’m using proton 9.0-1 since I cannot interact with the launcher using proton experimental.
Have a good day!

[PC] Do You Use Mods? (Optional):

Yes, and I’ve tried disabling them

Reproduction Rate (Required):

Constant (100%)

Platform (Required):

Steam (PC)

Player ID (Optional):

[PC] Crash Report (Optional):

  1. Launch the game using any version of proton.
  2. Launcher doesn’t have the “option” button or anything else than “Play”

Upload Supporting Evidence (Optional):

Regrettably we aren’t able to provide support for Linux users but there is a small community here that may be able to help.

This post may be of interest to you:

1 Like

Thank you for your answer! I can still play the game so no problem!
So this is normal behavior right?
Is there any way to turn the worker threads option down/up without this button since there are no settings in game for it? At least a kind of documentation on the user_settings file? (because I don’t know if the modifications I made work or not)

Once again thanks for the heads up, I will take a look!

Just wanted to chime in here. I as well have this issue, but it has not really been a problem as the game launches. However, for some reason I am now experiencing an issue after clicking play in the launcher. The shader cache process fails, an error message appears saying “loading dialog is not responding” and I have to force quit. Usually it works fine, but something has changed since patch 37 or maybe a kernel update around the same time. There have been times where it fails 3 or 4 times in a row before the shader cache process works and the game launches. Picture for reference.

Screenshot from 2024-05-17 13-42-33

I haven’t played since last Thursday and didn’t have any issues back then. I’ll take a look tonight, did you try playing with different Proton versions ? I have had issues in the past where I couldn’t get past the shader building when using experimental so it might be worth a shot!

I have tried it on every version of Proton available in Steam and this happens on every version of Proton that will run the launcher. After pressing play, there is a 50/50 shot of shader cache running successfully, but I had it fail 8 times in a row yesterday which was particularly frustrating lol, however it worked on the 9th try. I am using kernel 5.15.0-107 if that is worth mentioning. I am a beginner to linux, hence Mint distro, so I am not too knowledgeable of all this.

I never had the options menu either. I concur it’s not a problem for me either.

As for the crash during shader compilation, do you have more details on your system? The recent kernels seems to have touched some part of the AMD GPU driver, which has a noticeable effect on Darktide (good or bad).

For reference, the main changes in 6.9 is the addition of AMD P-state preferred core support.

Here are the commits:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f3a052391822b772b4e27f2594526cf1eb103cab
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a004e1fee4ba3d37976c1a9707869acc8d60b55
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dfddf34a3f0d45483f5b3e46c2e7bda173796f1b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e571a5e2068ef57945fcd5d0fb950f8f96da6dc8

It can be disabled via a kernel parameter (see 3rd link).

Hey, thanks for your help.

I am using Intel/Nvidia set up so I don’t think I am affected by AMD issues, I think. The kernel I am using says it’s supported until April 2027.

My system details:

image

Well, since you’re using a distro, kernel upgrades are out of your control.

Best advice I can give you is to make sure you’re up-to-date on packages and proprietary drivers.

Sorry, new to linux so I am not sure if I am understanding what you mean when you specifically say “upgrading” the kernel. I can choose from many different kernels in the update manager. I am just using the one that says it’s supported as all the others are labeled superseded or end of life except for 6.5.0-35. I can play the game so it’s not really a big deal, this is more educational for me as I learn more and more about linux and put stuff together.

Sure.

So, Linux is a free and open source operating system kernel, which means that anyone can contribute to its code. In practice, most hardware companies contribute driver code for their products, which has several benefits for them. The biggest one is that because their drivers are already included in the operating system, they don’t have to distribute them and users don’t have to install them.

For example, AMD and Intel have contributed the source code for all their GPUs. So if you use Linux, you know those will work flawlessly out of the box without having to download and install anything.

There are also companies who refuse to contribute and prefer to force users to download and install drivers. For example, Nvidia sells high-end and low-end GPUs that are actually the same hardware underneath, and it’s the driver that decides how many cores are turned on. Of course, that kind of market segmentation scheme would not work if users had access to the driver’s source code, as they could buy the low-end GPU, flip a bit, and then get the high-end performances.

That being said, the point is that as a Linux user, all you need to do is upgrade your kernel to get drivers improvements and support for more hardware.

Now, there is a new version of Linux released every 10 weeks or so, and you are expected to update to the latest if you want to get those bug-fixes, new features and performance improvements. However, some versions are marked as “long-term support” and will only get bug-fixes back-ported for some time (typically 2 years, sometimes more).

Finally getting to the Linux distribution question. It’s worth nothing that some of them prefer to use “long-term support” kernels, such as Linux Mint, while others are so-called “rolling releases” and always offer the latest kernel, such as Arch Linux used by the Steam Deck. It’s a matter of taste which one people use. Some want the latest and greatest while others say that if it ain’t broke don’t fix it. Your choice.

1 Like

Did you ever played around with worker threads in that case? I tried using the config file in compdata but it doesn’t seem to affect the behavior in game in my case… At least I’m not sure

EDIT: Also +1 for the kernel updates. Had an issue yesterday where the game ran like ass and Elden Ring crashed on load. My updates were locked behind a package requirement for the last two weeks… Updated everything and it seemed to work better now

Can you tell me the file location for the launcher settings? I would like to try changing the worker threads. On win10, this fixed a bunch of crash issues for me. I just can’t figure out where the file that has this setting is.

In my /.steam/debian-installation/steamapps/compatdata/1361210/config_info there is no visible setting for worker threads.

Edit: I think I might have found it here: /home/username/.steam/debian-installation/steamapps/compatdata/1361210/pfx/drive_c/users/steamuser/Application Data/Fatshark/Darktide/user_settings.config

Within this file, there is a threads line that is empty like so

image

Maybe that is it?

2nd edit:

Before you try this, please note this will reset all your settings for graphics, keybinds, mods, mod keybinds etc.

Did some experimenting and found what is so far a solution or atleast working much better now. In the user_settings.config, I added the following to the appropriate alphabetical location(I initially tried adding to the end, but this would cause the settings to be reset every time you launch the game instead of just the first time after the edit):

max_worker_threads = 6
launcher_verification_passed = true

So it should look similar to this:

launcher_overrides = {
}
launcher_verification_passed = true
master_render_settings = {
ambient_occlusion_quality = “low”
dlss = 4
dlss_master = “on”
dof_quality = “off”
gi_quality = “low”
graphics_quality = “custom”
lens_flare_quality = “sun_light_only”
light_quality = “medium”
ssr_quality = “medium”
texture_quality = “high”
volumetric_fog_quality = “medium”
}
max_worker_threads = 6
mesh_streamer_settings = {
}

I did this because in the darktide_launcher.log, I was getting these errors:

[Launcher] [Main Window] Could not find setting ‘max_worker_threads’, using default value ‘13’
[Launcher] [Main Window] Could not find setting ‘launcher_verification_passed’, using default value ‘False’

I used 6 threads for the worker threads setting because I have an 8 core processor and put true for verification because it was defaulting to false.

1 Like

No, I’ve tweaked with the settings in early 2023 and bricked the game. Since them I’ve stayed away and used the default.

It’s not as pretty as it could be, but at least it works.

First of all thank you for your research!

That was driving me crazy, I noticed after modifying the settings file that it was somehow taken into account (when I edited my settings in game it would modify the file but since there is no way to check how many worker threads are enabled in game it was a pain…) but I never tried neither with “launcher_overrides” nor “launcher_verification_passed”.

I will try your solution tonight, also I wasn’t even aware of the presence of the launcher log I feel stupid…

I really want to tinker with that since on windows the game would set the value to 32 threads and tank the performance, setting it to 14-16 increased my fps and the general stability.

EDIT: I tried both with the “max_worker_threads” option set to 14 and without it, seems like both yield the same performances (at least in the meat grinder)… I don’t know if the game acknowledges this setting or if it is just not changing the perfs that much. I’ll do some further testings later this week while monitoring threads stress I guess.

1 Like