Extremely glitchy graphics with DLSS 3.7 plugin in shipping build from UE 5.4.2 game

Gaming and Visualization Technologies DLSS
1

Hi,

I am using the UE DLSS plugin for 5.4.2 (plugin version). Under certain conditions, sometimes DLSS will cause the players screen to flicker back and forth between a proper upscaled image and an extremely glitching image where the bottom and right of the screen are completely distorted. This issue is quite rare and seems to affect <3% of players.

It looks as though the upscaling failed to draw and it is drawing the non-upscaled version starting at the top left of the screen and then the bottom and right edges are a garbled mess. The menus and UI are not effected.

Swordai Screenshot 2024.06.15 - 08.21.41.62
Swordai Screenshot 2024.06.15 - 08.21.41.621920×1080 123 KB

It does not happen on all hardware, but is reliably reproduceable on my laptop 3080 card with a 1440p/240hz monitor and several players have reported the same issue (one using a desktop 4080). The screen shot from above is with the game ready driver 555.99, a windows shipping UE 5.4.2 build, a laptop 3080, and a 1440p/240hz monitor running the game at 2560x1440 with the DLSS upscaling at 71% like this:

LogDLSSNGXRHI: Creating NGX DLSS Feature SrcRect=[0x0->1818x1023], DestRect=[0x0->2560x1440], ScaleX=0.710156, ScaleY=0.710417, NGXDLSSPreset=Default(0), NGXPerfQuality=MaxQuality(2), bHighResolutionMotionVectors=1, bNonZeroSharpness=0, bUseAutoExposure=1, bEnableAlphaUpscaling=0, bReleaseMemoryOnDelete=1, GPUNode=0, GPUVisibility=0x1, DenoiseMode=Off

This glitch is resolved by disabling DLSS. It also often goes away if the user caps their framerate at a lower value, changes the DLSS quality setting to ultra performance, reduces the overall graphics quality of the game, or disables reflex mode. The glitch does not occur in a development build.

Restarting the game sometimes fixes the problem and the problem seems far more common the first time the game is launched. Any help or advice on how to fix this is greatly appreciated.

1 Like
2

This glitch also occurs in our projects.
It is only occurring on DX12.
I am using RTX4060 Ti.

I would like to know if there is a solution to the glitch.

3

Thank you @yatagai for chiming in and welcome to the NVIDIA forums.

And thanks to both of you for bringing this to our attention.

I made the engineering team aware of this, let’s wait for their feedback.

Thanks!

1 Like
4

Any updates on this?

5

We’ve been noticing this periodically, and there was a large uptick in occurrences of this issue recently.

In my local test case, it seems to be much less of an issue with 552.44 (Nvidia GeForce Game Ready Driver).

555.85 and after seem to have considerably more reproduceable flickering.

6

We are still running into this issue with latest drivers. Any updates on this?

7

For anyone running into this issue: It seems related to separate translucency. Disabling it gets rid of the glitches for us.

3 Likes
8

This did work for me. I haven’t noticed that setting change introducing any notable visual changes yet but testing out everything in the game is difficult. Did you guys notice any visual issues that were introduced when you changed the setting?

9

Separate translucency affects the way translucency is drawn. As the name suggests, if enabled it is done as a separate pass and can be composited into the final result before DOF or after it, or even after motion blur has been applied. One other benefit of doing the translucency pass separately is that you can reduce the screen percentage of the pass, making the translucency pass cheaper. That being said, we did not really utilize any of that functionality at this point so we did not have any negative impact by disabling it. Ideally though a proper fix would be provided

10

Still have the same issue, game Empire of Ants, 4090, driver 566.03-desktop-win10-win11-64bit-international-dch-whql.exe

Happens with DLSS max quality, regardless of frame generation on/off.

Does not happen if select TSR option in the game.

11

Since the problem here occurs in TAA without DLSS plugin.
It is probably a bug in UnrealEngine.
I am currently contacting them via UDN.

FTranslucencyComposition::AddPass()
FTranslucencyComposition::EOperation::ComposeToExistingSceneColor
is specified, it is possible to avoid this problem.

12

Same as you, it occurs even if I turn off the DLSS plugin.

13

I’m having the same issue on several newer games. It happened recently on Empire Ants and Sengoku Dynasty.

14

did you make any progress with UDN on this? Interested to hear any developments you may have found out?

15

No particular progress has been made.
I received a response that a custom UE would not be supported.

16

We had this issue on my game as well. While I wasn’t able to repro it on my machine, I had a few team members who could. I was able to solve it for them by trying a few different things.

  1. Find out what material is causing it (most likely a translucent material)
  2. Remove Front Layer Transparency
  3. Add a near fade to the material and use WPO to keep the polygon away from the camera
  4. I also change to After DoF (I dont think its needed)

After I implemented those changes my team was no longer able to repro this issue.