Warhammer: Darktide Dev Tracker

Thanks again!

Hey, so the patch note on this reads :

• Fixed issue where ‘Counterfire’ didn’t increase weakspot damage by an additional 25%.

But I will double check with the devs if there was a increase on top as well!

Rejects,

Here are the notes for Hotfix 1.0.26 to fix some of the issues that arose from Patch 1.0.25:

• Fixed an issue where players could not complete Basic Training as Skullbreaker.

• Fixed an issue where Darktide would crash after making changes to the FOV slider in the video settings.

  ...

This will be addressed in our upcoming patch, apologies.

Thank you for the update! I was under the impression this would be AppData-related but I was very wrong there.

This is indicative that an underlying issue is at play - check out your Windows Event Viewer for any errors.

Take a breather, Sir. No ...

Long story short, depth is defined differently for different people and that’s ok (or should be)

/thread

As noted once before, we do have plans to include a score board down the line that puts more focus on cooperative stats than promote tunnel vision plays, putting a focus on cooperative play than personal glory. Whether or not we present personal glory to individuals isn’t entirely defined but we’ve seen the feedback throughout the varying threads on this matter over the past months so we’ll see what comes of it.

I am going to lock this up though as it’s framed in a manner that’s prone to incite one camp versus the other and we’re all honestly getting a little exhausted from the volume of infighting going on in the boards.

Rejects,

For today’s blog, we will outline some of the features and changes we are actively working on in our next major patch and discuss how we arrived at making some of these changes in detail.

An Update on the Shrine

Before Darktide’s launch date, we brought an update on the di...

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 )

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,...

Thanks for flagging! This should be fixed with the upcoming Hotfix which is due to go live tomorrow.

Thank you for the update!

Thank you for your report, we’ll be patching for this soon.

We will be releasing a patch for this soon. Thank you!