DLSS "update"

[ThorBrasil]

3 hours ago, mazex said:

Thanks for the advice here!

So, after creating the "autoexec.cfg" file in C:\Users\<username>\Saved Games\DCS\Config (did not exist before) with this content:

DLSS_Preset = 'K'
HUD_MFD_after_DLSS = true

It just works without having to mess with nvidiaProfileInspector etc. And it sure looks great! Loose 10 fps vs the default settings, but looks amazingly good. Really don't need more

It was perfect! Thank you!

[mazex]

 Thanks for the advice here!

So, after creating the "autoexec.cfg" file in C:\Users\<username>\Saved Games\DCS\Config (did not exist before) with this content:

DLSS_Preset = 'K'
HUD_MFD_after_DLSS = true

It just works without having to mess with nvidiaProfileInspector etc. And it sure looks great! Loose 10 fps vs the default settings, but looks amazingly good. Really don't need more

Note: I am running Nvidia 576.52 (on an RTX 5080) and DCS 2.9.16.10523. Additional info for VR users: I am using Pimax Play 1.39.4 and the 1.0.16 firmware for my Pimax Crystal Light it that matters. I have the Pimax render quality under the "games" section set to high that does a big difference in clarity (but takes quite som FPS). Worth it for me.

I am replying to my own post adding this good description stolen from Reddit where someone does a good job of explaining the different presets with letter codes. What I understand is that the latest version of DCS updates the DLSS dll to 310.2.1.0 It does however use preset C as the default setting (that we can override with the autoexec.cfg that is very nice of the devs). So only J and K use the new transformer model (AKA DLSS 4). The default C is the old CNN preset. I can see a very noticable difference in my Pimax Crystal Light using K instead of the default C preset. The displays and the landscape is MUCH sharper. But I loose around 10 fps. It is worth it for me...

Edited May 23 by mazex

[scommander2]

Thanks @mazex for the post, I do experience the flickering issue with the preset K.

[ThorBrasil]

16 minutes ago, mazex said:

 Thanks for the advice here!

So, after creating the "autoexec.cfg" file in C:\Users\<username>\Saved Games\DCS\Config (did not exist before) with this content:

DLSS_Preset = 'K'
HUD_MFD_after_DLSS = true

It just works without having to mess with nvidiaProfileInspector etc. And it sure looks great! Loose 10 fps vs the default settings, but looks amazingly good. Really don't need more

Note: I am running Nvidia 576.52 (on an RTX 5080) and DCS 2.9.16.10523

I am replying to my own post adding this good description stolen from Reddit where someone does a good job of explaining the different presets with letter codes. What I understand is that the latest version of DCS updates the DLSS dll to 310.2.1.0 It does however use preset C as the default setting (that we can override with the autoexec.cfg that is very nice of the devs). So only J and K use the new transformer model. The default C is the old CNN preset. I can see a very noticable difference in my Pimax Crystal Light using K instead of the default C preset. The displays and the landscape is MUCH sharper. But I loose around 10 fps. It is worth it for me...

@NineLine Could you ask the developers to put in the graphics options so you can choose the K preset and remove DLSS on MFDs and HUDs? It would be very welcome. This option would appear when you choose the DLSS option. Thanks!

[jnr4817]

I’d be interested in what other commands exist that could be helpful for us via the autoexec file. I’m sure there some that exist for the developers only, but surely there is a list that we could pull from and use at our own risk. 

[Qcumber]

7 hours ago, mazex said:

It just works without having to mess with nvidiaProfileInspector etc. And it sure looks great! Loose 10 fps vs the default settings, but looks amazingly good. Really don't need more

I have always found NVPI easy to use. Is there any specific advantage using the autoexec config file other than the MFD option? I presume it will need reinstalling after each DCS update. 

[mazex]

1 hour ago, Qcumber said:

I have always found NVPI easy to use. Is there any specific advantage using the autoexec config file other than the MFD option? I presume it will need reinstalling after each DCS update. 

Well, it seems like a dev override that is not included in the fingerprinted files it will overwite if changed. As it does not exist in the default install set it should be left alone. Not like us beeing forced down into a Soviet bunker with a cold war Su-27 as menu background every time a new update is released With NVPI we have to change 6 attributes every time a new Nvidia driver is released to get back to preset K. I hope this one will stay as it does not exist in the monitored files, and thus stick ...

[Draken35]

These options are new but autoexec.cfg is not... It will stay in place until you modify or delete it.

[Qcumber]

8 hours ago, mazex said:

Well, it seems like a dev override that is not included in the fingerprinted files it will overwite if changed. As it does not exist in the default install set it should be left alone. Not like us beeing forced down into a Soviet bunker with a cold war Su-27 as menu background every time a new update is released With NVPI we have to change 6 attributes every time a new Nvidia driver is released to get back to preset K. I hope this one will stay as it does not exist in the monitored files, and thus stick ...

NVPI has retained the DLSS settings for me the last 2 driver updates. 

[zildac]

Well, it seems like a dev override that is not included in the fingerprinted files it will overwite if changed. As it does not exist in the default install set it should be left alone. Not like us beeing forced down into a Soviet bunker with a cold war Su-27 as menu background every time a new update is released With NVPI we have to change 6 attributes every time a new Nvidia driver is released to get back to preset K. I hope this one will stay as it does not exist in the monitored files, and thus stick ...

Or you export the config and reapply it after the update.

[sleighzy]

8 hours ago, mazex said:

Well, it seems like a dev override that is not included in the fingerprinted files it will overwite if changed. As it does not exist in the default install set it should be left alone. Not like us beeing forced down into a Soviet bunker with a cold war Su-27 as menu background every time a new update is released With NVPI we have to change 6 attributes every time a new Nvidia driver is released to get back to preset K. I hope this one will stay as it does not exist in the monitored files, and thus stick ...

Not sure what 6 attributes you mean, is only 2.

The config file is in Saved Games so won’t be overridden. Those config changes were also made public on some channels by ED themselves so should be safe. 

[Qcumber]

I asked above but I did not get a reply but I'd there any specific advantage using the autoexec config (DLSS_Preset = 'K') versus using NVPI. 

[Tshark]

Quick question.  What Nvidia driver is needed to take advantage of preset "K"?  I am currently running a 4090 on driver 566.36.

[Rufuz64]

26 minutes ago, Qcumber said:

I asked above but I did not get a reply but I'd there any specific advantage using the autoexec config (DLSS_Preset = 'K') versus using NVPI. 

You don't have to use third-party software.

[sleighzy]

8 hours ago, Tshark said:

Quick question.  What Nvidia driver is needed to take advantage of preset "K"?  I am currently running a 4090 on driver 566.36.

The driver won't matter. 566.36 did not contain the DLSS4 K preset, but the latest DCS ships with the DLSS4 dll so will have that preset.

Note, if you've changed NVPI setting to override the dll used then it won't apply for 566.36

Edited May 24 by sleighzy

[Morphine]

Can we also exempt the HMD from DLSS? Having the HUD fixed really shows the fuzziness of the HMD.