Hello , so i started playing darktide again after a longer time and i dont know if amd drivers broke the visuals but the shield is not what it should look like . I met another amd graphics user that has the same issue. I cant see anything through it since it has color of rainbow and changes randomly like when u have rgb keyboard . It is really hard to play with this bug. THE BUG SEEMS TO APPEAR WHEN I TURN ON THE RTX IN LAUNCHER AND THEN I SWITCH IT OFF IN GAME.
Steps to Reproduce (Required):
I think u need to turn on rtx and then turn it off to reproduce it but not 100% sure
I’ve seen it a few times with an AMD card, drivers 24.20.02.02
No RTX.
I wasn’t able to identify what triggers it though, and last time was more than a week ago.
I had this bug quite a bit when i first started playing, the only way I’ve found to get rid of it is to install mods, since they wont or havent fixed this yet. The psych ward mod reduced the occurrence to maybe only 1 or 2 times since i installed it alone but it did still happen. Thankfully there is a new mod I Wanna See at Warhammer 40,000: Darktide Nexus - Mods and community that can make the shield invisible completely.
Jumping in on this because I’ve had it happen a lot too. Current drivers 24.9.1 but it’s happened on previous versions as well.
Some details I’ve noticed:
It also happens on the small default shield (but everyone runs with dome)
It’s usually fine for one or two games. The bug typically happens the more I play the game. One game will be fine and the next will have it. It doesn’t seem to effect anything besides the shield.
A few times I’ve seen it only partially happen on the shield. The corruption will be concentrated near the bottom and flow up sort of following the wavy pattern the shield typically displays when the bug isn’t present. Because this is rare I’ve yet to get a clip of it.
Restarting the game fixes it temporarily but reappears after another game or two.
Deleting the games shader cache in the game files, clearing the AMD shader cache, and clearing Windows directx cache (per the recommendation of someone else who fixed it somehow) didn’t fix it.
Reinstalling the game and wiping my drivers with the AMD cleanup utility didn’t fix it. Neither did updating my bios or reinstalling chipset drivers.
It happens on both the main build and the experimental build, whether I disable the mesh shader or not, whether I change the upscaler dlls in the game files (no other mods), and seemingly regardless of game settings.
The person who gave me their fix had a 5800X, 6950XT, and Gigabyte X570 + 32gb RAM while I have a 7900X, 7900XT, and Gigabyte B650I + 32gb RAM so it seems likely to be an issue with the driver/game rather than hardware generation (Unless it’s the gigabyte board? Doubt it but idk)
If I know the bug is present I’m able to go to the psykanium and it will show up when I use shield there.
Here’s a replay of the bug:
epilepsy warning
Compared to the typical wavy effect on the shield:
Edit: the stutter in the clips isn’t in the normal gameplay or full clip, probably an issue with cutting the clip down for the file limit.
While the first clip was taken with a power disruption modifier it’s impossible to see through the shield bug even under normal circumstances.
My next attempted fix is going to be a full driver wipe with DDU, uninstalling my chipset drivers first before reinstalling them, wiping all caches, and probably a full game reinstall as well.
Anyone else here with the bug, do you have ReBAR/SAM on? Or instant replay enabled? A gigabyte motherboard maybe? Trying to narrow the issue down and see what else could cause it if my next fix doesn’t work.
I have a 6900xt - driver version 24.9.1, but has happened on earlier versions dating back to like late 2023 / early 2024
SAM is enabled
Instant Replay disabled
I also have an Asrock Motherboard
I am almost 99% sure its just something to do with AMD cards, I also even reported this bug to AMD themselves with their bug report tool but never heard anything back so probably was never seen since I assume im the only person to ever report it to AMD lmao.
Did u update drivers ? I updated them and now i have problem with sound in missions , most of the time there is no sound except sound of fired bullets that are falling to the ground
I just updated to the newest driver through the AMD app so far and still have the shield bug but I had a scheduled DRG night with a group so I didn’t do anything else yet. The full reinstall and everything will come later tonight.
Instead of the AMD cleanup utility I’ve done a DDU driver wipe and reinstall this time + chipset drivers and game reinstall so I’ll post an update here if it pops up again still or goes away
Can sadly confirm that didn’t fix it. Trying ReBAR off in BIOS next. I tried turning SAM off in the driver app earlier in the week and crashed after two missions so I’m assuming this is the proper way to do it. It does show up as unsupported in the app now.
Also here’s the bug on the regular shield since nobody really uses it. Still haven’t captured the partial effect yet.
Ah so turning it off in bios doesn’t count as a restart until I restart again? SAM did show up as unavailable in the app so I figured that was fine. Guess I’ll try more tomorrow
No luck testing it. Turned SAM off in the AMD app, restarted. Checked device manager. My GPU still showed large memory range in the resources tab of it’s properties. Went to BIOS and disabled ReBAR. Device manager showed the large memory range was gone. Restarted again to be sure and still got a driver crash trying to load into my second game. I don’t have this issue with anything else. Game is weird.
I’ve never attempted that but I’ll try it next time I get the chance. Trying something else first though. I noticed the odd radar_pre_leak_64 warning in my event viewer even when not gaming which is windows warning about a potential memory leak. I dug out my old email receipt from microcenter to check the RAM I got with my motherboard + cpu bundle and the reviews are very harsh about it not working properly with EXPO, being unstable, crashing, etc while sometimes still reporting as fine with memory tests. I’m upping my memory voltage a bit to see how that goes first.
epilepsy warning 