Warhammer: Darktide Dev Tracker

Devoted Rejects,

Here are the notes for Hotfix 1.1.22 which just went live on Steam, and will be out shortly on the Microsoft Store.

• +X Stamina perks now give incrementally higher bonuses (+1 / +1.25 / +1.5 / +2).
• Refining “+% Curio Chance as mission reward” perk should no longer display an error.
• Minor fixes for various cosmetics items.

ok, we are also not planning to make them redundant

There are no plans to roll back any of the items players have got through this bug - but just as a heads up it will be fixed pretty soon!

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.

Please disable the Overwolf overlay.

I totally understand your enthusiasm for news on the update and that you have been waiting for changes like this.
The dev blog will be the next set of comms, and will give you much more information on the class revamp - until then all the information I can give is what the devs said to journalists at Gamescom

After Patch #13 launch I will be able to take time to sit down with the EP etc to talk about our likely patch cadence going forward and see if I can set a comm-link cadence in line with that.
Ultimately I don’t want to be in a position again where I don’t have information I am able to share, and just communicating for the sake of keeping to the set schedule, so they might well become more ad-hoc.

So I would imagine the next comm-link won’t be until after Patch#13, and the next piece of comms from us will be in the form of a dev blog.

Right now as the only member of the Communications team for both Games (aside from Quickpaw on a part time temporary basis for Vermintide) quite a lot is on my plate with big updates coming shortly for both games.
Separately to this, other comms we are preparing e.g dev blogs are written by the devs themselves who are also super busy right now. So by getting our heads down I meant that we have a lot on right now, both on a marketing front and the dev front.
Updates and information to the community will be released in the coming weeks so fret not!

Just to try and keep the forums a bit tidier I will lock this post - I would recommend continuing the discussion in Restart your servers on a regular basis as it is on the same subject!

This is mod-related. Unfortunately, I’m not sure which one is the culprit.

Please try disabling the Overwolf overlay.

Sure. Please PM me

We are already aware of this bug, but thank you for the heads up!