Do you have any other console logs, or ideally a crash report, that you could upload here please?
Do you have any other console logs, or ideally a crash report, that you could upload here please?
Could you screenshot your audio settings in Darktide for me please?
@Haphazard, your issue is the result of a DRM interfering with Darktide. Fasoo DRM?
For anybody else here other than the OP, please create a new post instead. Your issues are a bit more complicated and it’s not suitable to deal with them all in the same post as it causes confusion.
This is unfortunately a nondescript GPU-related crash. There might be some alternate solutions in the link below that can help:
Read moreCould you make sure your GPU drivers are up-to-date please?
Purely the level, I have no way of copying anything else over.
Our Backend Engineer is aware and looking in to this issue, but for players with long loading times, we recommend changing the DNS. This can be done via General Settings → Network Settings → Advanced Settings → DNS Settings - ‘Manual’
The DNS you decide to change to is up to you - there are multiple DNS providers available, such as Google DNS, Cloudflare, and so on. This is purely personal preference.
That’s what we like to hear! Let us know if you run in to any other problems.
Are there any restrictions on your account? The below instructions might help, also have a look in that same list to see if there’s anything else that might be impacting it.
It looks like a DRM is interfering with Darktide here. Possibly Fasoo Enterprise DRM?
Please disable the Overwolf overlay.
Thank you for sharing your solution here!
No problem, I have restored the weapon for you.
Hello! Did you purchase the launch bundle, as opposed to the standalone Imperial Edition?
This is a known crash and will be addressed in one of our upcoming patches, apologies.
Please see:
Read moreThank you for your darktide_launcher.log. Do you also have any console logs, please?
Read moreI’ve had to share this to our database for investigation. I apologise I don’t have any immediate solutions, but I hope we can address this soon.
Is this still occurring for you after restarting?
This is a known issue and will be patched soon. Sorry about this!