KNOWN ISSUE: Crashing at Random, Due to GPU-Related Errors

I’ve been stressing the game graphics wise (dlss, ray tracing, high settings, high worker thread, high foliage counter, 120 fps and no fps limits, etc) and I still haven’t had a crash since the most recent experimental beta.

console-2023-02-08-07.17.16-c783a193-b587-44a2-b673-f249274e8397.log (270.4 KB)

Hi, thanks for the quick fix!

Have there been any changes to this experimental branch with the new patch vs the previous one?

On prior patch and experimental branch, I had the same experience as the poster above “I’ve been stressing the game graphics wise (dlss, ray tracing, high settings, high worker thread, high foliage counter, 120 fps and no fps limits, etc) and I still haven’t had a crash since the most recent experimental beta.”

But after latest patch and experimental branch, I am crashing about once a game…mostly when things get hectic on screen.

i9 12900k, 32gb ddr5, evga 3080ti, 1440p ultrawide monitor (downclocked by 200MHz per the “reduce crashes” page here). everything patched and updated.

I’ll try lowering worker thread count from 21 to 10 (was that what you recommended?).

Kind of demoralizing…finally thought the game would run well. Only got to enjoy 1-2 days of crash free play. Any advice would be appreciated!

Thanks!

Why we don’t see no improves in stability in final releases?

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 :slight_smile: )

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, its almost always is once you finally solve a bug. But the nature of it is that it’s always on a move, the slighest change in timing between threads and the gpu can make it just work as it’s supposed to, or crash and burn horribly.
For people with slower CPUs and slower GPUs, it seems to be much less likely that whatever goes wrong goes wrong. For people with faster CPUs, with more cores and especially faster GPUs (30xx series+) It’s much more likely that whatever goes wrong goes wrong. This is also why lowering worker threads, capping frame rates seems to help.

To that end, the reason there have not been any stability fixes in the main release yet is because we haven’t found the culprit yet. The disabling of the portraits is a measure that seems to reduce the likelyhood of the issue to occur, but it’s not the issue itself. It still happens, just in a lesser frequency than before, and it also entirely depends on the hardware and the current mood of the PC, since it’s so highly dependent on time. This is also why each patch can seem to “move” the crash around, patches may fix it for some, and make it worse for others. Unfortunately.

We have managed to create an artifical repocase where we almost reliably can casue a hang to happen, and this is the first time since launch that we have been able to do that, if this is THE hang we’re not sure, but it is A hang. The people who can work on this issue are working 100% on solving it every day. The rest of the team are not equipped to work on this, so they will naturally continue to work on other aspects of the game, and that is why we release patches without fixing this issue. The things that are easily fixed are getting fixed while we continue to work on this beast.

19 Likes

@FatsharkPdr Thanks for the open and honest response. It makes sense, and many of us know how hard it is to find a bug even in relatively straightforward programs we write.

As for me, I’ve stopped playing the game for now and just check this thread every couple of days to see the progress. I’ll be back when there’s an announcement of a fix.

I am still crashing in the normal version of the game and in the experimental beta.

GUID: 8402ca95-31e9-4ff5-9e9c-168633b3b584
crashify://8402ca95-31e9-4ff5-9e9c-168633b3b584

many thanks for your team’s continued work on this. It’s incredibly frustrating as a player.

So far nothing has worked for me this patch. 10 worker threads, downclock gpu by 200hz for ultrawide (would capping the refresh rate to 120 on the actual monitor help?), no rtx, no overlays, experimental branch. Capping fps at 60 seems to help but is very jarring for my eyes.

New kind of crash cropped up too…used to be only CTDs, but now I’ll occasionally have the whole computer hang and autorestart.

Hope you guys figure this out soon!

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

Sadly, too little too late. Most of us who had this crashing issue have uninstalled the game like myself.
I’m genuinely curious as to why the decision was made to release the game in the state that is was/is? as this issue was well know from the get go during the beta period.
It just screams greed, cashing in on the Christmas period releasing then disappearing on holiday for the best part of a month.

1 Like

The experimental beta seems to be mostly stable. I still get rare crashes.

2 Likes

While I thank you for finally having the decency to communicate honestly with us @Developer , I too am already furious and insulted enough that it’s far too little arriving far too late.

You’ve had 4 months since the issue became apparent, and you have spent that time firstly ignoring our requests for an explanation, originally even having the gall to blame it on players troubleshooting ability.

You’ve then spent 4 months insulting us with your silence. I refunded the game two weeks after launch, when it became clear you were not in any rush to fix things. I’m sure many others did, but I’m also aware most now cannot, because they’ve spent so much time on the game, trying to do the troubleshooting you are paid to do, which in turn means they cannot get a refund from steam very easily

All in all, you’ve insulted us, you’ve ignored us, and it’s taken you four months to hold your hands up and say “we just don’t have a clue what’s going on”.

Congratulations, we’ve had some truly horrific PR disasters in the games industry over the last year or two, but this is the most ludicrous example I’ve seen yet.

So no, there will be no understanding, there will be no working with your community. That boat has long since sailed, the steam player charts demonstrate that very clearly.

1 Like

The “portrait-less” experimental patch was the fix all for me. Please release the same patch for the hotfix you made today.

Thanks for the response. So is there any chance that DT using DirectStorage, a new tech that allowing games transfer assets directly to GPU and bypass the CPU processor, which seems would benefit solving DT’s crashes and make game loading faster.

GUID: 5894743b-64e8-49cb-8bd6-1acad2e64e37
Log File:
Info Type:


New experimental deployed. Please update and try.

4 Likes

Issue Description:
Game crashed abruptly. Using experimental build. Did well 12 games or so yesterday, but second game today, and crash upon first contact w/ the enemy.

Crash Report (If Applicable):
GUID: aef8d16e-c2ef-4d7f-86f7-2c0424e6b3ef
Log File:
Info Type:


Error Displayed (If Applicable):
n/a

Steps to Reproduce:

  1. Play game.
  2. crash.

Mission Name (If Applicable):
i have no idea what the name of the mission was. but there was fog.

Platform:
steam

Player ID:
prysmatik

Approx. Time of Issue & Timezone:
5:50pm EST 2/10/2023

Reproduction Rate:
Unknown, but seems better than before.

Upload Supporting Evidence:
n/a

Upload Console Log:
https://pastebin.com/FqWfdDVh

Upload darktide_launcher.log:
https://pastebin.com/H2DNxdCc

tl;dr: <>gpu hang<</Crash type>>

Didn’t crash once on previous experimental build, even with stressing the quality higher than reasonably ‘playable’. Just crashed on this version using just TAA and medium/high video settings.

5800x3d / 3070ti with the new 528.49 driver

GUID: 84178595-4c30-44f8-abf2-cfb81c3e0850
[Crash Link]:
crashify://84178595-4c30-44f8-abf2-cfb81c3e0850
console-2023-02-11-07.15.02-84178595-4c30-44f8-abf2-cfb81c3e0850.log (577.8 KB)
crash_dump-2023-02-11-07.15.02-84178595-4c30-44f8-abf2-cfb81c3e0850.dmp (940.4 KB)

Massive crash, BSOD to os reboot. After an hour of play with lower settings…this exp branch is way less stable than the previous version.

crash_dump-2023-02-11-13.25.21-4b8c476d-8068-44f2-83af-9a7358ae19fa.dmp (684.2 KB)
console-2023-02-11-13.25.21-4b8c476d-8068-44f2-83af-9a7358ae19fa.log (244.6 KB)

So, I am wondering why it is that the game still crashes after 1-3 missions?

So I gonna let you all see the user settings I have here and guys. Tell me what on earth I need to do to get my game fix?

Hardware: AMD ryzen 5
RAM: corsair 16 GB
GPU: Radeon RX 580
driver: AMD adrenaline (updated)

entire user settings here:
adapter_index = 0
aspect_ratio = -1
borderless_fullscreen = false
fullscreen = false
fullscreen_output = 0
gamma = 1
gore_settings = {
attack_ragdolls_enabled = false
blood_decals_enabled = false
gibbing_enabled = false
minion_wounds_enabled = false
}
interface_settings = {
intro_cinematic_enabled = false
}
language_id = “en”
launcher_overrides = {
}
master_render_settings = {
ambient_occlusion_quality = “off”
anti_aliasing_solution = 0
dlss = 0
dlss_g = 0
dlss_master = “off”
dof_quality = “off”
fsr = 0
fsr2 = 0
graphics_quality = “custom”
lens_flare_quality = “off”
light_quality = “off”
nv_reflex_framerate_cap = 1
nv_reflex_low_latency = 2
ray_tracing_quality = “off”
ssr_quality = “off”
volumetric_fog_quality = “off”
}
max_worker_threads = 1
performance_settings = {
decal_lifetime = 1
max_blood_decals = 1
max_impact_decals = 1
max_ragdolls = 1
}
render_settings = {
ao_enabled = false
baked_ddgi = false
bloom_enabled = false
cacao_downsampled = false
cacao_quality = 0
decals_enabled = false
display_noise_enabled = false
dlss_enabled = false
dlss_g_enabled = false
dof_enabled = false
dof_high_quality = false
dxr = false
fsr2_enabled = false
fsr_enabled = false
fsr_quality = 0
fxaa_enabled = false
gamma = 2.2
hdr_rgb_format = “R11G11B10F”
jitter_enabled = false
lens_flares_enabled = false
lens_quality_color_fringe_enabled = false
lens_quality_distortion_enabled = false
lens_quality_enabled = false
light_shafts_enabled = false
local_lights_max_dynamic_shadow_distance = 0
local_lights_max_non_shadow_casting_distance = 0
local_lights_max_static_shadow_distance = 0
local_lights_shadow_atlas_size = [
8
8
]
local_lights_shadow_map_filter_quality = “off”
local_lights_shadows_enabled = false
lod_object_multiplier = 0.5
lod_scatter_density = 0
motion_blur_enabled = false
nv_framerate_cap = 60
nv_low_latency_boost = false
nv_low_latency_markers = false
nv_low_latency_mode = false
nv_reflex_framerate_cap = 1
nv_reflex_low_latency = 2
outline_enabled = true
particles_capacity_multiplier = 1
particles_simulation_lod = 0
rough_transparency_enabled = false
rt_checkerboard_reflections = false
rt_light_quality = false
rt_mixed_reflections = false
rt_particle_reflections_enabled = false
rt_reflections_enabled = false
rt_shadow_ray_multiplier = 0
rt_transparent_reflections_enabled = false
rtxgi_enabled = false
rtxgi_scale = 0
sharpen_enabled = false
skin_material_enabled = false
ssr_enabled = false
ssr_high_quality = false
static_sun_shadow_map_size = [
8
8
]
static_sun_shadows = false
sun_flare_enabled = false
sun_shadow_map_filter_quality = “low”
sun_shadow_map_size = [
2
2
]
sun_shadows = false
taa_enabled = false
ui_bloom_enabled = false
upscaling_enabled = false
upscaling_mode = “none”
upscaling_quality = “quality”
vertical_fov = 85
volumetric_data_size = [
10
8
12
]
volumetric_extrapolation_high_quality = false
volumetric_extrapolation_volumetric_shadows = false
volumetric_lighting_local_lights = false
volumetric_reprojection_amount = 0
volumetric_volumes_enabled = false
world_interaction_size = [
52
52
]
world_space_motion_vectors = false
}
screen_mode = “window”
screen_resolution = [
1600
900
]
sound = {
}
sound_settings = {
option_master_slider = 25
options_music_slider = 25
options_sfx_slider = 25
options_voip_volume_slider = 0
}
texture_settings = {
“content/texture_categories/character_bc” = 0
“content/texture_categories/character_bca” = 0
“content/texture_categories/character_bcm” = 0
“content/texture_categories/character_hm” = 0
“content/texture_categories/character_mask” = 0
“content/texture_categories/character_mask2” = 0
“content/texture_categories/character_nm” = 0
“content/texture_categories/character_orm” = 0
“content/texture_categories/environment_bc” = 0
“content/texture_categories/environment_bca” = 0
“content/texture_categories/environment_hm” = 0
“content/texture_categories/environment_nm” = 0
“content/texture_categories/environment_orm” = 0
“content/texture_categories/weapon_bc” = 0
“content/texture_categories/weapon_bca” = 0
“content/texture_categories/weapon_hm” = 0
“content/texture_categories/weapon_mask” = 0
“content/texture_categories/weapon_nm” = 0
“content/texture_categories/weapon_orm” = 0
}
threads = {
}
version = 2
vsync = false

These are the settings atm. I saw that I still had parts of RTX set on “true”. Those are now set on “false”. I also switched off the latency booster and low latency mode on the settings as well.

But it is getting crazy with the crashes I tell you. because even when you stand idle in the morning star, the game will crash at random.

This is something that NEVER happens with other games like Genshin Impact when those are played on very low settings.

I gonna keep tweaking the user settings. But Fatshark, you claimed on steam that the minium requirements was Radeon RX 570, 8 GB ram, and AMD Ryzen 2400G. This is silly that you put me on a lot of stress when adressing the issues. It took me 2 full months to tweak out 70% of the crashes and it seem that I have to tweak the user settings to the absolute lowste of settings just to play your game without crashing.

So I hope that you gonna stablized the game further. But the reason for putting my user settings here is to show to all of you, how ridiculus the whole situation has become…

Nothing you can do will fix your crashes, it’s a code issue. Best thing to do is keep your settings low and use the experimental patch.

It’s ridiculous, it’s frustrating, it’s annoying…but progress IS being made from the stability of these experimental patches as they come out.