Jump to content

Update the DLSS preset used by DCS to remove ghosting


Go to solution Solved by BIGNEWY,

Recommended Posts

Posted

310.2.1.0 is not in DLLS Swaper at the moment. 

Have any of you tried the K preset of the new drivers that is supposed to improve the J?

  • Like 1
Posted
8 hours ago, gonvise said:

310.2.1.0 is not in DLLS Swaper at the moment. 

Have any of you tried the K preset of the new drivers that is supposed to improve the J?

Try clicking the Refresh button in DLSS Swapper, is there for me and others.

  • Like 1
  • Thanks 1

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

Posted

Fun fact somebody pointed me at, works a charm. Just use the Nvidia Profile Inspector (no additional custom settings xml file) and set the DLSS-SR override to 1 and the DLSS-SR preset to your choosing, e.g. 0x00FFFFF is latest which is K now, and you don't need to swap dlls anymore. The driver just provides the requested preset and ignores the dll in the DCS folders. Can leave the crusty DCS 3.7.0.0 dll in there and still get K.

null

image.png

  • Like 2
  • Thanks 3

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

Posted
On 1/23/2025 at 9:43 PM, sleighzy said:

Been playing with this DLSS 4 today. Downloaded the nvngx_dlss.dll file (there are links available in other comments and the Reddit post) and replaced in the DCS bin and bin-mt directories. First thing noticed (was also mentioned in the comments on the Reddit post) was that the old presets have been reintroduced. Tested this by ensuring I was using the default preset. This meant that DCS started using the old Preset C again, v.s. the E we got with 3.8.10 (if you didn't override it). Because of this you can't just switch the dlls and get what you used to. Perhaps the new C is better...., but I don't care. Secondly, DLSSTweaks couldn't be used to override it from C to J.

So, installed Nvidia Profile Inspector from here nvidiaProfileInspectorForkAIO (.Net.Framework version) so that the DLSS override options are available in the config screen. The new Preset J did not show up for me in the dropdown of available presets, some folk have mentioned that it did for them, maybe it does for you too. I updated the CustomSettingsNames.xml file that comes with Nvidia Profile Inspector to add this new option instead. Search for the other presets and then add the below entry, see screenshot as well.

 

    <CustomSettingValue>
	<UserfriendlyName>Preset J</UserfriendlyName>
	<HexValue>0x0000000A</HexValue>
    </CustomSettingValue>

The Preset J option is now available in the dropdown.

Turned on the debug overlay (I use DLSS Tweaks for this) and jumped in a plane. Confirmed that the overlay showed the correct DLSS 310.1.0 version (weird number) and was using preset J

Ghosting was gone from MFDs, and everything looked really crisp. Flew in formation with another plane and did not experience the normal ghosting/blurring I used to around their wings and other areas. The blurring around wings etc. used to be present even with later DLSS versions and on presets E and F so this was a vast improvement.

It's more of a performance hit, I have a decent machine but could feel it a little bit. Tested changing the DLSS setting from Quality to Ultra Performance, and this still felt better than Quality with the previous DLSS version. The Performance setting was pretty much the same.

Final outcome, I highly recommend this and will be staying with this.

EDIT 31/01/25: Bunch of tools got updated last couple of days to better support this, and fix some bugs. I'm now using the following only:

  • DLSS Swapper: The latest version of this added support for manually adding games. I added the top level DCS game folder so it automatically swaps the dlls in both the bin and bin-mt folders for me.
  • DLSSTweaks: Now supports setting the J and K presets as well. Whilst I use this to override the Nvidia Global Profile, it also contains a fix to preventing crashing for people who use the dxgi.dll wrapper approach with it.

image.png

image.png

image.png

For us DCS users is this the preferred method to modify DLSS settings vs the new NVidia App?

Posted
38 minutes ago, greyeagle787 said:

For us DCS users is this the preferred method to modify DLSS settings vs the new NVidia App?

 

Would be good if we could. I had a go and couldn't see an obvious way to do it.

7800x3d, 5080, 64GB, PCIE5 SSD - Oculus Pro - Moza (AB9), Virpil (Alpha, CM3, CM1 and CM2), WW (TOP and CP), TM (MFDs, Pendular Rudder), Tek Creations (F18 panel), Total Controls (Apache MFD), Jetseat 

Posted (edited)
13 hours ago, sleighzy said:

Fun fact somebody pointed me at, works a charm. Just use the Nvidia Profile Inspector (no additional custom settings xml file) and set the DLSS-SR override to 1 and the DLSS-SR preset to your choosing, e.g. 0x00FFFFF is latest which is K now, and you don't need to swap dlls anymore. The driver just provides the requested preset and ignores the dll in the DCS folders. Can leave the crusty DCS 3.7.0.0 dll in there and still get K.

null

 

The new 2.4.2.3 Profile Inspector (NVPI-Revamped) shows it a bit differently..

 

null

image.png

Edited by GPatricks
  • Thanks 1

GIGABYTE X870E AORUS Elite WIFI7, Thermaltake 1200w PS \AMD Ryzen 7 9800X3D - Corsair iCue Titan Liquid CPU cooler \ 64GB G.Skill Z5 DDR5 \ SBlasterX G6 \ 4TB NvMe M.2 Boot Drive \ Zotac GeForce RTX 4090 Trinity 24GB - Nvidia 576.02 drivers \ 3 Samsung LC32G53TQWUXEN 32" 7680x1440 at 144Hz Gsync \ Win11 Pro Ver. 24H2 - Build 26100.3775 \ TIR 5 \ Warthog HOTAS  with VirPil stick base \ MFG V3 Pedals \ TM MFDs  on 2 8" Lilliputs \ Simgears ICP \ Varjo XR-3 VR

Posted

I've tried preset J as well as K, and while the visuals are definitely much sharper, the loss in performance was too much for me to absorb. My flights over Syria and South Atlantic went from buttery smooth to a stutter fest. It's basically the same as if I'd kept the original F preset and just cranked my PD. 

So am I missing something? Why is everyone so excited by these new presets? The capability to get the same performance and visuals was already there using existing means...

"...Iiiiiiiiiii just wanna fly; put your arms around me baby, put your arms around me baby" - Sugar Ray

RTX 3090, Ryzen 7 5800X3D, MSI MPG B550 Gaming mobo, 64 GB DDR4 RAM, 970 EVO Plus NVMe M.2 SSD 2TB game drive, VKB STECS Standard throttle, Winwing Ursa Minor Fighter stick, Oculus Quest Pro via ersatz link cable, Standalone DCS.

VR only.

 

Posted
3 hours ago, FupDuck said:

I've tried preset J as well as K, and while the visuals are definitely much sharper, the loss in performance was too much for me to absorb. My flights over Syria and South Atlantic went from buttery smooth to a stutter fest. It's basically the same as if I'd kept the original F preset and just cranked my PD. 

So am I missing something? Why is everyone so excited by these new presets? The capability to get the same performance and visuals was already there using existing means...

Same here... better image, big hit in performance.

I'm on 4k resolution - rtx 3070ti

  • Thanks 1
Posted

they told this, that transformer loss 6 to 8% on performances... but you should be able to use the lower preset (i.e. balance vs quality) and got better image than previous quality settings, resulting in basically a slightly performance boost over the same image quality than before (and without ghosting).

 

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Posted
4 hours ago, chromium said:

they told this, that transformer loss 6 to 8% on performances... but you should be able to use the lower preset (i.e. balance vs quality) and got better image than previous quality settings, resulting in basically a slightly performance boost over the same image quality than before (and without ghosting).

 

Ok I guess I'll give that a try after cocktail hour. Thanks kind sir!

"...Iiiiiiiiiii just wanna fly; put your arms around me baby, put your arms around me baby" - Sugar Ray

RTX 3090, Ryzen 7 5800X3D, MSI MPG B550 Gaming mobo, 64 GB DDR4 RAM, 970 EVO Plus NVMe M.2 SSD 2TB game drive, VKB STECS Standard throttle, Winwing Ursa Minor Fighter stick, Oculus Quest Pro via ersatz link cable, Standalone DCS.

VR only.

 

Posted

3070 pleb here.  The combination of the two new presets and dlls with the optimised textures powershell script has been remarkable.  I've been able to crank my view distance out to the highest settings with water, cloud and shadow settings that I wouldn't even consider previously just using DLAA.  Unfortunately it breaks IC, so I've only been using it on my private server.

  • Like 1
Posted
1 hour ago, Biggus said:

3070 pleb here.  The combination of the two new presets and dlls with the optimised textures powershell script has been remarkable.  I've been able to crank my view distance out to the highest settings with water, cloud and shadow settings that I wouldn't even consider previously just using DLAA.  Unfortunately it breaks IC, so I've only been using it on my private server.

How does that script enhance performance? It looks like it just reduces file sizes...

"...Iiiiiiiiiii just wanna fly; put your arms around me baby, put your arms around me baby" - Sugar Ray

RTX 3090, Ryzen 7 5800X3D, MSI MPG B550 Gaming mobo, 64 GB DDR4 RAM, 970 EVO Plus NVMe M.2 SSD 2TB game drive, VKB STECS Standard throttle, Winwing Ursa Minor Fighter stick, Oculus Quest Pro via ersatz link cable, Standalone DCS.

VR only.

 

Posted (edited)
5 minutes ago, FupDuck said:

How does that script enhance performance? It looks like it just reduces file sizes...

Smaller files = less VRAM used = less paging to RAM when you get low on VRAM = less paging to disk when you get low on RAM. Basically you have more VRAM headroom to play with.

Edited by sleighzy
  • Like 1

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

Posted
8 hours ago, chromium said:

they told this, that transformer loss 6 to 8% on performances... but you should be able to use the lower preset (i.e. balance vs quality) and got better image than previous quality settings, resulting in basically a slightly performance boost over the same image quality than before (and without ghosting).

 

Well I tried this and it didn't come close to being the same. In order to get the same framerate as preset F, I had to turn the DLSS quality down to ultra performance, which looked like absolute ass. So as expected, you can't get something for nothing. The only way preset J/K is better is if you had enough overhead from the beginning to crank your PD anyways.

"...Iiiiiiiiiii just wanna fly; put your arms around me baby, put your arms around me baby" - Sugar Ray

RTX 3090, Ryzen 7 5800X3D, MSI MPG B550 Gaming mobo, 64 GB DDR4 RAM, 970 EVO Plus NVMe M.2 SSD 2TB game drive, VKB STECS Standard throttle, Winwing Ursa Minor Fighter stick, Oculus Quest Pro via ersatz link cable, Standalone DCS.

VR only.

 

Posted

Uhmmm that's quite interesting cause well, I literally have your same system (if not for the MB model). I use Quest 3, with PD 1.3, and I get a very stabl3 30 to 40 fps (40 is maxed out for me). But I stay almost always on medium settings with terrain set as low, distance high.

ChromiumDis.png

Author of DSMC, mod to enable scenario persistency and save updated miz file

Stable version & site: https://dsmcfordcs.wordpress.com/

Openbeta: https://github.com/Chromium18/DSMC

 

The thing is, helicopters are different from planes. An airplane by it's nature wants to fly, and if not interfered with too strongly by unusual events or by a deliberately incompetent pilot, it will fly. A helicopter does not want to fly. It is maintained in the air by a variety of forces in opposition to each other, and if there is any disturbance in this delicate balance the helicopter stops flying; immediately and disastrously.

Posted (edited)
41 minutes ago, chromium said:

Uhmmm that's quite interesting cause well, I literally have your same system (if not for the MB model). I use Quest 3, with PD 1.3, and I get a very stabl3 30 to 40 fps (40 is maxed out for me). But I stay almost always on medium settings with terrain set as low, distance high.

Ah, you're using ASW then. That explains it. With my settings, I get a solid 80 FPS - no ASW. Here are my settings if you want to give them a try on our almost identical systems. Maybe you can also get 80!

https://www.amazon.ca/photos/share/iWU0LDhJu4Tv3jK27Kkl6ijrDiUdNjSrskoPluI069Y

 

Edit: one thing not shown in those settings is the fact that I use OpenXR toolkit purely for the turbo mode. That is key. ☝️

 

Also, I decided to try preset F with an increased PD in game. As expected, increasing my PD from 1.0 to 1.2 on preset F had the same performance and visuals as preset J/K with PD 1.0.

Edited by FupDuck
  • Thanks 1

"...Iiiiiiiiiii just wanna fly; put your arms around me baby, put your arms around me baby" - Sugar Ray

RTX 3090, Ryzen 7 5800X3D, MSI MPG B550 Gaming mobo, 64 GB DDR4 RAM, 970 EVO Plus NVMe M.2 SSD 2TB game drive, VKB STECS Standard throttle, Winwing Ursa Minor Fighter stick, Oculus Quest Pro via ersatz link cable, Standalone DCS.

VR only.

 

Posted
1 hour ago, FupDuck said:

Edit: one thing not shown in those settings is the fact that I use OpenXR toolkit purely for the turbo mode. That is key. ☝️

Worth noting that OpenXR Toolkit is no longer maintained or supported. You get turbo mode through QVF if you're using that though.

[sIGPIC][/sIGPIC]

Soul's pit thread

Posted
10 hours ago, AhSoul said:

Worth noting that OpenXR Toolkit is no longer maintained or supported. You get turbo mode through QVF if you're using that though.

I know. I tried using QVFR for that exact reason, but I wasn't able to disable the actual quad views stuff. I have a 3090, so quad views didn't make the game smoother for me.

Although it's no longer supported, OpenXR toolkit still works for me, and works better than QVFR atm.

"...Iiiiiiiiiii just wanna fly; put your arms around me baby, put your arms around me baby" - Sugar Ray

RTX 3090, Ryzen 7 5800X3D, MSI MPG B550 Gaming mobo, 64 GB DDR4 RAM, 970 EVO Plus NVMe M.2 SSD 2TB game drive, VKB STECS Standard throttle, Winwing Ursa Minor Fighter stick, Oculus Quest Pro via ersatz link cable, Standalone DCS.

VR only.

 

Posted
11 hours ago, FupDuck said:

I know. I tried using QVFR for that exact reason, but I wasn't able to disable the actual quad views stuff. I have a 3090, so quad views didn't make the game smoother for me.

Although it's no longer supported, OpenXR toolkit still works for me, and works better than QVFR atm.

I'm surprised QVF doesn't help you?

[sIGPIC][/sIGPIC]

Soul's pit thread

Posted
1 minute ago, okurz said:

Can you clarify what QVF is?

Quad View Foveated

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

Posted

Hello,

is the step by step on the first post still valid as off today in order to have DLSS4 only for DCS?

Thanks

🖥️   9800X3D - 64Go 6000C30 - RTX 5090 - Samsung 980Pro 1To

🥽   Quest 3

🕹️   VKB Gladiator NXT - Winwing Orion2 - Winwing MFDs with screens - Winwing PTO 2 - Custom UFC

✈️   F/A-18C

Posted
2 minutes ago, Farside24 said:

Hello,

is the step by step on the first post still valid as off today in order to have DLSS4 only for DCS?

Thanks

If you are referring to putting the dxgi.dll and dlsstweaks ini files in the bin and bin-mt dirs and updating the preset in the ini files then the answer is Yes, this is still valid.

DLSS Swapper can be used to replace the nvngx_dlss.dll files to the latest version as an easy preference to manually copying those latest dll files in.

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

Posted (edited)
17 minutes ago, sleighzy said:

If you are referring to putting the dxgi.dll and dlsstweaks ini files in the bin and bin-mt dirs and updating the preset in the ini files then the answer is Yes, this is still valid.

DLSS Swapper can be used to replace the nvngx_dlss.dll files to the latest version as an easy preference to manually copying those latest dll files in.

Alright Thanks so if I understand correctly, if I only want DLSS 4 for DCS, I only need to :

- install DLSS Swapper

- Select the DCS folder so the ini and dll files gets there

- Install Nvidia Profile Inspector to select profile J (or K) and apply it

- Enable DLSS in-game (Quality profile)

- That's it, no need for additionnal such as DLSSTweaksConfig or Nvidia Global Profile

Right ?

 

Edited by Farside24

🖥️   9800X3D - 64Go 6000C30 - RTX 5090 - Samsung 980Pro 1To

🥽   Quest 3

🕹️   VKB Gladiator NXT - Winwing Orion2 - Winwing MFDs with screens - Winwing PTO 2 - Custom UFC

✈️   F/A-18C

  • Recently Browsing   0 members

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