We have integrated the latest DLSS plugin into our Unreal Engine 4.27 project to make use of the improvements to Anti-Aliasing and Performance. However during this integration, we have encountered an issue with moving objects leaving behind ghosts/trails.
The following settings have been validated:
r.DefaultFeature.Antialiasing 2
r.TemporalAA.Upscaler 1
r.Reflections.Denoiser 2
r.BasePassForceOutputsVelocity 1
r.NGX.DLSS.DilateMotionVectors 1
r.NGX.DLSS.AutoExposure 1
Using the Debug overlay, we noticed that we had yellow colored interior offsets when looking at the jitter offset debug. We realized that the default r.TemporalAASamples 8 was not sufficient, so we changed it to r.TemporalAASamples 16. This did not seem to have an effect on the ghosting/trailing we see.
We have tried different combinations of disabling DilateMotionVectors, AutoExposure, BasePassForceOutputsVelocity.
We have also downloaded and built the NvRTX 4.27.2-4 version of the Unreal Engine from the NvRTX/UnrealEngine Github. We have had no improvement to the ghosting/trailing issue with the custom engine or any of the other settings that were suggested by the documentation provided with the plugin.
Is this a known issue of DLSS for Unreal Engine. Does anyone have any suggestions or workarounds that might work to alleviate the issue?
Hello @tclements1 and welcome to the NVIDIA developer forums!
It is really unfortunate that you are seeing ghosting in your project with DLSS. To get you started and before the experts chime in, did you see the FAQ for Unreal and DLSS, in particular the question about ghosting? While it is too much to hope that this fixes your problems, it still is worth a shot.
Can you please also find out which version the DLSS DLL has that you installed as part of the plugin?
Yes, I have tried the suggestion that was in the FAQ about using r.BasePassForceOutputsVelocity, this did not solve the issue.
The version of the DLSS DLL is 2.3.11.0, this DLL comes from the latest plugin for UE4.27 provided from the DLSS Nivida Download page, Get Started | NVIDIA Developer
I wanted to add that I sent an email that contains the same information, plus a few videos to nvrtx-support@nvidia as recommended from Epic Employees on Unreal Developer Network, and DLSS-Support@nvidia. These emails were sent around November 1st, 2022, when neither of the emails got any replies, I decided to create this forum post.
Has there been any movement on one of the experts chiming in? This is the primary issue we are experiencing when using DLSS, and is what is keeping us from moving forward with the DLSS implementation.
Our GTC Fall last week has kept people really busy, so it might take a while for an answer. But now this should pick up again and I will also reach out to engineering again.
Thank you for the suggestion, but it did not fix the issue. Before originally posting on the forum, I had tried different combinations of enabling/disabling the following commands with no improvement to the ghosting/trailing.
We are having a very similar problem. We use the latest DLSS plugin with UE5.0.3 and have severe ghosting. We tried many things without success. We emailed dlss-support@nvidia.com too, but got no reply.
We reproduce this ghosting problem with the simplest scene. I suspect this is a well known problem at nVidia. A status from the dev team would be appreciated.
DLSS 3.1.1 DLL version by default chooses “preset D” for DLSS Quality, Balanced, and Performance modes for most games, and apparently, this preset still has issues with object ghosting in quite a number of games. It often seems to occur when e.g. NPCs start moving again after standing still for a while. “Preset C” usually doesn’t show this issue.
Really hope “preset D” can be made less prone to this issue with future DLSS updates.
And on a different note, reduced “smearing” for thin object edges (e.g. flying birds) would also be nice.
Sorry that it has been rather silent in this thread. There were several sets of optimizations to DLSS over the last couple of months, addressing apart from other things also Ghosting in different scenarios. But it seems to be in the nature of the problem that it is hard to get 100% coverage for all possible combinations of content.
Development continues and you can expect improvements in the future. And any and all feedback on quality issues are welcome and will be passed on to the development team.
