DLSS 4

[widen76]

2 minutes ago, 71st_Mastiff said:

apparently not working for the cards they stated.

because it tells me MSI RTX 4080 Super not supported.

Maybe it's only working for "supported" titles? If you select the Star Wars Squadrons game, does it still say not supported?

 

[VR Flight Guy in PJ Pants]

On the profiles, the J one is not look very good, but K, it is very clean and I need to check the performance difference.

[mmike87]

I was running DLSS 4 on "quality" and pre-set "J" via profile inspector on my 4090 / Aero ...  With the CUDA SDK dev drivers. 

HANDS DOWN... Best DCS experience in VR I've ever had.

Today I installed the official driver update and the new NVIDIA app.

My settings were blown away and I had to re-enable the resizable bar and preset J. The NVIDIA app will not let you do it for DCS because it says it's not supported.

Start the game and my frame rate was literally cut in half. I don't know if it's the drivers or if the new version of the NVIDIA app is setting something to a non-optimal setting behind the scenes.

I re-ran the CUDA SDK install and it wouldn't override the new drivers. So I had to completely manually uninstall them and roll everything back to the CUDA SDK version.I

Presto! Nice and smooth, very little ghosting, And I'm running pretty high settings.

Has anyone else noticed the difference in performance with the new drivers versus the development drivers? Or it may be the NVIDIA app? 

Edited January 31 by mmike87

[VR Flight Guy in PJ Pants]

Silly question, as profile K is so “clean”, how could I know DLSS is actually at work or not?

[mmike87]

53 minutes ago, VR Flight Guy in PJ Pants said:

Silly question, as profile K is so “clean”, how could I know DLSS is actually at work or not?

If DLSS Tweak still works, you can force an on-screen indicator of sorts. I think there is a registry key that can be set, too. However, in my VR it's tiny and illegible. 

 

[71st_Mastiff]

7 hours ago, widen76 said:

Maybe it's only working for "supported" titles? If you select the Star Wars Squadrons game, does it still say not supported?

 

[Ready]

9 hours ago, mmike87 said:

I was running DLSS 4 on "quality" and pre-set "J" via profile inspector on my 4090 / Aero ...  With the CUDA SDK dev drivers. 

HANDS DOWN... Best DCS experience in VR I've ever had.

Today I installed the official driver update and the new NVIDIA app.

My settings were blown away and I had to re-enable the resizable bar and preset J. The NVIDIA app will not let you do it for DCS because it says it's not supported.

Start the game and my frame rate was literally cut in half. I don't know if it's the drivers or if the new version of the NVIDIA app is setting something to a non-optimal setting behind the scenes.

I re-ran the CUDA SDK install and it wouldn't override the new drivers. So I had to completely manually uninstall them and roll everything back to the CUDA SDK version.I

Presto! Nice and smooth, very little ghosting, And I'm running pretty high settings.

Has anyone else noticed the difference in performance with the new drivers versus the development drivers? Or it may be the NVIDIA app? 

Yes same here. I installed the new Nvidia driver (572.16) and Nvidia App after first having used the CUDA released driver (571.96). I checked Nvidia app but quickly uninstalled it. I got the feeling it will mess up my settings and is bloat and complications I don't need. There is also a question in the Nvidia app installer that asks 'do you want this app to optimize your stuff' or something like that. Do not do that, I read it can really mess up your settings.

I also could not roll back to 571.96 so I tried rolling back to my previous best driver(566.14) and from there I installed 571.96. Performance-wise I did not notice much difference between 571.96 and 572.16. I will install the latest version again, but without the Nvidia app. With every driver I always go through the NVCP settings and the DLSSTweaks to make sure the settings I want are reconfigured.

8 hours ago, mmike87 said:

If DLSS Tweak still works, you can force an on-screen indicator of sorts. I think there is a registry key that can be set, too. However, in my VR it's tiny and illegible. 

 

I also can not see the overlay inside the headset. It is perfectly readable on my Desktop mirror though.

9 hours ago, VR Flight Guy in PJ Pants said:

Silly question, as profile K is so “clean”, how could I know DLSS is actually at work or not?

For me the easiest is using DLSSTweak to set 'HudOverlay'or something like that. 

4 hours ago, 71st_Mastiff said:

I would Ditch the Nvidia app. 

[Nate--IRL--]

Tried preset K this morning and am very happy with the Improvement in clarity in Balanced mode. It has it's own particular artifacts that I can overlook, overall it's positive for me.

Nate

[Qcumber]

I am still getting crashes and headset freezes using DLSS 4. Both with VD and meta link. Everything is fine with no AA or MSAA. I tried removing DLSSTweaks and set the global preset (K or J) with NVPI. I have cleared out the shader folders. I still get random crashes.

Edit: not sure what I did but it's now working with the latest DLSS release (310.2) and preset K. 

Edited February 2 by Qcumber

[Fiztex]

28 минут назад, Qcumber сказал:

I am still getting crashes and headset freezes using DLSS 4. Both with VD and meta link. Everything is fine with no AA or MSAA. I tried removing DLSSTweaks and set the global preset (K or J) with NVPI. I have cleared out the shader folders. I still get random crashes.

 

Are you flying with ASW/SSW? I had issues with DLSS 4 and VDXR SSW.

[Qcumber]

30 minutes ago, Fiztex said:

Are you flying with ASW/SSW? I had issues with DLSS 4 and VDXR SSW.

No. Reprojection is off. I think it is related to preset J and K.

[VR Flight Guy in PJ Pants]

This make DLSS worthwhile again. Before that I was fighting comets with unreadable MFDs. I use VD, and I am sure I have not turned on ASW as such.

Edited February 1 by VR Flight Guy in PJ Pants

[Flyingfish]

1 hour ago, Qcumber said:

I am still getting crashes and headset freezes using DLSS 4. Both with VD and meta link. Everything is fine with no AA or MSAA. I tried removing DLSSTweaks and set the global preset (K or J) with NVPI. I have cleared out the shader folders. I still get random crashes.

 

I've had problems with preset k but I managed to get J working by swapping the DLSS file to the previous version (the one with preset J but not K) then selecting preset J

[Qcumber]

6 minutes ago, Flyingfish said:

I've had problems with preset k but I managed to get J working by swapping the DLSS file to the previous version (the one with preset J but not K) then selecting preset J

Thanks. I'll give that a go. 

[Roosterfeet]

I noticed a substantial performance hit using both preset J and K but I also noticed something else which is subjective and I wonder if other people will have the same experience. Prior to DLSS 4, I have been using pixel density to 1.3 to achieve the image clarity I want, but when I rolled the pixel density back to 1.0 with preset K enabled using DLSS 4, I had comparable image clarity and performance to DLSS 3 at 1.3 pixel density. I was using the Quality setting in both scenarios.

[EricToGo]

I worked my way through to preset K with the Nvidia Profile Inspector and forced the HUD via DLSS Tweaks. In the overlay it shows Render Preset K now (or whatever I pick in the inspector), but I was wondering if it showing "DLSSv3 v310.2.1" in the following line is correct or if it should say "DLSSv4 ..." there? I downloaded the new DLLs and put them into DCS as well. I think it looks better in game, but it might as well be placebo and me wanting it to look better.

[Fiztex]

27 минут назад, EricToGo сказал:

I worked my way through to preset K with the Nvidia Profile Inspector and forced the HUD via DLSS Tweaks. In the overlay it shows Render Preset K now (or whatever I pick in the inspector), but I was wondering if it showing "DLSSv3 v310.2.1" in the following line is correct or if it should say "DLSSv4 ..." there? I downloaded the new DLLs and put them into DCS as well. I think it looks better in game, but it might as well be placebo and me wanting it to look better.

All is correct, this is the latest dll.

Edited February 1 by Fiztex

[johnbowzer]

I decided to give this a go, and found something I did not expect after reading through these threads and others in the forum on DLSS4 and how to implement and use/activate it.

I first went online to get nvidia profile inspector and came across this page as well. It suggested that the other tools maybe were not needed. So no nvidia app, no dll replacement, and I assumed no DLSSSwapper either. My DCS is a clean install, original dlss dlls. I already had nvidia 572.16 installed clean, after DDU removal. I do not have nvidia app, dlssTweaks or dlssSwapper installed.

So per that reddit page, I installed profile inspector, set the global overrides per this page, used the registry edit to see the DLSS info on screen, and launched DCS on the monitor. With settings using DLSS - Quality it shows it is using the latest dlss4 with preset K. I ran MSFS 2020 with DLSS set, same.

This suggest that just the new nvidia driver is required, with the overrides needed via NPI, but that is it.

 

[EightyDuce]

Had a couple days to play around with J and now with K. While clarity and shimmer are improved significantly, I still have some pretty egregious ghosting. Almost looks like aircraft is training smoke when looking at other aircraft against ground terrain. Didn't notice it initially as against the sky it doesn't seem to happen or isn't nearly as noticeable.

This is on Q3 with VD using AV1+Godlike preset. DCS settings DLSS Quality.

Edited February 1 by EightyDuce

[Blackhawk163]

Anyone change their quality preset render multiplier in dlss tweaks? I have. I think quality is defaulted to .65, I’ve changed it to .75 runs smooth on my rig and everything looks sharp with ever the slightest softening in objects like aircraft in the distance. Sometimes aircraft will comet tail when the ground is in their direct background. 

[Guldendrak]

Hi, anyone noticed a loss of FPS with the 310.2.1.0 version of dlss ? I tried first the new dlss 4 with the 310.1.0.0 and preset J and now the 310.2.1.0 with preset J and preset K and I had really better performances with the 310.1.0.0.

I have better clarity in MFD with the new version but the loss of fps is big.

[Qcumber]

1 hour ago, EightyDuce said:

Had a couple days to play around with J and now with K. While clarity and shimmer are improved significantly, I still have some pretty egregious ghosting. Almost looks like aircraft is training smoke when looking at other aircraft against ground terrain. Didn't notice it initially as against the sky it doesn't seem to happen or isn't nearly as noticeable.

This is on Q3 with VD using AV1+Godlike preset. DCS settings DLSS Quality.

I've seen this too. Ghosting in the sky is virtually gone but there is terrible ghosting against the ground. Particularly trees. 

3 minutes ago, Guldendrak said:

Hi, anyone noticed a loss of FPS with the 310.2.1.0 version of dlss ? I tried first the new dlss 4 with the 310.1.0.0 and preset J and now the 310.2.1.0 with preset J and preset K and I had really better performances with the 310.1.0.0.

I have better clarity in MFD with the new version but the loss of fps is big.

Yes. With QVFR I get the same FPS with DLSS4 Quality as MSAAx2. 

[sleighzy]

1 hour ago, johnbowzer said:

I decided to give this a go, and found something I did not expect after reading through these threads and others in the forum on DLSS4 and how to implement and use/activate it.

I first went online to get nvidia profile inspector and came across this page as well. It suggested that the other tools maybe were not needed. So no nvidia app, no dll replacement, and I assumed no DLSSSwapper either. My DCS is a clean install, original dlss dlls. I already had nvidia 572.16 installed clean, after DDU removal. I do not have nvidia app, dlssTweaks or dlssSwapper installed.

So per that reddit page, I installed profile inspector, set the global overrides per this page, used the registry edit to see the DLSS info on screen, and launched DCS on the monitor. With settings using DLSS - Quality it shows it is using the latest dlss4 with preset K. I ran MSFS 2020 with DLSS set, same.

This suggest that just the new nvidia driver is required, with the overrides needed via NPI, but that is it.

 

Correct, that is all that is needed. Don’t think some of that was known at the time…and also wouldn’t have been possible when people were testing this prior to the official driver release.

[Qcumber]

OK. My thoughts after using DLSS4 for a few days:

Pros:

• Clarity (cockpit and distance) is very good even with "performance" setting. Near perfect.
• Anti-aliasing is excellent. Overall a very smooth experience. Much better than MSAA. 
• Minimal ghosting of planes against the sky (some "tadpoling" at distance but not too bad).

Cons:

• Ghosting against the ground is very bad. Horrendous blurring. Once you see it for the first time you keep looking for it!
• Objects can become very difficult to see against clouds or contrasty backgrounds. 
• Spotting dots are terrible. You just can't see them at all. The only solution is setting dots to 2 pixels. Then they look like big blobs. 
• There is a significant performance hit compared to preset E or F. If you use QVFR there is no benefit versus MSAA x2. 
• DCS keeps crashing after 1-5 minutes [This last one might just be my issue but I can't solve it and I can't be bothered spending any more time on it. I am very vexed]. 

Overall this is much better than anything before but is still not there yet. I am going to stick with no AA or MSAA for now. 

[Roosterfeet]

The ghosting on other aircraft is a deal breaker for me too. I went back to the stock DLSS 3.7 dll and it's certainly not as crisp without increasing the PD but the ghosting is much less noticeable.