the only thing I can say is they they are rolling out patches almost daily on the experimental.
but they still do not tell us anything, or say what it changes.
I personally would like to see a fully offline version without EAC to rule it out as potential crash cause.
Even if its only for like 100 people to test, because I somehow doubt the dev build is crashing that much…
but I personally know from experience that most internal builds don’t use any anti cheat (correct me if it changed in the last 5 years).
Underclocking seems to have helped a lot. Dont have enough time to really test atm, but i managed 3 games without a crash, which is progress. That said, there have been fixes before that did the same, and then suddenly it was a crashfest again.
Underclocking did reveal something interesting tho, some really hard hangs and stutters that ive never had before. Like the game just totally locks up for a second or two and then resumes. Im assuming these would have been my crashes before.
I hate EAC as much as the next guy, but i regularly play serveral games with it, and none of them behave like Darktide. I cant think of a single game that has been this unstable (EAC or not)
yeah they did a darktide release stream where at least 2 CMs were present and on camera the whole time playing the game.
they also clarified in that stream that one of them is vermintide only and the other one manages Darktide only, also pretty sure that was not supposed to be said but they were playing a internal build and not the release version…
Thanks for the link, I’m sure their heart is in the right place and I hope they can find the time to fix this issue. Perhaps the Community Manager - Catfish will help with the comms drought.
well she starts in janurary and I am pretty sure the game will be completely dead if they don’t fix the bugs till then, or the community is so mad at this point that she will get just trash talked into the ground on her very first day.
Yes again , crash when aiming with bolter. DLSS on. And gpu usage suddenly raise to 100%.
GUID: 9f5a7a83-59a3-46b2-8b82-fc028424e7d4
Log File:
Info Type:
I can only play the game if I set the worker threads to the value 1.
This ofc makes it somewhat playable, but often drop down to 40ish fps since only 1 CPU thread is utilized. Average around 60 fps.
If I set worker threads to for example 8, the fps only drops to around 70-80 and averages around 100+ (Max GFX settings, RTX = OFF), but crashes anywhere between 1-5 minutes.
I see that in the console log that the GPU crashes, but in crash dump it states a read/write exception on virtual threads(CPU?).
Specs:
Windows 11 (Latest official update)
Ryzen 7 3700X @ 4200Mhz 8/16 Core
Asus RTX 3080 10GB
32GB DDR4 3200Mhz
Issue Description:
Worker Threads > 1 = Crash
Steps to Reproduce:
Set worker threads to anything over value 1
Start game
Wait in game or join a session
Crashes after a few minutes
Mission Name (If Applicable):
Platform:
Steam
Player ID:
ShadowFart
Approx. Time of Issue & Timezone:
Happens every single time I try something other than value 1
GPU hangs are among our key priorities right now, and we work on a solution to them around the clock. While they are becoming less and less common, and we know our efforts so far have worked, we understand we are not yet where we want to be: eradicating the issue entirely so that all of our players get to enjoy the game without interruptions.
What we have seen from our crash-data is that they are more common on Win11, and more common on high-end GPUs (30 series). They do occur across the board as well, but in a much much less frequency.
Most repeat-crashers seem to have the previous in common, but there are exceptions.
The experimental build is where we do rapid updates when we find something that could possibly be the source of the problem.
PC development is very tricky as there are so many different configurations, drivers, hardware, software, and a plethora of other influencing factors. Rest assured the work on eradicating GPU hangs won’t stop until we have succeeded.
There are many more of crash logs with this issue that I’ve never posted because it’s the same issue (and of course that all of us with this crash since BETA is exhaust by now). But doesn’t mean this issue is less common each experimental branch update.
For now, I’ve tried Fasel guide with -150 Mhz offset Core Clock, -500 Memory Clock and set the Curve with stable core clock from 1000 mv which is the most stable I have ever experienced (beside playing on Windows 10) with 6 threads, High settings, DLSS on - Quality, 60 FPS Cap.
could you please push microsoft to approve the updates for the game pass version? I managed to resolve the crashes with worker threads = 1 but it’s kinda unplayable with my ryzen 2700 locked to a single thread…
I thought I should mention it in this thread. I am completely unable to play without experiencing a crash to desktop, but the error present in the console logs isnt a GPU hang but it instead this is the error,
[D3D12_RENDER_DEVICE] SL Error: '[04.12.2022 10-18-00][streamline][error]commoninterface.h:336[set] Setting ‘common’ constants with the same frame index several times per frame, this needs to be fixed!
I have also noticed that if the game errors out in this way then no crash dump is generated. Not sure if anyone else has this issue but wanted to bring it to attention.
setting my 4090 to 33% power limit and -200mhz gpu core reduces crashes. not to 0 but can get a mission done maybe 2 now. playing on game pass. 3700x 4090 win 11 all drivers and up dates
GUID: e9caa0a7-fa1d-405e-bb80-ffb8a71decf0
Log File:
Info Type: