I’m getting a weird flickering and ghosting with my viewport. This is happening in all my maps I believe. I’ve tried turning a bunch of things on and off methodically to no avail.
The only thing out of the ordinary I have done recently is enable the Procedural Texture plugin, messed around with the graph, and then disabled it. Never saved any textures or anything, just played around.
Here’s another screen cap of weird things that Rect Lights are doing. They almost seem like they’re behaving in screen-space if that makes sense.
UPDATE: Immediately after my original post, Nvidia released new Studio Drivers, I updated them and now the problem has stopped. Will update again if it continues.
UPDATE 3: I downgraded my Nvidia drivers to earlier ones and it fixed the problem! I currently have Version 551.86 installed, which fixed the problem, it might be safe to upgrade to the latest now, but it’s running perfectly so no need to upgrade right now.
This happens when I have multiple static or movable rect lights with large or overlapping attenuation radiuses. I understand stationary lights should not overlap more than 9 times (I think), and I have 30 of these. Is the issue related to that somehow?
If I set my lights to static, the problem goes away… Which is fine if you want static lights, but they produce terrible shadows compared to static or mobile lights with ray traced shadows and they do no illuminate the scene as well (could be user error on my part).
I also had the same problem. It was recommended by a developer in a similar post to use old drivers. I’m using Studio Driver 552.22 (4/16/24) and the problem hasn’t recurred again.
I had the same problem on the version ue5.3.2 and I uninstalled this version now installed ue5.4.2 but the problem remained rect lights still flicker and sometimes there are ghost flickers…
I just randomly started getting the ghosting artifacts again even with my still downgraded GPU drivers, so if anyone finds this, I highly recommend just using the
r.Shadow.Denoiser 0
console command. Maybe Nvidia will fix the problem eventually.
One way to make sure the variable is always enabled is to create a Console Variable Collection in your Content Browser and add the variable, this is a good way if you don’t want to edit console variables in the project folder text files.
Has there been an updates to this problem? We tried the console variable but it did not help.
Should it just be about running it in the Cmd in the editor like normal?
Reverting to the older drivers DID work, but won’t work as a proper solution when this is deployed
