DLSS "update"

[sleighzy]

20 hours ago, VietGirl said:

Hi anyone know how to set DlssTweaks in OVGME, So I dont have to keep replacing the dll everytime their is a new update to DCS , thanks in advance .

You can use Nvidia Profile Inspector (the Orbmu2k one) and then in the Other section set Enable DLSS-SR Override to 1 and Override DLSS-SR presets to 0x000000A for J or 0xFFFFFFF for latest (preset K). This means you don't need to swap dlls as it will use the one from the driver.

If you want to use OVGMe then in the folder you currently keep your mods for this create a DLSSTweaks folder, and then a bin and bin-mt folder under that. Put the dlls in that folder. When you enable the mod it'll put them in the right folder, basically it overwrites stuff based on the same folder structure as the core games folders.

DLSS Swapper is also really easy for this and you can download and switch dlss versions without manually copying stuff.

10 hours ago, Arcc said:

Hi

Sorry, i use an online translator...

I followed the tutorial   https://www.youtube.com/watch?v=ZKCMmAip_ZM&t=58s   to install DLSS .4

I have less flickering with the DLSS than without

Oh oh just to try... my DCS works well in DLAA

It is possible to delete the text at the bottom.

Best regards

Christian

 

 

If you followed that video you would have created a new registry key that turned that text (the hud overlay) on. Just remove the registry key again.

[VietGirl]

Thanks for the help .

[Mustang]

6 hours ago, sleighzy said:

You can use Nvidia Profile Inspector (the Orbmu2k one) and then in the Other section set Enable DLSS-SR Override to 1 and Override DLSS-SR presets to 0x000000A for J or 0xFFFFFFF for latest (preset K). This means you don't need to swap dlls as it will use the one from the driver.

If you want to use OVGMe then in the folder you currently keep your mods for this create a DLSSTweaks folder, and then a bin and bin-mt folder under that. Put the dlls in that folder. When you enable the mod it'll put them in the right folder, basically it overwrites stuff based on the same folder structure as the core games folders.

DLSS Swapper is also really easy for this and you can download and switch dlss versions without manually copying stuff.

If you followed that video you would have created a new registry key that turned that text (the hud overlay) on. Just remove the registry key again.

I gotta say you defo know your stuff, well impressed thanks for all this info 

[Arcc]

Quote

If you followed that video you would have created a new registry key that turned that text (the hud overlay) on. Just remove the registry key again.

Si vous avez suivi cette vidéo, vous auriez créé une nouvelle clé de registre qui a activé ce texte (la superposition du HUD). Supprimez simplement à nouveau la clé de registre.

Of course..... ShowDlssIndicator  means see. 

Thanks

[mmike87]

On 1/30/2025 at 2:58 PM, diamond26 said:

I don't know what happened but after installing the latest Nvidia drivers 572.16, I lost eye tracking and I don't see the option for it in DCS VR Settings!!! Also DCS crashes if I use new dll and new drivers

I had a similar experience. I rolled back to the Cuda SDK development drivers that also fully support DLSS 4. I've had zero issues with those drivers, despite being non-release drivers. 

[DCoffey]

3 hours ago, mmike87 said:

I had a similar experience. I rolled back to the Cuda SDK development drivers that also fully support DLSS 4. I've had zero issues with those drivers, despite being non-release drivers. 

And I was accused of driver roulette…

Edited February 10 by DCoffey

[BlackReef]

Both J and K have ghosting for me

[Camelot101]

On 3/12/2025 at 10:35 PM, BlackReef said:

Both J and K have ghosting for me

Same here

[Mausar]

I'll stick with E preset for now. It's little more blurry than J and K and I have stable frame rate in VR.

[Bigity]

All

 

You may have noticed by now the entry in the latest patch about updating the DLSS version that DCS uses.

• Render system. DLSS updated to version 310.2.1.0.

In addition to DCS using the latest dll file (for now at least!) we can control our preset with a line in the autoexec.cfg file.  The file is here and can be created as a text file (note the .cfg extension) if it does not exist:  Saved Games\DCS\Config\autoexec.cfg

 

Add the following line:

DLSS_Preset = 'K' -- or whichever preset you prefer

 

The following line will draw your HUD and MFDs after applying DLSS meaning they will not have DLSS applied to them and will have no ghosting from DLSS

HUD_MFD_after_DLSS = true

 

 

 

Big thanks to the devs, this is a nice QoL addition.

 

 

EDIT: I confirmed this works - just add the line as is to the file in question, or make a blank text file with the correct name and paste it in and save it.

Edited May 22 by Bigity

[scommander2]

4 minutes ago, Bigity said:

DLSS_Preset = 'K'

About the full syntax of autoexec.cfg likes below?

dx11backend =
{
    DLSS_Preset = 'K',
}

Thanks.

[Bigity]

1 minute ago, scommander2 said:

About the full syntax of autoexec.cfg likes below?

dx11backend =
{
    DLSS_Preset = 'K',
}

Thanks.

Not sure, the above is what I got from Special K on the ED discord.

I didn't have the file so I just created it and added the 'DLSS_Preset = 'K'' and saved it.   I haven't tried it yet though, just finished the update.

[scommander2]

12 minutes ago, Bigity said:

Not sure, the above is what I got from Special K on the ED discord.

No problem, thanks!

 

[Bigity]

All - I've just found this posted by ralfidude

 

Adding 'HUD_MFD_after_DLSS = true' to the same file draws your HUD and MFD screens without applying DLSS to them - meaning you can run DLSS and have no ghosting on your HUD or MFDs.

[Precog]

SO like this??

dx11backend =
{
    DLSS_Preset = 'K',
    HUD_MFD_after_DLSS = true
}

[sleighzy]

12 minutes ago, Precog said:

SO like this??

dx11backend =
{
    DLSS_Preset = 'K',
    HUD_MFD_after_DLSS = true
}

The autoexec.cfg file is just flat lines, v.s. a lua like syntax, so just the below:

DLSS_Preset = 'K'
HUD_MFD_after_DLSS = true

 

[Dondy]

I got the hint that the newest DLSS 4 is now also available in the NV App when using the option "latest" under the DLSS graphics option "DLSS override - Model presets" for DCS World.

null

[Ratfink]

18 hours ago, sleighzy said:

The autoexec.cfg file is just flat lines, v.s. a lua like syntax, so just the below:

DLSS_Preset = 'K'
HUD_MFD_after_DLSS = true

 

This works for me - B scope in F-18C looks sharp while still able to apply K

[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

[scommander2]

A quick question:

The recent release has shipped the latest DLSS, why the "DLSS_Preset" option is required in autoexec.cfg?

Thanks.

[rob10]

23 minutes ago, scommander2 said:

A quick question:

The recent release has shipped the latest DLSS, why the "DLSS_Preset" option is required in autoexec.cfg?

Thanks.

Because there are a number of presets (think versions) of DLSS that the DLSS version now included can use.  I'm not fully up to speed, but I think it defaults to something like preset "C" but the general consensus seems to be that preset "K" provides better results.  But some prefer preset "J". And likely some prefer "C".  So ED has to choose one to include by default and I guess they decided to go with an older one (for whatever their reasons are, maybe good, maybe inertia to leave it the same), so recommendation is to add that in the autoexec to get the one the "crowd" thinks is the better one.

[scommander2]

6 minutes ago, rob10 said:

Because there are a number of presets (think versions) of DLSS that the DLSS version now included can use.  I'm not fully up to speed, but I think it defaults to something like preset "C" but the general consensus seems to be that preset "K" provides better results.  But some prefer preset "J". And likely some prefer "C".  So ED has to choose one to include by default and I guess they decided to go with an older one (for whatever their reasons are, maybe good, maybe inertia to leave it the same), so recommendation is to add that in the autoexec to get the one the "crowd" thinks is the better one.

@rob10, thanks for the comment.  So, it is more for the backward support... 

[Ramsay]

52 minutes ago, scommander2 said:

The recent release has shipped the latest DLSS, why the "DLSS_Preset" option is required in autoexec.cfg?

Because by default DCS will use "Preset C" i.e. the older, more performant CNN (Convolutional Neural Network) mode.

Detail

DLSS 4 has advantages and disadvantages. It is not a "no cost" upgrade for all graphics/stuations (yet?) i.e. temporal artifacts/ghosting. Choosing the "best model" is often a matter of personal opinion.

DLSS 4 looks better in certain circumstances but has a negative impact on fps - this can be offset by choosing a lower quality upscale i.e. DLSS 4 Balanced -> DLSS 3 Quality, however this can have negative effect on MFD text, etc. in DCS and require tweaking using "sharpening" or similar effects. 

17 minutes ago, scommander2 said:

So, it is more for the backward support... 

IMHO rather for user preference, improvements to temporal artificing in DCS with DLSS 4 - often seem to be a placebo effect, rather than "real".

Nvidia continue to improve DLSS Super Resolution, so the "preset" default may change once ED feel DLSS 4 has "matured".

Edited May 23 by Ramsay

[rob10]

6 minutes ago, Ramsay said:

Because by default DCS will use "Preset C" i.e. the older, more performant CNN (Convolutional Neural Network) mode.

Thanks for the better and more detailed response!

[scommander2]

7 minutes ago, Ramsay said:

Nvidia continue to improve DLSS Super Resolution, so the "preset" default may change once ED feel DLSS 4.0 has "matured".

Thanks, @Ramsay, Indeed...