The game runs at a stable ~60-70 fps for the first 1 or 2 games upon opening darktide but then becomes very inconsistent with fps varying from ~30 fps in the mourningstar to 60 fps in empty rooms and 20 fps during hordes after said first few games.
Attempted Solutions (Optional):
Assumed this was caused by a memory leak in the game and tried to remedy using a mod to help lessen effects of memory leak but did not notice any noticeable improvements
00:29:22.097 [D3D12_RESOURCE] Render Target ‘#ID[60f3d04d247b73b4]’ was not released, refcount: 10
00:29:22.097 [D3D12_RESOURCE] Render Target ‘#ID[df10df4a8ef95522]’ was not released, refcount: 10
00:29:22.098 [D3D12_RESOURCE] Render Target ‘#ID[567e683f9ea1f34c]’ was not released, refcount: 10
00:29:22.101 [D3D12_RESOURCE] Render Target ‘#ID[60a1b6186dddd602]’ was not released, refcount: 7
00:29:22.101 [D3D12_RESOURCE] Render Target ‘#ID[755c1ae405b532ef]’ was not released, refcount: 7
00:29:22.167 [d3d12 pipeline state] PSO fail rate 0/4466 (0%)
00:29:22.175 [d3d12 pipeline state] Serialized pipeline library
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 131072 b allocated
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 262144 b allocated
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘10df4a8ef95522]’ has still registered 0 b used and 131072 b allocated
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 131072 b allocated
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘7b73b4]’ has still registered 0 b used and 131072 b allocated
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 262144 b allocated
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 262144 b allocated
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 131072 b allocated
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘#ID[60f3d04d247b73b4]’ has still registered 0 b used and 131072 b allocated
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘]’ has still registered 0 b used and 2097152 b allocated
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 131072 b allocated
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 131072 b allocated
00:29:22.178 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 131072 b allocated
00:29:22.529 warning: [DummyRegistryAllocator] Registry ‘default_heap_constant_buffer’ has still registered 0 b used and 65536 b allocated
00:29:22.529 warning: [DummyRegistryAllocator] Registry ‘vertex_buffer’ has still registered 0 b used and 1644167168 b allocated
00:29:22.529 warning: [DummyRegistryAllocator] Registry ‘index_buffer’ has still registered 0 b used and 230686720 b allocated
00:29:22.530 warning: [DummyRegistryAllocator] Registry ‘D3D12Memory’ has still registered 0 b used and 1878982656 b allocated
Yes, you can say there is a leak
That’s about as useful as trying to fix it by doing interpretative dance
One thing that could help is lowering your texture quality to low (unless you already have it) and regular game restarts while waiting for the fix, which might be a question of days if we optimistic
17:12:28.060 warning: [DummyRegistryAllocator] Registry ‘]’ has still registered 0 b used and 4521984 b allocated
17:12:28.060 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 589824 b allocated
17:12:28.060 warning: [DummyRegistryAllocator] Registry ‘5c1ae405b532ef]’ has still registered 0 b used and 589824 b allocated
17:12:28.060 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 589824 b allocated
17:12:28.060 warning: [DummyRegistryAllocator] Registry ‘#ID[75314ba6]’ has still registered 0 b used and 3276800 b allocated
17:12:28.060 warning: [DummyRegistryAllocator] Registry ‘ddd602]’ has still registered 0 b used and 2686976 b allocated
17:12:28.060 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 589824 b allocated
17:12:28.060 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 589824 b allocated
17:12:28.060 warning: [DummyRegistryAllocator] Registry ‘#ID[60f3d04d247b73b4]’ has still registered 0 b used and 38797312 b allocated
17:12:28.060 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 524288 b allocated
17:12:28.060 warning: [DummyRegistryAllocator] Registry ‘#ID[492e409b]’ has still registered 0 b used and 8585216 b allocated
17:12:28.060 warning: [DummyRegistryAllocator] Registry ‘#ID[60f3d04d247b73b4]’ has still registered 0 b used and 589824 b allocated
17:12:29.652 warning: [D3D12ArrayStorage] 7 of 12880 resources of type ‘D3D12Texture’ has not been released.
17:12:29.689 warning: [DummyRegistryAllocator] Registry ‘srv_uav_cbv_descriptors’ has still registered 224 b used and 0 b allocated
17:12:29.726 warning: [DummyRegistryAllocator] Registry ‘permanent_descriptors’ has still registered 224 b used and 0 b allocated
17:12:29.726 warning: [DummyRegistryAllocator] Registry ‘default_heap_constant_buffer’ has still registered 0 b used and 65536 b allocated
17:12:29.727 warning: [DummyRegistryAllocator] Registry ‘vertex_buffer’ has still registered 0 b used and 1174405120 b allocated
17:12:29.727 warning: [DummyRegistryAllocator] Registry ‘index_buffer’ has still registered 0 b used and 218103808 b allocated
17:12:29.727 warning: [DummyRegistryAllocator] Registry ‘shader_table’ has still registered 0 b used and 4194304 b allocated
17:12:29.727 warning: [DummyRegistryAllocator] Registry ‘#ID[e40c8985]’ has still registered 403200 b used and 458752 b allocated
17:12:29.727 warning: [DummyRegistryAllocator] Registry ‘comitted_textures’ has still registered 458752 b used and 458752 b allocated
17:12:29.727 warning: [DummyRegistryAllocator] Registry ‘D3D12Descriptors’ has still registered 448 b used and 0 b allocated
17:12:29.727 warning: [DummyRegistryAllocator] Registry ‘D3D12Memory’ has still registered 459200 b used and 1459748864 b allocated
[Log end]
Same issue, just noticed it recently, it wasn’t a problem a month or so ago, I often left game running in background for a while. Now I see steep drop in fps counters after a few matches, until I restart the game.
So it’s still not fixed? I’m having it too (AMD RX 7600 card). Just after two games FPS drops 20 points (from 80 - what is already pretty low, no idea why is it so slow on medium settings - to 60). And then it gets worse, at 40 it’s already unplayable at higher difficulties. I need to restart the game to play another couple games each time.
Here is my log from today’s session (15 mins in simulation and one Auric run), which started at 90-100fps, and ended at 40-50, even on the station. (I use mods here, but I’ve tried to disable them, it didn’t help) console-2026-02-07-15.36.24-d0d7196f-3e5c-4080-bb2d-026eadd778d1.log (454.6 KB)
What i found after putting diagnostics on my screen was the GPU for some reason just gradually lost power over time. For EG it’d start at like 350 - 370 watts, then gradually just drop to like 280, then 250, then 220, then 180 etc.
What immediately snaps it out of it is if mid mission I go escape → options → video. That’s it, just close the menu after that. My GPU immediately goes back up to 350 - 370 watts and normal performance.
No idea why, it’s literally only darktide this happens on, no other game.
I’ve observed it for a month as of now, and yes I also noticed the power loss in monitoring tools - but I think it may be a byproduct of something else, in particular CPU not feeding enough data for GPU to process, so GPU just naturally reduces its throughput as well. That could be one explanation.
I also noticed that about that time when I see steep drop in FPS (up to 2 times) the game usually crashes due to various memory-related shortages (both RAM and page file are mentioned; both have enough free space left at that moment). So either it crashes and I start it again and enjoy decent FPS for about 3 matches - or I had to restart it myself as it becomes unlayable.
I think those things - obvious memory leaks and gradual FPS drop - may be interconnected. Perhaps CPU is getting more and more bogged down in handling memory allocation and release while memory leaks grow in volumes - and so it has less and less time to prepare frames for GPU to draw. Something like this.
