Warhammer: Darktide Dev Tracker

@Garfielf, name changed!

@GRIPPY, done!

@NimaQ87 name changed!

@Myrddin done!

Hm, do you have another GPU that isn’t being utilised correctly? It may be worth checking out this article:

As i’ve said in other threads, It’s barely been a month since most of us got back from vacation so we are a little ways out yet. But be assured we are working on the next updates currently, just aren’t ready to communicate on them just yet!

Oh shoot, I thought this was the V2 forum. RIP.

So I can’t really say too much on what goes on in Darktide as I don’t work on it, but at least V2 side, usually it’s due to a handful of reasons:

• The issue is taking longer than expected to figure out
• The issue is pushed down in the priority list to make room for the developers to address more pressing issues (such as crashes, etc) who would otherwise be responsible for that fix
• The issue is resolved but waiting to be rolled into a more extensive patch/build
• On console, the issue is resolved, but is in the cert process

Again, I can’t really speak too heavily on Darktide as I’m not usually poking my nose into there (except here where it was an accident, whoops!); but hope this gives some context into some of the triage that happens with the acknowledged tag!

It means the community support team has looked at it and inputted it into our report logging system. This system is then used for prioritization or triage and also helps us log replication of the report.

Not at all! There are some in the pipeline.

Just to clarify - my comment was in reply to having devs themselves posting thoughts and updates, rather than dev blogs

Why would we have the same processes for two different games especially ones so far apart in life cycle? They have separate EPs who have different visions.
One has a considerably larger team than the other - so a process that would work for the Vermintide team might not work for Darktide.
Also the differences in the systems, servers, tooling, etc means we cannot have the same process for a lot of elements.
We try and centralise where we can but tailoring our processes to the product and the devs/managements requests is important.

I totally understand that and hear you!
With the confidence element - game development isn’t always as simple as ‘we want to do X → do the work for X → it works → we release it.’
Something that i’m sure all game studios suffer from is the ‘we want to do X → oh there are so many bugs this creates can we fix them all? → is this even doable?’
Of course we are much further than this in the process for the things we want to release however until it is a done deal it is hard to give a date.

To reassure ( as much as I can) you I see all of you requesting some statement on vision, and I am feeding this back to the team.

It almost as if they are two separate games with two separate sets of developers and processes!

Please do not necro threads as stated in the forum rules! There are many more recent threads you can use for this discussion, or create your own.

Locking this thread

Thanks for the update - that’s interesting to know. Hopefully it’s done the trick

Hi @Fumero,

You appear to be running into a GPU-related crash. I recommend trying our GPU crash solutions, here:

Glad to hear you resolved this

Hi @boxy,

Sorry to hear this.

Regarding the GPU crashes, as you’ve tried our usual solutions already, the only other thing I can recommend to try is rolling back to a previous driver version to see if it’s the current latest GPU driver version that isn’t playing nicely.

For the Access Violation crash (0xc0000005), this is usually due to a conflict with Anti-Virus. I recommend checking this article out:

Hi @cacanegra,

You appear to be running into a Deadlock type crash, though I can’t determine the exact cause from the log data.

In this instance, I recommend to try a clean reinstallation of Darktide:

Hi @Bodnamax,

I wonder if there may be a background application/process that’s causing this.

I recommend to try disabling your background applications via a ‘Selective Startup’, and to try running through our other performance improvement solutions, here:

@BecauseRaisins, done!