Jump to content

Update the DLSS preset used by DCS to remove ghosting


Go to solution Solved by BIGNEWY,

Recommended Posts

Posted
18 minutes ago, Nighthawk 117 said:

After todays patch if you have the Nvidia App you can now select the preset on there 

nice. i see that now. thanks for the tip. 

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

Posted
4 hours ago, Nighthawk 117 said:
4 hours ago, Nighthawk 117 said:

After todays patch if you have the Nvidia App you can now select the preset on there 

No longer required either. Add the below line to your C:\Users\Saved Games\DCS\Config\autoexec.cfg file (create it if it doesn’t exist) to set the preset for DCS

DLSS_Preset = "K"

You can add this line as well if you don’t want DLSS applied to MFDs and HUD to keep them sharp with no ghosting for greater control.

HUD_MFD_after_DLSS = true

 

  • Like 3
  • Thanks 1

AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2

Posted
3 hours ago, sleighzy said:

You can add this line as well if you don’t want DLSS applied to MFDs and HUD to keep them sharp with no ghosting for greater control.

HUD_MFD_after_DLSS = true

 

Is there any downfall / sideeffects to using this? Does it take up more GPU or CPU resources? (Just wondering why this isn't done by default with DCS and/or why this is hidden away to implement instead of being standard and what I should be aware of before implementing it). 

  • Like 1
Posted (edited)
2 hours ago, Dangerzone said:

Is there any downfall / sideeffects to using this? Does it take up more GPU or CPU resources? (Just wondering why this isn't done by default with DCS and/or why this is hidden away to implement instead of being standard and what I should be aware of before implementing it). 

May be minutely GPU hit compared to using nothing at all. Yes, this is “hidden” away (should have been better documented in release notes). The second option is not everybody wants DLSS for MFDs due to the ghosting it can cause with cursors etc on radar screens and other things. I reckon it’s a great addition and compromise.

Youre right though, it could have defaulted to K instead of C and people could override if they wanted to. The K (and J) presets are going to be a little less performant than some others. 

Edited by sleighzy

AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2

Posted
7 hours ago, sleighzy said:

You can add this line as well if you don’t want DLSS applied to MFDs and HUD to keep them sharp with no ghosting for greater control.

Haven't tested yet but I suspect it might leave it with no AA which makes it clear but aliased and shimmering.

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted

I have the latest GeForce v. 576.52 drivers installed. nvngx_dlss.dll v. 310.2.1.0 file. Regardless of whether I use the 'K' preset in the NVIDIA application or use the entry in autoexe.cfg, I still experience ghosting when using DLSS.

Does anyone have any ideas where the problem might be?

 

223750_20250525140755_1.png

223750_20250525142501_1.jpg

223750_20250525144836_1.png

baner.jpg

Posted
33 minutes ago, Raffi75 said:

I still experience ghosting

Ghosting is normal part of every temporal AA method. They can only reduce it. If you can't live with the effect you have to go with other AA tech.

  • Like 1

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted

@draconus Thanks for the reply. I thought I was doing something wrong or messed up the settings. It doesn't bother me much. I got interested in it because it's been a hot topic lately. 😉

baner.jpg

Posted
1 hour ago, Raffi75 said:

I have the latest GeForce v. 576.52 drivers installed. nvngx_dlss.dll v. 310.2.1.0 file. Regardless of whether I use the 'K' preset in the NVIDIA application or use the entry in autoexe.cfg, I still experience ghosting when using DLSS.

Does anyone have any ideas where the problem might be?

 

223750_20250525140755_1.png

223750_20250525142501_1.jpg

223750_20250525144836_1.png

The only only way to get rid of it (that I have found) is to push resolution as high as possible. I see you have a quest 3. Have you tried using Quad Views Foveated Rendering? I push the foveated resolution up to about 5000 pixels (equivalent) and this virtually eliminates ghosting. 

PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

IMG_0114.jpeg

 

Posted
16 minutes ago, Qcumber said:

The only only way to get rid of it (that I have found) is to push resolution as high as possible. I see you have a quest 3. Have you tried using Quad Views Foveated Rendering? I push the foveated resolution up to about 5000 pixels (equivalent) and this virtually eliminates ghosting. 

I don't use VR goggles, I don't know what you were suggesting. Could you write this in a clearer way? For someone who has no idea what you're talking about. 😀

baner.jpg

Posted
12 minutes ago, Raffi75 said:

I don't use VR goggles, I don't know what you were suggesting. Could you write this in a clearer way? For someone who has no idea what you're talking about. 😀

Sorry. I looked at the wrong signature.  Ignore me. 

PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

IMG_0114.jpeg

 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...