Axloss

I’ve now confirmed that the input seems to work with reWASD if I’m using mute.

Meaning I mapped WASD on the left thumbstick and then muted them as well.

Otherwise the game will get both gamepad and keyboard input and will not know how to handle that.

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\\AppData\Roaming\Fatshark\Darktide\user_settings.config

This is the file I have modified to be clear

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.

if you still are interested of having a fix for this, please upload if there is a specific rewasd config we should try out.

Note I have never used rewasd. I will try reach out to them as well to see how this should work from their perspective.

Sorry for late reply.

I believe the issue is due to game believes we have more than one input (M/KB + Gamepad) and we switch which one to listen to all the time due to this.

I will see if we can make a fix.

hey, i’ve not followed the whole thread but this issue is due to some driver issue making creation of ray tracing shaders slower than it should.

Im not familiar how common this is for Intel but for AMD i know this affects a few.

you can turn off ray tracing using

ray_tracing = false in your user config (found in appdata)

or modifying the game file
application_settings\win32_settings.ini
same thing there, set ray_tracing = false

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.

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

another note, since we dont set the file to read only you could encounter other issues doing that.

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.

yes, set to false is correct

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.

could be unrelated to the changes, I tried this on my PC with locked 60 fps. What this flag does is that it moves the reads of streamed audio to the game thread which in theory is bad. If you are on a fast SSD it might not be that slow, but on a HDD it might cause alot of issues.

Are you running the game on a SSD? (our log tells me that you do).

Could there be issues with said drive? Perhaps try move the game to another disc if possible since the original issue could be due to this.

My guess is that your perf issues might be related to the original issue.

Seems like your latest crash is related to use_engine_thread. Note that we never changed these values, we are only testing this to see if any of them resolves your issue.

I would start with testing use_bank_thread as false and then use_blocking_io.

Try combos with of them. Meaning one false and the other one true and vice versa. Let us know if any combo resolves your issue.

i think you can actually add
ray_tracing = false

in your user config in appdata (I added support for that in last patch I think) so you dont need to change the game files for this to work. We currently have not exposed this in any menu since it would be quite confusing since this is more like acting that your GPU doesn’t have ray tracing support at all.

However we need to make another patch to get more metadata for the users getting this crash. It’s currently quite rare but you are a few.

you can also try disable ray tracing completly since i see some signs that could be an issue and we have a few other amd users having same issue.

The time of generating the ray tracing shaders take a bit too much time and accumulate to the deadlock threshold.

in game files, lookup this file win32_settings.ini and change value of ray_tracing to false

edit: try this before disabling the deadlock detector. We have added some extra metadata to try find the cause of this issue but we have not yet patched that due to xmas.

try disable the deadlock detector and see if you can continue into the game.

I will consider increasing the time out. Or look into if we can see if we do a “update” to tell the game that we have not deadlocked yet.

Nvidia couldn’t see any reason why it get stuck either. You could see if removing the check makes the game continue instead of crashing. In this case you timeout due to the engine being stuck here for 2 min.

in game files, lookup this file win32_settings.ini and change value of deadlock_detector_enabled to false

I was able to launch the game somewhat consistently by reinstalling my graphics drivers (Nvidia) before launching the game, after which the game would run almost perfectly. However, I would ...

FYI in your case the game is stuck in ntmarta.dll never seen that one before.

edit: after further inspection it looks like its’ stuck in a sl dll. I will send this to Nvidia and ask if they can see anything