DLSS 4

[widen76]

@Phantom711 Try installing by right-clicking and selecting "Run as administrator"

[Phantom711]

@widen76

Thanks for your suggestion, already tried that though. 
I will try DDU tomorrow. I hope I won‘t get stuck without being able to install any driver.

Edited February 3 by Phantom711

[david_joe]

Question: DCS default dlss version?

thanks

[sleighzy]

1 hour ago, david_joe said:

Question: DCS default dlss version?

thanks

DLSS 3.7.0.0

[MAXsenna]

13 hours ago, Phantom711 said:

Any ideas anybody?

Well, the message clearly says your GPU is too old and not compatible. Which makes me worried. Which GPU do you have? 

[Farside24]

Hello,

This DLSS4 is awesome.

It leads to improved graphics I would say versus native res.

With my RIG : 5700X3D / RTX3080 / 64Go / Quest 3 (with fixed foveated optimisation)

The settings bellow leads to 70FPS (locked) on custom mission single player Caucasus and Marianas maps.

Could you recommend any quickwin on graphics/performances/latency?

 

Edited February 4 by Farside24

[Phantom711]

vor 8 Stunden schrieb MAXsenna:

Well, the message clearly says your GPU is too old and not compatible. Which makes me worried. Which GPU do you have? 

4090 

...and yes, I´m serious.

I installed a riser cable recently in order to have the card vertically mounted. Mainly due to space in the case rather than optics or anything...could this be a problem? The card works flawlessly otherwise.

[sleighzy]

52 minutes ago, Farside24 said:

Hello,

This DLSS4 is awesome.

It leads to improved graphics I would say versus native res.

With my RIG : 5700X3D / RTX3080 / 64Go / Quest 3 (with fixed foveated optimisation)

The settings bellow leads to 70FPS (locked) on custom mission single player Caucasus and Marianas maps.

Could you recommend any quickwin on graphics/performances/latency?

 

Reduce the Preload Radius to 60000 as you are currently loading lots of stuff into memory which is potentially redundant.  What is the refresh rate of your headset set to? Make sure the max fps matches at least that.

Note, this is now going off topic so let’s not get distracted from the topic of this thread. Go to the VR4DCS Discord server for more feedback. 

Edited February 4 by sleighzy

[mmike87]

I think i figured out my issues ... the drivers, DLSS, etc. were all red herrings ... I finally opened up MSI Afterburner that I use to apply a small core OC and the typical, 1000+ 4090 memory clock and I noticed my power limit was set at like 35%!!!!!!!!!!!!!

Not sure how this happened ... I have not even opened Afterburner in months. I think that all the nVidia App's "optimization" crap did something since it seemed to default to "on". I removed the nVidia App and will just use the profile inspector and the trusty nVidia Control Panel for as long as I can.

After restoring my power limit to 105%, I am smooth as silk again in Profile K.

Someone asked me for my settings - I will play a bit and make sure it's all kosher and then post what I use.

Edited February 4 by mmike87

[Fiztex]

4 минуты назад, mmike87 сказал:

I think i figured out my issues ... the drivers, DLSS, etc. were all red herrings ... I finally opened up MSI Afterburner that I use to apply a small core OC and the typical, 1000+ 4090 memory clock and I noticed my power limit was set at like 35%!!!!!!!!!!!!!

You probably had the most Eco 4090 there is  I think you had a 3070 experience with a limit like that.

Edited February 4 by Fiztex

[mmike87]

So far, so good. Here are my specs and settings FWIW:

• 13900K, HT off, 5.6GHz all P-cores, .090mv undervolt
• 64GB DDR5 6800
• Gigabyte Gaming OC 4090, +25 core clock, +1025 memory over factory
• All system temps way below the threshold when playing DCS
• Varo Aero, running 35ppd, OpenXR, Automatic Vertical Sync with Motion Smoothing to "always on"
• Varjo Foveated with 1.3/0.80 with vertical and horizontal scale set to 1.2 and Turbo Mode to ON
• Latest DLSS 4 DLL installed via DLSS Swap
• Resizable BAR and DLSS profile "K" set in Nvidia profile inspector
• HAGS enabled in Windows 11 Prod
• VR pixel density in DCS at default 1.0

These are my DCS settings. This is while playing multiplayer with no mods. One of the mods I use in single player is supposed to reduce shadow impact, but at this point I can't tell any longer.
 

• nullnullAnti-Aliasing = DLAA
• Upscaling = DLSS
• DLSS Quality = Quality
• Sharpening = 0.30
• All textures = "high"
• Shadows = "low"
• Flat Shadow Blur = ON
• Secondary Shadows = ON
• SSS = ON
• Visibility Range = HIGH
• Civilian Traffic = OFF
• Water = HIGH
• Clouds = HIGH
• SSAO and SSLR = OFF
• Lens effects, Heat Blur, Motion Blur, DOF = OFF
• Volumetric Lights = ON
• Anisotropic Filtering = ON, 16x
• Terrain Object Shadows = DEFAULT
• Global Cockpit Illumination = OFF
• Rain Droplets = LOW
• Vsync = OFF
• Full Screen = OFF

With the above setup, provided something doesn't set my max power on the 4090 to 30% behind my back, is the overall smoothest and clearest DCS experience I have ever had so far. Stuttering is rare ... maybe a little if a whole bunch of stuff comes into view suddenly, such as when turning head to side quickly, but it's rare now.

DLSS 4 seemed to have really helped with the ghosting, which was previously TERRIBLE - especially when the Aero dropped to 45 hz and when full-on motion smoothing. With the above, now with DLSS 4 I stay at 90 hz most of the time, and even at 45 the ghosting is there, but noticeably less and bearable.

Some observations:

• With the above, setting the Aero to its "39 PPD" setting (which I think is simply a build-in supersample) I don't notice any difference in image quality, but performance seems to be a little worse but is still very good
• My overall performance is better with DLSS 4 ... I am at 90FPS a lot more, even flying low cities in the Persian Gulf or Siani. Syria is of course worse, but still a lot better than before.
• Varjo Foveated "Turbo Mode" really helps, and IMO that software still provides the best overall combination of clarity and performance. I just wish I could use OpenXR Toolkit to play around with the post-processing. The Quad Views application IMO performs worse and looks worse than Varjo Foveated. God help me if it ever stops working.
• I have a Somnium VR-1 ordered and hopefully will have it in a couple of weeks. Anxious to see how that all performs. I am 100% satisfied with the Aero's visual clarity even after all this time, I just wish they didn't abandon the product and had actually implemented local dimming, which is coming to the VR-1.

[Ready]

1 hour ago, mmike87 said:

So far, so good. Here are my specs and settings FWIW:

• 13900K, HT off, 5.6GHz all P-cores, .090mv undervolt
• 64GB DDR5 6800
• Gigabyte Gaming OC 4090, +25 core clock, +1025 memory over factory
• All system temps way below the threshold when playing DCS
• Varo Aero, running 35ppd, OpenXR, Automatic Vertical Sync with Motion Smoothing to "always on"
• Varjo Foveated with 1.3/0.80 with vertical and horizontal scale set to 1.2 and Turbo Mode to ON
• Latest DLSS 4 DLL installed via DLSS Swap
• Resizable BAR and DLSS profile "K" set in Nvidia profile inspector
• HAGS enabled in Windows 11 Prod
• VR pixel density in DCS at default 1.0

These are my DCS settings. This is while playing multiplayer with no mods. One of the mods I use in single player is supposed to reduce shadow impact, but at this point I can't tell any longer.
 

• nullnullAnti-Aliasing = DLAA
• Upscaling = DLSS
• DLSS Quality = Quality
• Sharpening = 0.30
• All textures = "high"
• Shadows = "low"
• Flat Shadow Blur = ON
• Secondary Shadows = ON
• SSS = ON
• Visibility Range = HIGH
• Civilian Traffic = OFF
• Water = HIGH
• Clouds = HIGH
• SSAO and SSLR = OFF
• Lens effects, Heat Blur, Motion Blur, DOF = OFF
• Volumetric Lights = ON
• Anisotropic Filtering = ON, 16x
• Terrain Object Shadows = DEFAULT
• Global Cockpit Illumination = OFF
• Rain Droplets = LOW
• Vsync = OFF
• Full Screen = OFF

With the above setup, provided something doesn't set my max power on the 4090 to 30% behind my back, is the overall smoothest and clearest DCS experience I have ever had so far. Stuttering is rare ... maybe a little if a whole bunch of stuff comes into view suddenly, such as when turning head to side quickly, but it's rare now.

DLSS 4 seemed to have really helped with the ghosting, which was previously TERRIBLE - especially when the Aero dropped to 45 hz and when full-on motion smoothing. With the above, now with DLSS 4 I stay at 90 hz most of the time, and even at 45 the ghosting is there, but noticeably less and bearable.

Some observations:

• With the above, setting the Aero to its "39 PPD" setting (which I think is simply a build-in supersample) I don't notice any difference in image quality, but performance seems to be a little worse but is still very good
• My overall performance is better with DLSS 4 ... I am at 90FPS a lot more, even flying low cities in the Persian Gulf or Siani. Syria is of course worse, but still a lot better than before.
• Varjo Foveated "Turbo Mode" really helps, and IMO that software still provides the best overall combination of clarity and performance. I just wish I could use OpenXR Toolkit to play around with the post-processing. The Quad Views application IMO performs worse and looks worse than Varjo Foveated. God help me if it ever stops working.
• I have a Somnium VR-1 ordered and hopefully will have it in a couple of weeks. Anxious to see how that all performs. I am 100% satisfied with the Aero's visual clarity even after all this time, I just wish they didn't abandon the product and had actually implemented local dimming, which is coming to the VR-1.

Nice!

So with your setup you don't really see a difference between 35ppd and 39ppd? I will check the same now DLSS4 is here.

Which Quad Views application do you refer to? I am using Mbuccia's QVFR and have OpenXRToolkit running for the performance overlay and some post processing effects sometimes. When I enable Turbo Mode inside OXRTK I don't see any difference in performance on way or the other.

Why are you automatic vertical sync and motion smoothing? For me that costs a lot. 

 

 

[Ready]

2 hours ago, mmike87 said:

I think i figured out my issues ... the drivers, DLSS, etc. were all red herrings ... I finally opened up MSI Afterburner that I use to apply a small core OC and the typical, 1000+ 4090 memory clock and I noticed my power limit was set at like 35%!!!!!!!!!!!!!

Not sure how this happened ... I have not even opened Afterburner in months. I think that all the nVidia App's "optimization" crap did something since it seemed to default to "on". I removed the nVidia App and will just use the profile inspector and the trusty nVidia Control Panel for as long as I can.

After restoring my power limit to 105%, I am smooth as silk again in Profile K.

What are your MSI Afterburner settings for the 4090? I am currently on +100 Core Voltage, +50 Core clock and +700 Memory Clock. I sometimes run Core Clock on +120 and Memory Clock on +900, which also seems to be sweet and stable, but I had a few crashes a while ago and I think it was caused by this OC (but it was with my previous W10 install) so I could experiment with upping it again..

[EightyDuce]

Best I've been able to get out of my 4090 is +210 Core and +2000(max allowed) Memory. That's with 135% PL and it draws 475-530w, turning my cooling into heating. Water temp gets to 40C just after the GPU waterblock. This is my "I need to render as many frames as physically possible by the hardware" preset... Mostly for VR lol. 

My daily for everything else is undervolted with a curve (boosts to 2750 core) at 950mV and +2000 on memory; this results in ~350w load. The reduction in performance (~10-15%) is is well worth ~30% reduction in power draw. Water temp 31C after GPU waterblock. 

[MAXsenna]

4090 
...and yes, I´m serious.
I installed a riser cable recently in order to have the card vertically mounted. Mainly due to space in the case rather than optics or anything...could this be a problem? The card works flawlessly otherwise.

Nah, if the card works it works, while the driver installation shield believe you have an incompatible card installed. I'd go with DDU, reboot back into Safe Mode an install the driver, then normal boot into Windows.

Sent from my SM-A536B using Tapatalk

[Phantom711]

@MAXsenna

So….I DDUed the <profanity> out of it last night. Still didn‘t work afterwards initially.

I rechecked and figured out, I had downloaded the Studio Drivers instead of the Game Ready Drivers. Note that they have the same number (572.16) and were the first (and only) ones I found. So I downloaded the Game Ready Drivers. In the filename of these it says something like „notebook“ or „laptop“ which was further confusing, but I gave it a shot. They installed without any problem.

I downloaded the latest CustomNameSettings.xml and put it in the NVPI folder. Unlike the tutorials I watched, I have an option in NVPI that says something like „DLSS Enable dll override“. It‘s right above the one with the Preset selection and I have to put it to ON for DCS to work. Otherwise mission load will crash. I can post a pic later today.

First impression of Preset J and K was, that it was a performance hit. But since NVCP is also gone, I still have to find all the respective settings in NVPI. The NV Ap is a joke with regards to options.

[MAXsenna]

@Phantom711 Right, have never tried Studio drivers. Haven't had time to test the new DLSS version yet. Hope you sort it out.

Sent from my SM-A536B using Tapatalk

[Phantom711]

@MAXsenna

My bad…the performance hit was my fault. I had played around with settings recently and DCS had an FPS cap set at 75 while my QPro was running at 80Hz. It‘s all smooth now.

I didn‘t do any extensive testing, so I really can‘t tell if it‘s better or worse. It looks good with DLAA, but without a side-by-side comparison, I don‘t see much of a difference.

[Qcumber]

4 minutes ago, Phantom711 said:

@MAXsenna

My bad…the performance hit was my fault. I had played around with settings recently and DCS had an FPS cap set at 75 while my QPro was running at 80Hz. It‘s all smooth now.

Schoolboy error

[Willie Nelson]

There seems to be an awful lot of system tweaking required for DLSS 4 to be get up and running, is there any time frame as to when we shuold be able to run it without all the back end hacks? I'm disinclined to start fiddling with it given my performance in VR is pretty decent as is.

[sleighzy]

1 minute ago, Willie Nelson said:

There seems to be an awful lot of system tweaking required for DLSS 4 to be get up and running, is there any time frame as to when we shuold be able to run it without all the back end hacks? I'm disinclined to start fiddling with it given my performance in VR is pretty decent as is.

Eagle Dynamics have said they're not planning on anything in that area until after Vulcan support.

Not sure what all the hacks are that you've been doing, it's just updating two fields in Nvidia Profile Inspector.

[Willie Nelson]

7 minutes ago, sleighzy said:

Eagle Dynamics have said they're not planning on anything in that area until after Vulcan support.

Not sure what all the hacks are that you've been doing, it's just updating two fields in Nvidia Profile Inspector.

Well somewhere between page 1 and 7, i got confused.

Are you talking about these two changes is the profile inspector?:

 

[sleighzy]

7 hours ago, Willie Nelson said:

Well somewhere between page 1 and 7, i got confused.

Are you talking about these two changes is the profile inspector?:

 

Yup, that’s the one. The ways of doing this evolved rapidly over the days as the tools got heaps better in a very short space of time, so yeah you’re right about the changes between pages 1 through 7. 

[Habu_69]

New Inspector V2.4.0.11 is different. How to adjust?

[sleighzy]

6 hours ago, Habu_69 said:

New Inspector V2.4.0.11 is different. How to adjust?

This is how the options appear for me now, a little more user friendly:

null