Update the DLSS preset used by DCS to remove ghosting

[Greyman]

sorry if I've missed this above, but I'd heard, possibly a rumour, that with the release of DLSS 4 at the end of this month, the Nvidia app would at least make the DLSS Swapper app unnecessary and possibly DLSS tweaks as well.   

We've now not got too long to wait to see if that turns out to be accurate. 

[cercata]

This is the DLSS that comes with Cyberpunk 2077 today's update, they say it's version 4:

https://drive.google.com/file/d/17gZKi62fJGY5_3R-Nmc7_loAuMabTJky/view?usp=sharing

It works with DCS, but didn't play for a while, It's good but I can't tell if there are difference with previous versions.

[sleighzy]

3 hours ago, cercata said:

This is the DLSS that comes with Cyberpunk 2077 today's update, they say it's version 4:

https://drive.google.com/file/d/17gZKi62fJGY5_3R-Nmc7_loAuMabTJky/view?usp=sharing

It works with DCS, but didn't play for a while, It's good but I can't tell if there are difference with previous versions.

Unfortunately that appears to have reintroduced the older presets that were removed in 3.8.10. This means unless you’re overriding them then you’ll be back on the older C preset. I’m currently looking to use Nvidia Profile Inspector to test preset J to see how much better it looks. 

[PawlaczGMD]

3 hours ago, cercata said:

This is the DLSS that comes with Cyberpunk 2077 today's update, they say it's version 4:

https://drive.google.com/file/d/17gZKi62fJGY5_3R-Nmc7_loAuMabTJky/view?usp=sharing

It works with DCS, but didn't play for a while, It's good but I can't tell if there are difference with previous versions.

Are you saying DLSS 4 works with older GPU generations? That would be interesting.

[sleighzy]

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.

Edited January 31 by sleighzy
Easier tools now they have better support.

[zildac]

1 hour ago, 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 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.

Exactly the process I followed, thanks for summarising it well.

[PawlaczGMD]

FYI, I've found this chart of what new features are available on which gen.

[Grodin]

2 hours ago, 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 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.

 

While getting rid of the MFD ghosting is a huge deal, looking at the switch labels in your picture it still looks like the same blurry mess DLSS always was - can anyone confirm if the image quality in VR still takes a huge hit like it did with the previous versions? I just can't stand the blurry labels and MFDs in VR.

[Thundersmoke]

37 minutes ago, Grodin said:

 

While getting rid of the MFD ghosting is a huge deal, looking at the switch labels in your picture it still looks like the same blurry mess DLSS always was - can anyone confirm if the image quality in VR still takes a huge hit like it did with the previous versions? I just can't stand the blurry labels and MFDs in VR.

I'm on 4090, Quest 3, Virtual Desktop.  Previously, I was on "Godlike" VD and 1.2 pixel density and stable at 72FPS with good cockpit detail.  Now I'm getting the same detail, nice sharp cockpit labels and gauges, on "Ultra" in VD (a step down in res), at 80FPS at 1.0 pixel density in DCS.  I'd also dabbled with DLSS off and MSAA 2x, but hated the shimmer.

So far as I can tell, I'm getting much sharper DLSS performance which has allowed me to dial back resolution and increase framerate.  I spend most of my time in warbirds so I live and die by the engine gauges and like you, they gotta be sharp.  And since all combat is close-quarters dogfights, motion blurring and smearing is a no-go.

It's not perfect, but it seems a significant improvement.  I'm definitely parking my settings here for a while to further evaluate.  I think people are going to like Preset J.

[sleighzy]

1 hour ago, Grodin said:

looking at the switch labels in your picture it still looks like the same blurry mess DLSS always was

Screenshot for that one wasn't taken in game, was just to demonstrate the debug overlay and not the game's clarity (was screenshot from my laptop remoted into my PC at the time), so may have lost some clarity there. Not the same blurry DLSS mess it used to be.

I'm a VD user with res at Ultra, DCS PD is 1.0. I also use Quad Views as well with the focal multiplier set to 1.4. I'll do some further testing and reduce the quad views multiplier, but honestly I'm happy with everything so far.

[gonvise]

Is this latest version worth it if I only use DLAA?

[zildac]

7 minutes ago, gonvise said:

Is this latest version worth it if I only use DLAA?

For me (I am also DLAA only) there is less ghosting, I am using Preset J

[gonvise]

Is it necessary to put J preset in the base profile or can it be put only in the Digital Combat Simulator profile?

[Grodin]

4 hours ago, sleighzy said:

Screenshot for that one wasn't taken in game, was just to demonstrate the debug overlay and not the game's clarity (was screenshot from my laptop remoted into my PC at the time), so may have lost some clarity there. Not the same blurry DLSS mess it used to be.

I'm a VD user with res at Ultra, DCS PD is 1.0. I also use Quad Views as well with the focal multiplier set to 1.4. I'll do some further testing and reduce the quad views multiplier, but honestly I'm happy with everything so far.

Very happy to hear that, until now i've found DLSS to be unbearable but i'll give this a try!

[zildac]

1 hour ago, gonvise said:

Is it necessary to put J preset in the base profile or can it be put only in the Digital Combat Simulator profile?

I have applied it only to the DCS profile, I am also running DLSSTweaks and with the profile in DLSSTweaks set to default and Preset J set in the DCS NVPI profile the DLSSTweaks HUD confirms preset J is in use. I ONLY used DLSSTweaks previously to set profile F instead of the default E used by DCS and of course the HUD function.

[Selliese]

DLAA + Preset J have artefacts.

Спойлер

 

[zildac]

49 minutes ago, Selliese said:

DLAA + Preset J have artefacts.

  Hide contents

 

I haven't noticed any (exclusively in VR) and it's hard to make out in your pic as it's quite small.

[Selliese]

2 часа назад, zildac сказал:

I haven't noticed any (exclusively in VR) and it's hard to make out in your pic as it's quite small.

Full

Спойлер

 

Edited January 24 by Selliese

[cercata]

10 hours ago, sleighzy said:

The Preset J option is now available in the dropdown.

Where do you apply that preset, to the profile "Digital Combat Simulator: Black Shark" in the profile Inspector ?

[zildac]

Where do you apply that preset, to the profile "Digital Combat Simulator: Black Shark" in the profile Inspector ?

Yes, or globally if you prefer. I opted for the former.

[-Relax-]

Will there be a more easy way to get this work when the new nvidia drivers are released?
Without need install nividiaprofileinspector and dlss tweaks?

i heard you should be ablte to do it just via nvidia app!?

[sleighzy]

28 minutes ago, -Relax- said:

Will there be a more easy way to get this work when the new nvidia drivers are released?
Without need install nividiaprofileinspector and dlss tweaks?

i heard you should be ablte to do it just via nvidia app!?

No you’ll still need those steps to set the preset. DCS by default uses the C preset.

You don’t need DLSSTweaks for this one, it’s just helpful for the hud overlay for verifying you’ve made the correct change. 

Edited January 24 by sleighzy

[FrankT118]

Did everything as above, but how do you enable the debug overlay?

Edited January 24 by FrankT118

[-Relax-]

@sleighzy
so i have try follow the instructions now.

1st ut the DLL file in bin and bin mt (42mb file)
2nd installed inspector and edited the lne for J profile.
(i chooses DCS instead of global)

now i am stuck. how i use DLSSTweaks to confirm profil J is activ?
and in DCS graphic options i select DLSS and quaility?


EDIT
DLSS tweaks folder has his own nvngx.dll file (827kb)
do i need to switch this also with the dlss 4 file or something?

Edited January 24 by -Relax-

[LucShep]

12 minutes ago, -Relax- said:

@sleighzy
so i have try follow the instructions now.

1st ut the DLL file in bin and bin mt (42mb file)
2nd installed inspector and edited the lne for J profile.
(i chooses DCS instead of global)

now i am stuck. how i use DLSSTweaks to confirm profil J is activ?
and in DCS graphic options i select DLSS and quaility?

If you clicked "Apply Changes" in the NVInspector app, then... it's done!  

DLLSTweaks is just an alternative (i.e, not required over what you already done), in case you wish to mess around and tweak stuff (I prefer it myself, see here).
 

Edited January 24 by LucShep