FatsharkJulia

Thank you for your report, I’ve raised this to our database!

Are there any remaining solutions on that list you haven’t tried? They are the only known solutions we have for these particular corruption errors unfortunately - any time a new solution is uncovered, we add it to the list.

I understand this is disappointing if you’ve exhausted everything already. I can assist with a refund alternatively.

Hello! Are your RAM speeds consistent?

I’ve sent you a DM!

Would you be able to upload your most recent console logs, please? I will query this with our developers, or alternatively, I’m happy to help with a refund.

No problem - I’ve refunded the purchase for you.

Thank you for sharing! I’ve raised this to our database.

I have queried this with our developers, and I will report back to you as soon as I’ve received a response. Sorry about this.

Please check the Windows Event Viewer - are there any errors that correspond with when this occurs?

1. Press the Windows key
2. Conduct a search for ‘Event Viewer’ and select the app
3. In the sidebar, expand the ‘Windows Logs’ dropdown
4. Select ‘System’
5. Search for errors that correspond with Darktide losing responsiveness

Sorry about this, it’s my understanding the original colouring was unintended, and was later patched to be the intended colour. I understand this is disappointing if you liked the original colour more.

Would you like me to refund the purchase?

Oh, if there’s no integrated GPU, no need. I’m not sure why else it would be having an issue with monitor detection - I’ll have a think on this.

My apologies for missing your reply. This is a really complicated one, as much of the crash data is missing, so it is a shot in the dark. I can continue to press this with our developers, or alternatively I can help with a refund?

It is a shot in the dark, but back to the monitor theory - are they for sure connected to your dedicated, as opposed to your integrated GPU ports?

I’ve responded to your DM.

We are working on hotfixing various issues concerning the description of Blessings.

Existing reports may be merged here, to help us keep track of the issues being reported.

Unfortunately it’s not possible, as the backend used for Darktide is not the same as what we use for Vermintide 2. There is no option available to us in Support to delete or reset the account at this time. It’s possible this option will be available to us at a later date, but I’m unable to provide an estimation as to when. Sorry about this!

Due to an increase of players reporting failed_found_no_lobby / Error Code: 3013, I have chosen to merge all related posts here. This makes it easier for our Backend Engineers to parse multiple reports at once.

Work continues on this particular error, and I will post any relevant updates in the comments below. I will include links to any updates here.

For any new reports pertaining to this error, please help us out by including the information listed below in your report:

Issue Description:

Crash Report (If Applicable):
[Please see instructions on how to provide a crash report in the pinned Topic]

Steps to Reproduce:
[Please add the steps that can help our QA department in reproducing the issue. For example:]

1. Play Chasm Logistratum as Ogryn (Skullbreaker)
2. Attempt to pick up the second Grimoire
3. Observe Backend Error

My cat does that all the time! We won’t be able to restore the character in its entirety, but I can look at levelling up a new one for you. Please could you contact us over at https://fatshark.se/support?

Your suspicion with it being related to WebView2 is correct! We are working on updating the SDK, which should resolve the issue for you.

Edit: In the mean time, you should be able to workaround this by deleting the the entire WebView2 directory in Steam\steamapps\common\Warhammer 40,000 DARKTIDE\launcher

This is a bit of a mysterious issue admittedly, and I understand you’ve exhausted many solutions already. I’ve shared this with our Launcher Developers, and I hope to have some more information soon.