When you hold F allowing you to select the wall/sphere, is the effect garbled too or just when it’s placed?
Event viewer entry should have more info as to the culprit?
Just FYI memory leaks are software issues, and too often the term is overused and overused incorrectly leading to confusion.
E.g. an MS forum thread , a quick read.
I guess it’s technically possible for HW to cause chaos, but probably very very unlikely fwiw.
P.S. Can an AMD user test this real quick? I was wondering if the issue was with updating the shield effect or if it’s there from the beginning.
ForceFieldFixer.zip (13.9 KB)
All it does is disable the update based on remaining life
--local variable_name = self._sphere_shield and "psyker_sphere_shield_life" or "psyker_flat_shield_life"
--Unit.set_scalar_for_materials(self._unit, variable_name, 1, true)
Just when it’s placed iirc but I don’t use shield enough to know. I only made a set with shield on for testing purposes in the first place.
And yea, the memory leak warning pointed at the radeon software but I’ve also had event viewer report an application fault with darktide when closing the game. The game itself showed no signs of crashing either.
When searching up why the game would crash without SAM on I actually came across this comment in an AMD community thread where the OP was getting crashes in CPU intensive games. The OP ended up getting a new card but the commenter fixed their issue by upping their RAM voltage. That lead to me investigating my memory (also gskill, hmmm) and if you look at all the low rated reviews from the microcenter website it seems to be a very common issue usually solved by bumping the voltage from the EXPO rated 1.35v to 1.36.
It could explain why turning on memory integrity stopped my crashes but not for @AsukaSoryuLangley because ryzen is picky with memory and memory issues can pop up in a lot of odd ways without being immediately obvious that it’s memory. Not to mention ReBAR/SAM is always on in games for AMD whereas nvidia uses a per game whitelist to enable it so little wonder a RAM issue could show itself as GPU/driver issues. And now I’m rethinking if my ghost of tsushima memory leak issues were related to that and not malwarebytes like many people claimed.
But I’m typing too much and not testing the game like I should so I’m off to do that.
Trying this doesn’t fix it. A radeon driver timeout notification pops up but the game still runs.
Bumping memory voltage a bit doesn’t fix it so I may raise it a bit more and/or run some memory tests. It may have been causing issues with other things so it’s still good to check out but at the moment it’s still up in the air if it’s causing the shield bug.
I think you’re very likely barking up the wrong tree with mem voltage but it’s not long to test (well full mem test can be). Unstable mem is very unlikely to cause the issues, or be the source of your mem leak messages, odds are you’d have more serious issues across the board too.
It’s very likely an AMD driver glitch (and/or DT), probably related to transparency/fx shimmer if I had to make a wild guess. You could try underclocking GPU/VRAM (video mem) speeds as test rather than main system stuff.
I’m going to assume you tried other stuff like toggling HAGS since you were messing with ReBar. Other long shots like “Graphic Options” in windows and voodoo like CFG exploit protection whitelist (which is typically a stutter fix for some games for some users)
That’s why I wanted an AMD use to test out the update disable mod to maybe narrow it down. I have no dog in the fight but maybe I can offer a work-around via a simple mod.
P.S. There’s already a mod to at least disable the bugged VFX
I’ll try the shield update disable mod you gave above later, though i have no experience with modding besides swapping in newer upscaler dll files. Running the full mem test and walked away at the moment to be productive. On the plus side if there’s no issue with memory I can try toggling the low latency mode in bios for a bit more performance.
Fun side effect of my ADHD being medicated now. If I see something that I suspect is causing a problem I now have enough willpower and dopamine to hyperfocus on it and test and try things again and again until proven otherwise.
I don’t have a nexus mods account to download stuff with so I put off trying the mod but I did finally come across the partial effect on the shield again. Note how it gets much more noticeable with the pulsing shield effect
Oooh interesting!
Try my tiny mod I linked for you (no nexus needed, linked here in forums) ? Your video may have confirmed my hunch, maybe partially; it may fix it.
It might be tied to impacts or both.
Ah, by that I mean I can’t get the mod loader/framework stuff. I dislike needing accounts for everything these days but I’ll just bite the bullet and do that later tonight.
Also some of my clips are too big to post here until I cut them or lower quality but it persisted after I loaded out of mission, swapped to psyker and went to the psykanium. The effect was consistent on the shield through the mission as far as I could tell, again seemingly confirming that it’s something happening between mission loading screens (or at least loading out of mission. I should have done one more mission to verify).
The effect was more intense when testing in the psykanium but still didn’t cover the entire shield which was interesting! Normally it goes from nothing to covering the whole shield. I also confirmed that the partial effect also effects the smaller wall shield (and likewise gets more wobbly when about to vanish.
One odd thing that I saw momentarily in mission but didn’t get a shot of was when the shield was used near a jump down. The lower part of it that’s normally in the ground had the corruption effect all the way around it, almost like there’s a rainbow ring of “fire” of sorts bubbling up the side of the shield.
Also thanks for this. Once I test it I’ll probably compile everything together in a new tech support thread for the devs to see easier.
Oh right, derp, the other stuff.
You can also grab the mod loader straight from github skipping NexusMods as explained from the old guide.
Nexus mentions them in the [Mirrors] sections usually.
For DMF, only the DMF folder and its contents is of interest, download the zip and extract/copy the DMF folder to the DT Mods folder as in the guide.
I forgot to get a clip but it doesn’t fix it. The effect just doesn’t wave upwards like it does normally.
Hmmm…try this real quick? It should disable additional shield effects including impacts (so no decals if any? ).
ForceFieldFixer (2).zip (14.5 KB)
P.S. I haven’t really looked yet, is there a decal applied to shield that’s moved when updating shield health? Is that what was static via mod you tested?
Does reducing this change behavior? Or is is the base VFX that moves upwards so fundamental issue?
Normally the shield starts with a lighter blue effect, slowly shifts to a darker blue and starts a wobbling effect when low on health/time. The first mod sets the shield automatically to the darker blue wobble effect. Slight change to what I said above, it does still show the scrolling up effect but it’s harder to notice with the modded glitch due to the wobble always being there. I got some clips of a before and after (again with the partial effect, neat)
Unmodded effect:
Mod 1 normal:
Mod 1 glitched:
I hadn’t considered that it could be a decal but I’ll give it a shot. Now I’m wondering if it’s a shader that just isn’t coded right for AMD or doesn’t play well with AMDs drivers.
I’ll give the second mod a shot and see how that goes (unless I put it off because Ys X: Nordics is out today). It’s the weekend and the fatshark people are probably off until monday so I’m not in a rush to make a tech support post about all of this yet.
Prob not decals methinks, holy is that obnoxious though to see in vid form.
Must be a base VFX issue, guess replacing it with something non-buggy or disabling it completely is the way to go for AMD.
I do know someone with an RX 6800 that had very old drivers on it and never saw the bug so it’s probably something to do with a change in the drivers sometime the last year. Now that they’re updated I should ask if it happens. I found a reddit thread of someone with the same issue with a RX 5500 too so if it effects 3 generations of cards I’m leaning towards a weird driver problem/interaction
Yep, saw that thread and replied in it. Been following these threads out of interest hoping to stumble on some good info and maybe some better workarounds.
Luckily for you you came across someone upset enough to do something about it
@Slaughterhaus @Shajirr @AccountMadeToReply @Daskard
This is going to sound crazy but turn off Anti-Lag for Darktide in your AMD software.
I never tested it because I thought there’s no way that could be it but I turned it off and I haven’t had the shield glitch for a day now. I’m pretty confident that this is it because it fixed it for me and a friend (also already put it in my tech support thread so the devs know) but I want y’all to try too to be sure.
Just remember that if you change your global gaming profile but you’ve changed Darktide’s gaming profile separately it won’t follow the global profile. As an example, see how on mine Darktide says custom but that’s not the same as Global Experience (Custom).
If any of you use the HYPR-RX or Quality presets then keep in mind that Anti-Lag is on by default in those and you’ll have to change either your global profile if Darktide uses it or change Darktide to default or customize Darktide’s profile directly.
I will give this a try, and also disable my mod that makes the shield invis to see if i ever get the bug again, thanks
