FatsharkPdr

FatsharkPdr


29 Mar

Comment

If you haven’t already, could you try to wipe your %Appdata%/roaming/Fatshark/Darktide folder from .hans and .pso_lib files, also clear your windows Shader cache. (Using Disk Cleanup tool)

image554×683 27.4 KB

Just to make sure your issues aren’t stemming from cached broken shaders somehow.


28 Mar


04 Mar

Comment

Hi Solun. You are on a very old driver (dec 2022), and something seems to go wrong with the shader cache for you. I would suggest that you firstly update your driver and then erase everything in C:\Users\AppData\Roaming\Fatshark\Darktide. Or if you want to keep your settings, only erase the files ending with .pso_lib and .hans. Then run the game again.


27 Feb

Comment

Sorry to hear that Moto. But if it’s not too much to ask, please try this current experimental as well. You are one of the unlucky ones who seem to crash all the time, it would be valuable if you could try and se if you still crash on this build. (experimental). It looks like you’ve only played on the main branch according to the one crash that is reported to our system from your steam user name.


26 Feb

Comment

Have you tried the experimental branch? Beta password: cTYPtKTsfMDsLHAV


25 Feb

Comment

A new build has been deployed. This build will require more VRAM the longer you are playing. So if you experience crashes do to Out of memory consider lowering texture quality or resolution.


24 Feb

Comment

New experimental deployed, restart Steam to get it. Portraits disabled as that seems to have helped a lot before, plus a new experiment.


21 Feb

Comment

Yes. I did a small update to the experimental yesterday. I will do another today.


10 Feb

Comment

New experimental deployed. Please update and try.


08 Feb

Comment

So, I think it’s hard to explain exactly why this is the way it is, and that’s partly because the cold truth is that we don’t know yet. What we do know is that it’s something that has to do with our instancing and instanced skinning system. (Instancing being drawing multiple copies of the same mesh at different places faster than it would be drawing them one by one, Skinning being transforming vertices of a mesh to a set of of ‘bones’ to make the mesh move around, end of graphics programming crash course :slight_smile: )

We also know that whatever is causing the issue must be a product of some pesky “race condition”, which means that occasionally when you are processing stuff on many threads and processors at the same time, things can come out of expected order. It’s like finding a neele in a haystack, it’s probably something super-dumb,...

Read more

07 Feb

Comment

experimental should be back and working with the latest content patch. I missed one commit when cleaning out on the experimental branch. I was hard-capping worker threads to 10 in the engine, this is no longer the case. But you can emulate this behaviour using the launcher if needed.


04 Feb

Comment

New build deployed where only portraits are disabled. Weapons and cosmetics should be back on this one.

Comment

The current experimental have no portraits. It’s part of the experiment. I should have probably mentioned this. But this is the nature of the experimental build. I experiment and see what works. Since this GPU hang can’t be reliably reproduced in a controlled environment I need to go wide and block out parts of the engine which we suspect. Currently it has lead us to the portrait rendering system and I want to verify that it helps by disabling this system completely. Currently only one part of it is disabled, which is why I still can see some hangs comming in. But I’m planning on disabling the other part as well and see if that does it. Then we know where to dig in and figure out what is going wrong.


03 Feb

Comment

Also please hop over to the experimental branch! This is a rare one, and there’s a lot of new debugging info added to shine more light on the issue when this happens.

Beta password: cTYPtKTsfMDsLHAV


28 Jan

Comment

New experimental update is available. Fingers crossed.

Password: cTYPtKTsfMDsLHAV


26 Dec

Comment

I probably should elaborate. This is why we try to not say too much, as it’s always being misinterpreted to a degree. It’s not useless to post logs and dumps for most issues. It’s useless for GPU hangs in particular, for us developers.

Our community managers are not developers, but they know how to categorize crashes based on quickly looking at the logs, so to them it’s not useless in terms of giving accurate response and referring to possible known workarounds.

Another aspect of posting logs and dumps it that ...

Read more
Comment

Please don’t. Everytime this prompt goes up, an automatic crash report is sent to our systems along with all logs and dumps. This helps us keep track of what crashes are most critical to prioritise. If a large enough player base does this, our systems will say that everything looks good.

On that note, it’s entirely useless to post dumps and logs here, we already get all that informtaion in our system. All you need to post, if you want special assistance with ...

Read more

23 Dec

Comment

Hi.

I have another thing you are welcome to try, and get back to me with wether it does any difference or not. It is to disable the mesh streamer, this will cause the game to require much more VRAM than usual, so if you have low VRAM (6Gb or so) this might not work for you.

Anyway, to disable the mesh streamer, browse to the games steam files.
Locate the file settings_common.ini in the folder bundle\application_settings
In that file, locate the section that says: mesh_streamer_settings = { … }
and change the “disable = false” to “disable = true” and save the file.

while you’re at it, or rather, if the mesh streamer hack doesn’t do anything for you, you can also try to disable the multi threaded texture streamer by changing the value
threaded_streamer = true to threaded_streamer = false in the section called feedback_streamer_settings = { … }

Disabling the threaded texture streamer will most likely degrade your performance slightly. Jus...

Read more
Comment

Hi.

Have you tried to turn off DLSS, change to FSR1 or FSR2, or switched around with those settings? Just trying to see if anything in particular other than the “low”, “medium” and “high” presets could affect this.

This is very weird, but as a matter of fact, there is something you could do in order to help troubleshoot this issue. It is a bit involved, I wont lie. You would need to download pix for windows (Download - PIX on Windows). Then enable Pix to be attached to the running instance of the game by editing a settings file in the game. To do this, browse to the “Local Files” for the game, there’s a short ...

Read more