Crash - During Play
Crashed 3 times in a row trying to load damnation maelstrom (scab faction, extra specials, mostly melee). I’ll try a different mission, but it’s the first time i encounter this problem.
No, I don’t use mods
Constant (100%)
Steam (PC)
Crashed joining a different mission too. Earlier I was able to play a low intensity one.
Could you try this below, please?
user_settings.configray_tracing = true to ray_tracing = falseI can still open the game to check it otherwise.
Opening the config file i see no such line: I see a couple of ray_tracing_quality = “off”
Checking the option ingame it showed N/A, I set it on off, but I see no difference.
Further down in the config file I have this:
rt_checkerboard_reflections = false
rt_light_quality = “high”
rt_mixed_reflections = false
rt_particle_reflections_enabled = false
rt_reflections_enabled = false
rt_shadow_ray_multiplier = 2
rt_transparent_reflections_enabled = false
rtxgi_enabled = false
rtxgi_scale = 0.5
put ray_tracing = true directly in the top section of the .config file so it’s parsed correctly. Meaning the option you see is not the correct option to change to fix your issue.
This option will tell your game you dont have ray tracing support so we dont load anything related to that. The options you see is related to the ingame menu.
This options is not exposed by default, it’s for users such as you that have this issue. Of some reason it takes too long time for you creating pipeline state objects (PSO)
when this option is enabled you wont have any ray tracing options available in the menu ingame.
ok so the very top of the file.
shouldn’t I set it to false?
yes, set to false is correct 
Please remind me, should I set it to read only? otherwise the game will overwrite my changes. Is it going to be a problem for future updates?
i think the game respects new entries without overwriting them. Not sure since I don’t work with that work. So I dont think you need to make it read only.
But if this doesn’t work for you we can also override it by doing same thing in game files → win_settings.ini. But since you dont really want to modify game files this is prefered.
During my tests the game didnt overwrite this value.
another note, since we dont set the file to read only you could encounter other issues doing that.
ok, so, I needed to set it to write only. I have vague memories of an update changing the config anyway.
should i change the win_settings.ini instead?
If you are interested, I think the problem might be with the updated drivers for my video card (AMD radeon rx 6600), version 24.1.1
hopefully i’ll be fine in the future. adding that line to the config seems to have worked for now 
thanks
Sadly I just had a crash on mission launch again, even with this modification 
i dont think you should modify the write read rights at all
can you still see ray_tracing = false in your config file? you can upload if you are unsure. But note it should not be inside any other object since we assume it is in the root level. The log has still logs about ray tracing.
If you cant see ray tracing it could be launcher or game that overwrites the file. You could try launch the game from the exe to work around the launcher
I downgraded my video card drivers and the game is working again.
So the problem is there somewhere I guess.
yes, so its quite clear the issue is that creating ray tracing shaders takes too much time. We have communicated this with AMD but they have not been able to repro it and it seems to only affect a few ppl. Could be a combo of windows installation, drivers and potentially other stuff.
We can potentially handle that in the future but regardless that will cause longer loading times and I assume we rarely have stalls longer than a second and this is a 15 second stall.
note that i neither work on launcher or ingame settings and thus not sure if they overwrite the settings, but this worked when i was testing it locally because i added this setting just for this reason that we have seen more players with this issue.
So hopefully they might take care of it.
Just in case I need to try this solution again, your suggestion was adding the line and launching the game through the executable, right?
i’ve been testing setting
ray_tracing = false
from appdata user config in the steam app using the launcher. And from my side this works how I expect it. Ray tracing settings are gone from ingame menus.
Ive changed settings from both launcher and ingame and this setting remains in my .config file. So strange that this doesnt work for you.
When launching directly from .exe that would be a workaround if the launcher would overwrite this setting. But it wouldnt help if it’s the ingame logic that removes it. Also skipping launcher means no crashes will be uploaded.
Let me know if you still have issues settinng the user config value.
C:\Users\<user name>\AppData\Roaming\Fatshark\Darktide\user_settings.config
This is the file I have modified to be clear
Thanks, I will. For now the downgrade of my video drivers seems to have bypassed the problem. I’ll try their next major update and see how it goes then.