DLSS "update"

[PLUTON]

I've been using DLSS 3.8.10.0 since the beginning but I never found a way to set it to E in VNPI
so there was no point in having DLSS 3.8.10

[zildac]

3 minutes ago, PLUTON said:

I've been using DLSS 3.8.10.0 since the beginning but I never found a way to set it to E in VNPI
so there was no point in having DLSS 3.8.10

Use DLSSTweaks and use the hook method for dxgi

[sleighzy]

2 minutes ago, PLUTON said:

I've been using DLSS 3.8.10.0 since the beginning but I never found a way to set it to E in VNPI
so there was no point in having DLSS 3.8.10

3.8.10 used E by default so didn’t need to update the preset, it just works.  With the DLSS 4 one you will. 

[warmachine79]

Ok, I did it; then I went into the Digital Combat Simulator Black Shark Profile and selected "Force Profile J" - do I need to copy the customnamesettingsfile anywhere? And in DCS, which DLSS level to I select or is that irrelevant since the NVInsp setting take precedence? Also, is there an Overview of the settings/parameters that apply to each Preset? 

 

Edit: I think it works but I hope this is not a placebo ;). Looks even sharper, 60 FPS on a Pimax Crystal Light with all eye candy on, 90hz upscale mode. Frametime is constantly 11 ms, and it does not seem to be CPU limited, the 4090 is sipping ~410 Watts. 

Edited January 24 by warmachine79

[zildac]

16 minutes ago, warmachine79 said:

Ok, I did it; then I went into the Digital Combat Simulator Black Shark Profile and selected "Force Profile J" - do I need to copy the customnamesettingsfile anywhere? And in DCS, which DLSS level to I select or is that irrelevant since the NVInsp setting take precedence? Also, is there an Overview of the settings/parameters that apply to each Preset? 

 

Edit: I think it works but I hope this is not a placebo ;). Looks even sharper, 60 FPS on a Pimax Crystal Light with all eye candy on, 90hz upscale mode. Frametime is constantly 11 ms, and it does not seem to be CPU limited, the 4090 is sipping ~410 Watts. 

You still need to select what "level" or DLSS you want to use in the DCS UI. With a 4090 and a Varjo Aero I only use DLAA, do you need DLSS with your setup? What does the DCS in game FPS counter say is "limiting" you.

[warmachine79]

6 minutes ago, zildac said:

You still need to select what "level" or DLSS you want to use in the DCS UI. With a 4090 and a Varjo Aero I only use DLAA, do you need DLSS with your setup? What does the DCS in game FPS counter say is "limiting" you.

So I use "Quality" in order for it to use Preset J? 

I cannot exactly see by the graph what is limiting me, the stat screen is somehow "cropped". 

[zildac]

6 minutes ago, warmachine79 said:

So I use "Quality" in order for it to use Preset J? 

I cannot exactly see by the graph what is limiting me, the stat screen is somehow "cropped". 

No, it will use preset J regardless the "levels" are particular variations to how it does its "stuff". Odd, re the FPS display usually just click the down arrow and it expands the graph and at the top of the graph it should tell you in coloured text what the limiting factor is.

Edited January 24 by zildac

[warmachine79]

It jumps between "Rendering Thread" and "Main Thread", but both CPU bound (7950X3D). 

[zildac]

It jumps between "Rendering Thread" and "Main Thread", but both CPU bound (7950X3D). 

OK, so DLSS probably not going to do much for you tbh. Can still use DLAA far better than MSAA especially in VR

[warmachine79]

1 hour ago, zildac said:

1 hour ago, warmachine79 said:

It jumps between "Rendering Thread" and "Main Thread", but both CPU bound (7950X3D). 

OK, so DLSS probably not going to do much for you tbh. Can still use DLAA far better than MSAA especially in VR

Now this is starting to confuse me. I started without VR in UHD (all cranked up) and now I am GPU bound. How can I be CPU bound in VR and GPU bound in UHD? I also checked whether the correct cores are parked (the X3D issue) which is the case. 

 

It also confuses me that you play with DLAA and Aero and I play with DLSS and PCL; if I play with DLAA, it becomes to slow, although PCL has a lower Res than Aero. 

nullSettings below. I also Pimax set to Central Priority Rendering Balanced and otherwise to its default resolutio. nullnull

Edited January 24 by warmachine79

[Bigity]

3 hours ago, zildac said:

Profile "J" is the new transformer preset. You need to force it via NVPI and you will also have to add it to the config XML file in order for it to be selectable in the GUI.

 

CustomSettingNames.xml - the highlighted line needs to be added and selected in the DCS profile in NVPI and it will NOT persist a driver update, so you'll need to reapply.

 

null

Can we set it with DLSSTweaks?

[zildac]

Just now, Bigity said:

Can we set it with DLSSTweaks?

I couldn't get it to work with DLSS tweaks only, by setting J in the .ini. I had to also set the NVPI preset too, then set the DLSSTweaks .ini preset to DEFAULT.

[zildac]

18 minutes ago, warmachine79 said:

Now this is starting to confuse me. I started without VR in UHD (all cranked up) and now I am GPU bound. How can I be CPU bound in VR and GPU bound in UHD? I also checked whether the correct cores are parked (the X3D issue) which is the case. 

 

It also confuses me that you play with DLAA and Aero and I play with DLSS and PCL; if I play with DLAA, it becomes to slow, although PCL has a lower Res than Aero. 

At a guess, in VR the CPU is worked harder, hence the CPU render thread message. In 2D I am GPU bound at 249FPS. It seems normal to me. As to why you are seeing worse performance in VR with DLAA when you are not GPU limited is a bit of a mystery. I am also using Varjo Quadviews Foveated in VR.

[LucShep]

For those accustomed with DLSS Tweaks (an old video tutorial here), you can keep using it for the new DLSS4 .DLL with transformer model (v310.1.0.0).
Just make sure to select force preset G.
This is because, somehow, forcing preset G will actually make it utilize the J preset (aka "transformer"), which does not appear in DLSS Tweaks for selection.

Have to say, with a few settings changed (see image below, I also attach my .INI here if you wish to try it), it seems this version of DLSS works great in Cyberpunk2077.
EDIT: actually, I'm noticing some shimmering in the foliage, whereas there is none with "preset C"  hmmmm...
(NOTE: haven't tested with DCS yet)
I'm very impressed. The image clarity is noticeably better, and inclusively in motion most of the smear is gone.
There's a tiny hit in performance, but then improvements are so good that it even allows decrease of one step to get back performance (from quality to balanced, etc).

Edited January 24 by LucShep

[jurinko]

New DLSS got rid of residual shimmering in F1 pit. Letters and gauges are much better visible. It is more taxing, but going back one step in PD fixed it. 

[zildac]

1 hour ago, LucShep said:

For those accustomed with DLSS Tweaks, you can keep using that for the new DLSS4 .DLL with transformer model (v310.1.0.0).
Just make sure to select force preset G.
This is because, somehow, forcing preset G will actually make it utilize the J preset (aka "transformer"), which does not appear in DLSS Tweaks for selection.

Have to say, with a few settings changed (see image below, I also attach my .INI here if you wish to try it), it seems DLSS is finally working great in Cyberpunk2077.
(NOTE: haven't tested with DCS yet)
I'm very impressed. The image clarity is noticeably better, and inclusively in motion most of the smear is gone.
There's a small hit in performance, but then the improvements mean you can actually decrease one step to get back the performance (f.ex, from quality to balanced, etc).

 

That's interesting, and negates the need to set the profile via NVPI if you’re already using DLSSTweaks...how did you find that?

[5ephir0th]

Those of you that had tried the new DLSSs are using the leaked driver from CUDA drivers (571.96)? It looks like with the new driver the lower performance is neglected, at least in other games.

Can try right now, my 4090 its at nVidia RMA due to a burned connector...

[LucShep]

25 minutes ago, zildac said:

That's interesting, and negates the need to set the profile via NVPI if you’re already using DLSSTweaks...how did you find that?

By trial and error, as the other method by NVInspector does not give me same results with DLAA forced onto DLSS profiles (can't live without it).  
I later found out it's transversal to other people in reddit and guru3d forums, who had already found same results (for example, see here) - it seems I'm not alone experimenting until stuff gets borked! LOL (in this case it didn't get borked )
 

20 minutes ago, 5ephir0th said:

Those of you that had tried the new DLSSs are using the leaked driver from CUDA drivers (571.96)? It looks like with the new driver the lower performance is neglected, at least in other games.

Can try right now, my 4090 its at nVidia RMA due to a burned connector...

Nope, still using good old 537.58 drivers here (in my experience the best drivers to this day for my RTX3090).
No issues whatsoever.

 

Edited January 24 by LucShep

[zildac]

20 minutes ago, LucShep said:

By trial and error, as the other method by NVInspector does not give me same results with DLAA forced onto DLSS profiles (can't live without it).  
I later found out it's transversal to other people in reddit and guru3d forums, who had already found same results (for example, see here) - it seems I'm not alone experimenting until stuff gets borked! LOL (in this case it didn't get borked )
 

Nope, still using good old 537.58 drivers here (in my experience the best drivers to this day for my RTX3090).
No issues whatsoever.

 

21 minutes ago, 5ephir0th said:

Those of you that had tried the new DLSSs are using the leaked driver from CUDA drivers (571.96)? It looks like with the new driver the lower performance is neglected, at least in other games.

Can try right now, my 4090 its at nVidia RMA due to a burned connector...

No, just using the latest DLSS dll that shipped with the CyberPunk patch.

[Qcumber]

2 hours ago, LucShep said:

I'm very impressed. The image clarity is noticeably better, and inclusively in motion most of the smear is gone

Yes. I am seeing that too.

[VietGirl]

Which DLL do we use there are 3 of them?

[sleighzy]

2 hours ago, VietGirl said:

Which DLL do we use there are 3 of them?

You want the nvngx_dlss.dll one. The others are for frame-generation etc. which is not supported by DCS.

[VietGirl]

Thanks for you help,will try it ,and let you know how it works. 

[diego999]

In my case with the J preset the cockpit is much crispier and sharper, with a slight increase in GPU frametimes. Distant objects are noticeable less blurry than before.

Ghosting, on the other hand, is horrible. Way worse than all other presets.

My GPU is an old 3060ti, so maybe this new preset is aimed at newer cards? I don't know.

[5ephir0th]

This is new DLSS 4 with actual drivers vs leaked ones from CUDA Toolkit

From:

Reddit post

Edited January 25 by 5ephir0th