I’ve just updated to 1.11.2 and run the game. 5 seconds into character selection screen and game crashes. Disabled mods, game crashed again. Enabled mods, no change.
The game is unplayable now and even unstartable.
It was ok at 1.11.1 although FSR frame gen didn’t work.
[PC] Do You Use Mods? (Optional):
Yes, and I’ve tried disabling them
Reproduction Rate (Required):
Constant (100%)
Platform (Required):
PC - Steam
Player ID (Optional):
[PC] Crash Report (Optional):
GUID: f098743b-1b58-4b30-a43e-7a96978c124c
Log File:
Info Type:
At D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570 in function stingray::aftermath::d3d_assert
After loading Mourning Star (quickly pressed start before game crashed). Loading screen took like few minutes to load (previous patch it was like seconds). After ~10 seconds in-game:
At D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570 in function stingray::aftermath::d3d_assert
THE GAME IS UNPLAYABLE. Can you please rollback patch to 1.11.1?
Deploying a product in such state to production environment at my job, would result in firing people. This patch 1.11.2 renders the product useless.
At D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570 in function stingray::aftermath::d3d_assert
Turned off AMD fps counter. Turned off every AMD enhancement (RSR, Fluid Motion Frames, XGP, FSR). The error still persists.
Also turned off FSR upscaling and frame gen in game options. I have like 40-60 FPS in mourning star but it seems it doesn’t crash anymore.
After that I set FSR upscaling to quality. It didn’t crash for few minutes. After that I set AMD FSR Frame Generation to On - and game crashes in 10 seconds.
So the culprit and crash cause is turning on AMD FSR Frame Generation. So the fix didn’t fix the errors with FSR, but has worsened the issue.
I am having a similar issue with the same GPU. I’ve deleted all mods, verified files, and even done a clean install from scratch. I can’t even get passed the launcher at this point. I can go into the game directory and skip the launcher, which works, but then I can’t actually play because I’m not logged in.
Seems to be an issue with the recent small update, because I was running pretty well the day before, minus some stuttering which I assume was what the patch was meant to address.
At D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570 in function stingray::aftermath::d3d_assert"
Try turning on AMD FSR Frame Generator in game options and report if it crashes. Thank you
By the way AMD Fluid Motion Frames is driver level generator for games that don’t support FSR Frame Generator. FSR Frame Generator (FSR3.1, FSR4 or FSR Redstone), which is game engine level, is supposed to give better quality and more fluent picture than Fluid Motion Frames.
What is your AMD Adrenaline Software version?
Mine is 26.3.1 which is up to date. Also I did clean reinstall AMD drivers after Darktide 1.11.1 and before Darktide 1.11.2 (removed amd drivers completly before new installation).
Sadly even if I turn everything off in adrenalin, the game still crash after a few seconds.
Even after clean reinstalling the AMD driver and reinstalling Darktide.
The issue still exists.
Current driver: 26.3.1 (Same as yours.)
Maybe if I roll back 25.9.1 the game would probably ran without issues.
But other games run well without any issue and some games running better with the current driver. For example Monster Hunter Wilds or Mechwarrior 5: Clans.
I can wait for Fatshark to fix the issue, and someday maybe they fix these issues.
In the meantime also hope they make some content which was actually requested by the community.
Turning AMD FSR 3.1 Frame Generation on will cause the game to crash on RX9070XT. Turning it off will make the game playable but with lower framerate. Extra frames with FSR Frame Gen are generated by the game engine, not at driver level. Driver can only override algorithms at game engine to use FSR 4 or FSR Redstone if available for the game (which are available for Darktide).
Frame generation by AMD Fluid Motion Frames 2.1. You turn it on via AMD Adrenaline Software options:
Turning AMD FMF 2.1 doesn’t cause the game to crash on RX9070XT. Turning it on improves framerate, but there are visual artifacts. Extra frames are generated by the AMD driver, and algorithms to generate picture don’t have access to game engine/game files. The frame pacing is uneven, UI has ghosting effects during transitions, motion vectors are handled poorly, shadows are inaccurate.
The temporary solution to the issue is to turn off FSR 3.1 Frame generation via in-game/launcher options. To have acceptable framerate you can turn on AMD FMF 2.1, but be prepared to visual artifacts and lower picture quality.
Yes, I tried exactly this one to but the performance was horrendous and I’m a bit off tired of tinkering with the game after every patch/hotfix and modifying the .ini file too.
After 1800+ hours I just uninstalled the game.
Still love the game but right now I just take a break from it.
Maybe after some time the game will be playable and MAYBE they make something which makes the game worth reinstalling.
Off topic but for me the expeditions are a huge let down.
This game has so much potential to be awesome, but the devs don’t listen to the community and barely communicate to us.
For anybody crashing with FSR Frame Generation enabled: to support our investigation with AMD, would you be willing to try rolling back to an earlier driver version, to see if the issue persists?
I have started the game in patch 1.11.3 with AMD FSR Frame Generation turned on in game launcher/game settings. In AMD Adrenaline Software I changed nothing:
## GUID: 71ac1b55-9498-48ee-978e-cbbacdcfce10
Log File:
Info Type:
\[Engine Error\]: HRESULT: 0x887a0005 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_DRIVER_INTERNAL_ERROR, assert: \`\`
At `D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570` in function `stingray::aftermath::d3d_assert`
After that I have restarted the game and I have turned off AMD Fluid Motion Frames 2.1 and turned off Frame Generation AMD FSR:
## GUID: 2d90e22a-c7be-42f0-bc2e-aa302dfeb821
Log File:
Info Type:
\[Engine Error\]: HRESULT: 0x887a0005 = DXGI_ERROR_DEVICE_REMOVED: GetDeviceRemovedReason() = DXGI_ERROR_DRIVER_INTERNAL_ERROR, assert: \`\`
At `D:\a\d\e2af82edaa31c93c6098ffbd561125ed\b0be1561439953a6\stingray\runtime\d3d12_render_device\d3d12_debug.cpp:1570` in function `stingray::aftermath::d3d_assert`
The game still crashes. I have reverted changes in AMD Adrenaline Software (back to defaults with HYPR-RX profile) and turned off FSR Frame Generation in game launcher/game settings.
The game doesn’t crash.
I will try to downgrade my AMD drivers later tonight. If I have to clean reinstall drivers, I can do it as soon as weekend (I use PC also for professional work). Will report what I find.
I rolled back my driver to version 25.12.1 and played for three hours without any crashes. It seems there might be a bug between AMD’s new driver and the game. I hope you can fix this issue as soon as possible.
Would be super to hear if 25.12.1 (or perhaps even later versions?) alleviate the issue for others. We’ll continue looking in to this on our end too, of course
