Jump to content

Update the DLSS preset used by DCS to remove ghosting


Go to solution Solved by BIGNEWY,

Recommended Posts

Posted (edited)

The DLSS option in DCS is more performant than MSAA, however has a side-effect of ghosting. The DLSS library itself supports a number of presets for varying graphics qualities/performance. DCS appears to set preset C. A number of DCS users currently use the DLSSTweaks tool (https://github.com/emoose/DLSSTweaks) to override this preset value. A commonly recommended one, at least within the VR community, is preset F which has great performance, image clarity, and removes the ghosting which is otherwise seen with preset C (even when using the Quality mode).

Could this be investigated and potentially the default preset used by DCS to be updated to remove the current ghosting that is experienced. Would be good to evaluate the preset with both 2D and VR, as if the experience is much better for VR users, but has no change for 2D users, then a direct change of this should have minimal impact on users across both platforms.

For anybody wanting to test this themselves; follow the instructions on the link above, and then rename the DLSSTweaks "nvngx.dll" placed in the DCS bin and bin-mt directories to "dxgi.dll". Set the DLSSPresets to F in the dlsstweaks.ini file, place this in the bin and bin-mt directory as well, and then start DCS and use DLSS. You should see the dlsstweaks.log file created in the bin or bin-mt directory. Additionally if you enable the DLSSTweaks debug overlay you should see this as per the screenshot. You should see less ghosting when using DLSS. Similar config exists within that config ini file for using with DLAA instead of DLSS.

EDIT: A more simplified approach to configuring this, will apply to all games using DLSS, is to use DLSSTweaks to set this preset globally within the Nvidia Global Profile. This means you don't need to place the dll file and ini file (or update it) in the DCS/bin-mt directory. Instructions as follows:

1. As per the previous instructions, download the DLSSTweaks.zip file from https://www.nexusmods.com/site/mods/550?tab=files

2. Unzip this and then run the DLSSTweaksConfig.exe file. This requires administrator permissions, but will prompt you and run if you don't

3. Set the GlobalForcedPreset to F (or preset of choice) as per the screenshot and save changes

Set GlobalHudOverride to Enabled (all DLLs) to display the debug overlay that will show the preset currently in use.

 

Update 11/14/24: The latest release of the DLSS library (3.8.10) has removed all other presets except for E and F. If you just replace the DCS nvngx_dlss.dll file in the bin and bin-mt directories then DCS will now by default use preset E for the Performance, Quality, Balanced without any overrides. The "Ultra Performance" option will select preset F, however this will mean lowered graphics clarity so you will need to use DLSSTweaks to enable preset F for the "Quality" or other options.

 

image.png

image.png

Edited by sleighzy
Update comment on the Ultra Performance option for preset F
  • Like 11
  • Thanks 5
Posted

Thank you for this thread! DLAA now looks as it should from the start. But... Another 3rd party soft for DCS to look as it should. It is rally hard to keep everything updated.

Wysłane z mojego VOG-L29 przy użyciu Tapatalka

  • Like 1

PC: i7 13700k, 64GB RAM 3200MHz DDR4, SSD M.2 Drives, RTX 4090, VR: Quest 3.

VPC MongoosT-50CM2 Grip, VPC MongoosT-50CM3 Throttle, crosswinds rudder pedals, VPC panel CP3, WinWing PTO2

 

Posted

Good to hear.

I believe the default setting can also be changed in the Nvidiaprofileinspector tool. I've only seen the option but never tried it, so I can't give any feedback on its effectiveness.

Posted

Ohhh, it would be awesome if many of the things we have to do to DCS were just options in the DCS Options settings.

Like 2K Apache/other aircraft/object textures. SceneVR.lua settings to change the aircraft in the hangar or even the hangar to something else, mod management similar to how ARMA handles them (built in Open Mod Manager/OVGME/etc), the list goes on!

  • Like 3
Posted
14 hours ago, Cab said:

Good to hear.

I believe the default setting can also be changed in the Nvidiaprofileinspector tool. I've only seen the option but never tried it, so I can't give any feedback on its effectiveness.

Thanks for that, I'll see if I can find it again, previous references had been modifying XML files for it. The DLSSTweaksConfig tool provides an option in that screen as well for updating the Nvidia Global Profile to use the preset across everything. I'll have to give this a go to confirm, but at least simplifies the config (as long as folk don't care about it applying to every game).

  • Like 1
Posted

Tried this last night for the fun of it. It works quite well. The majority of ghosting with DLSS is gone ( significantly reduced). 

  • Like 2
  • Thanks 2

Intel i7 13700k, ASUS  rog strix z790A, 64gigs G.Skill Trident DDR5 @6400Mhz, Nvidia  RTX 4080FE, 2x 2TB Samsung M.2 NVME, 2x 1TB Samsung SSD,  Corsair RM1000x, Corsair Titan 360 X AIO cooler, Lian Li LanCool 2, VKB Gunfighter Ultimate, VKB STECS , MFG Crosswinds, Track IR5, 48” LG UltraGear OLED & HP 24” touchscreen for Helios, Streamdeck XL, DCS-UFC App, Corsair Virtuoso RGB Headphones

Posted

I've updated the instructions for using DLSSTweaks to set this preset globally in the Nvidia global profile. Removes a number of steps for placing updated dll and ini file in the DCS\bin-mt directory. Note, the preset will apply to all DLSS games if this approach is taken, and not all additional fine-grained config will be possible. Not a big deal when looking to achieve these results in DCS.

Posted

Does the DLSSTweaks.zip need to be extracted to bin-mt folder, or can I just extract to desktop and run the .exe and apply to all games on my PC?

Also, will I need to run this .exe each time I play DCS?

Thank you

  • Like 1
Posted

I run DLAA and so far this has HELPED the ghosting.  It is still noticeable but much better.


I like DLAA the best, but I wish I could "sharpen" the graphics a bit.  It looks just a little bit too soft IMO

  • Like 2
Posted (edited)
1 hour ago, BlackReef said:

Does the DLSSTweaks.zip need to be extracted to bin-mt folder, or can I just extract to desktop and run the .exe and apply to all games on my PC?

Also, will I need to run this .exe each time I play DCS?

Thank you

You can extract it to the bin-mt folder if you just want to just have it wrap DCS and apply settings for DCS only (note you'll need to rename the `nvngx.dll` to `dxgi.dll`). Otherwise, yes, just extract to your desktop and use the second approach. No, don't need to run each time, the exe file is just used to update the config in the .ini file. Only need to run again if you're wanting to play with other settings, e.g. try preset F and then update it to try with preset E, or play with DLAA instead.

Edited by sleighzy
  • Like 1
Posted
20 hours ago, gonvise said:

Hi, so far I only replace nvngx_dlss.dll in the /mt-bin directory with the latest version from

https://www.techpowerup.com/download/nvidia-dlss-dll/

, and within DCS I select DLAA. What is the default profile without using dlsstweaks?

The DLAA preset? That I don't know sorry. The debug overlay only shows preset C as the default, even when I'm using DLAA, so I'm presuming this information is based on DLSS. Various comments on the internet (not everything can be believed of course) is that the standard defaults for the library prior to 3.7 (not saying that this is what DCS does, but may be why it is C for historical reasons 🤷‍♂️) are F for DLAA and C for DLSS. The DLSS default changed to E in DLSS 3.7, unless being set to something different by the game. I'll drop an update if I find anything further out.

  • Thanks 1
Posted (edited)

Preset E was the shiny new one that was introduced in DLSS 3.7 as the default for games. I'm a VR user and have tried both, but honestly couldn't say which was better than the other. Would be curious how people find E vs. F, especially with higher end headsets or 2D, as to whether or not one is noticeably better than the other to get some more informed decisions if this was to be changed within the game permanently. Some internet comments are that E is smoother than F, although the ones I've run across are for 2D and games other than DCS.

Edited by sleighzy
Posted
8 hours ago, sleighzy said:

You can extract it to the bin-mt folder if you just want to just have it wrap DCS and apply settings for DCS only (note you'll need to rename the `nvngx.dll` to `dxgi.dll`). Otherwise, yes, just extract to your desktop and use the second approach. No, don't need to run each time, the exe file is just used to update the config in the .ini file. Only need to run again if you're wanting to play with other settings, e.g. try preset F and then update it to try with preset E, or play with DLAA instead.

 

Thanks! Yea I extracted the software to the bin-mt folder and run the .EXE and selected the "F" preset.  I am happy with the changes, although I did not rename the nvngx.dll to dxgi.dll?  I just extracted the files and ran the .exe.  I guess if I am happy with the results I shouldn't mess with it lol

 

Thanks again

Posted

Thanks for this. Just going to give my experience for what it is worth.  I tried forcing Profile E and F.  Couldn't really tell much difference graphically, but I did seem to see a decrease in Frame Rate with both E and F.  For now, I'm sticking with the default as the best compromise.  I got rid of most of my ghosting (and got a lot more stability) by moving from 90 Hz to 72 Hz (Quest 2, RTX 3070) so thankfully that was no longer an issue.  Of course there are endless things to tweak and it is nice to have this additional option. Using DLSS Quality in DCS, currently so maybe moving down to BALANCED and changing DLSS profiles is something I am going to try.

Posted
5 hours ago, BlackReef said:

Thanks! Yea I extracted the software to the bin-mt folder and run the .EXE and selected the "F" preset.  I am happy with the changes, although I did not rename the nvngx.dll to dxgi.dll?  I just extracted the files and ran the .exe.  I guess if I am happy with the results I shouldn't mess with it lol

 

Thanks again

Did you select "F" for the global nvidia option, or "F" for all the individual preset options? If global then yeah, the nvngx.dll rename probably not needed as it won't look at that.

  • Like 1
Posted
1 hour ago, Recluse said:

Thanks for this. Just going to give my experience for what it is worth.  I tried forcing Profile E and F.  Couldn't really tell much difference graphically, but I did seem to see a decrease in Frame Rate with both E and F.  For now, I'm sticking with the default as the best compromise.  I got rid of most of my ghosting (and got a lot more stability) by moving from 90 Hz to 72 Hz (Quest 2, RTX 3070) so thankfully that was no longer an issue.  Of course there are endless things to tweak and it is nice to have this additional option. Using DLSS Quality in DCS, currently so maybe moving down to BALANCED and changing DLSS profiles is something I am going to try.

I don't know what your fps is, but if dropping to 72 Hz means that you're now able to meet that refresh rate within the game then it's possible that ASW (Meta Quest's motion-smoothing) isn't kicking in now. If you can't meet the refresh rate, e.g. previously 90 Hz, then ASW will cut your frames in half and inject "fake" frames which can cause some artifacting (may look like a bit like ghosting in the game).

Posted (edited)
1 hour ago, sleighzy said:

I don't know what your fps is, but if dropping to 72 Hz means that you're now able to meet that refresh rate within the game then it's possible that ASW (Meta Quest's motion-smoothing) isn't kicking in now. If you can't meet the refresh rate, e.g. previously 90 Hz, then ASW will cut your frames in half and inject "fake" frames which can cause some artifacting (may look like a bit like ghosting in the game).

ASW is OFF in OTT....  In the Menus, I get 72 FPS (and got 90 when set to 90 Hz).  In the mission I used for Testing...  Various aircraft taking of from Melez on the Sinai map,  I get about 50-60 FPS at the default, about 25-35 at Preset F and about 35-45 with Preset E.  Everything else remains the same. Using OTT and OXRTK, so there is room for tweaking, but for the purposes of the test the DLSS preset was the only variable. ASW should not be kicking in at all, but when it was on, indeed I get about 50% of the set Hz (at max).

Edited by Recluse
Posted

Good find I'll test this . 

Gigabyte - X570UD ~ Ryzen - 5600X @ 4.7 - RTX-4070 SUPER -  XPG 32:GB @ 3200 - VKB - Gunfighter 4 - STECs - Throttle - Crosswinds Rudders - Trackir 5 .

I'm a dot . Pico Nero 3 link VR . @ 4k

Win 11 Pro 64Bit . No longer Supporting DCS . 

Posted

Whats the status on this? I'm curious as DLSS/DLAA was ghosting, it went away with a patch, then came back? Do I use the newest DLL file? Tweak settings... do both? 

  • Like 1
Posted (edited)
24 minutes ago, Sigma6 said:

Whats the status on this? I'm curious as DLSS/DLAA was ghosting, it went away with a patch, then came back? Do I use the newest DLL file? Tweak settings... do both? 

Status is nothing has changed from the DCS end. Doing both won't hurt, grab the latest one from here, it's up to 3.7.20 at the moment https://www.techpowerup.com/download/nvidia-dlss-dll/ . You'll still need to update your Global Nvidia Profile (via DLSSTweaks) to set it a better preset (E or F) to reduce ghosting though.

Edited by sleighzy
  • Recently Browsing   0 members

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