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 1
  • 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

×
×
  • Create New...