DLSS 4

[sleighzy]

4 hours ago, Roosterfeet said:

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.

You might be better off going to the previous 3.8.10 version that we used to use and the E / F presets for further reduced ghosting. Presets E and F are still present on the latest one, and as far as I'm aware aren't new transformer models so should still work there too.

[nikoel]

Sign me up to the .96 team

Just updated from the “leaked” version to the newest and had massive performance issues that some reported

Went back to .96 with Profile J and all the issues went away. Duno ¯\_(ツ)_/¯ 

P.S. neither had the NVIDIA app installed. As lean and mean of an installation as it gets 

Edited February 2 by nikoel

[YoYo]

I've heard that DLSS Overwrite doesn't work with DCS though, so you can't officially test DLSS4. Is there any idea for a quick installation and test of DLSS4 without additional programs? Just replacing the appropriate files?

10 hours ago, Qcumber said:

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. 

So it turns out that this is not some Holy Grail for Sims users. I suspected so. As long as ghosting is visible and one pixel is invisible (spotting dots) then it is still an option associated with a compromise. Probably not for me, these are "no-go" elements.

[Fiztex]

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

 

So it turns out that this is not some Holy Grail for Sims users. I suspected so. As long as ghosting is visible and one pixel is invisible (spotting dots) then it is still an option associated with a compromise. Probably not for me, these are "no-go" elements.

I think you should try for yourself, everything is very subjective. E.g. I'm definitely not going back to old DLSS or MSAA, have no issue with the gameplay whatsoever with new DLAA. 

[VR Flight Guy in PJ Pants]

Balanced setting for DLSS generates longer trailer, regardless the subject is above or below me, it is worse.

[Fiztex]

People sensitive to smearing should only use DLAA without downsampling of DLSS, and adjust their render resolution and QV settings till needed performance level vs visual quality balance is reached.

[YoYo]

2 hours ago, YoYo said:

I've heard that DLSS Overwrite doesn't work with DCS though, so you can't officially test DLSS4. Is there any idea for a quick installation and test of DLSS4 without additional programs? Just replacing the appropriate files?

I found this quite easy method:

 

[Esac_mirmidon]

Its working, wonders, for DCS, for sure, both 2D and VR.

Before this new .dll, for me, 2D, any DLAA or DLSS was a blurry, ghosting mess.

Now is crispy, just some minor ghosting, and all MSAA jagginess gone.

 

[YoYo]

7 minutes ago, Esac_mirmidon said:

Its working, wonders, for DCS, for sure, both 2D and VR.

Before this new .dll, for me, 2D, any DLAA or DLSS was a blurry, ghosting mess.

Now is crispy, just some minor ghosting, and all MSAA jagginess gone.

 

Thx I'll try. Generally I'm happy still with MSAA in VR and it still works for me, it's ok, I don't complain about the performance in DCS at all, but on the other hand using DLSS you can increase the resolution because there will be an increase in performance, so with DLAA you can still have a sharp image, but for me the obstacle was too blurry image with DLSS 3 in VR plus ghosting. This was a barrier for me with DLSS 3. I'll check this DLSS 4, thanks. 

[Esac_mirmidon]

You will be pleased...

 

[Fiztex]

46 минут назад, YoYo сказал:

Thx I'll try. Generally I'm happy still with MSAA in VR and it still works for me, it's ok, I don't complain about the performance in DCS at all, but on the other hand using DLSS you can increase the resolution because there will be an increase in performance, so with DLAA you can still have a sharp image, but for me the obstacle was too blurry image with DLSS 3 in VR plus ghosting. This was a barrier for me with DLSS 3. I'll check this DLSS 4, thanks. 

Try setting PD 1.2 in DCS and enabling DLAA without DLSS J/K - beats MSAA 4x+MFAA for sure, and 4090 is well capable of that with Quest Pro + VDXR Godlike. QV helps a ton as well if not CPU limited as DLAA is excellent at blending the low res periferal section of QV.

Edited February 2 by Fiztex

[MAXsenna]

@Ready A little late. If you boot up in Safe Mode and use DDU to wipe the drivers. You should be able to revert back to any driver.
Press LWin+R on your keyboard. Type in msconfig, press Enter. Click the Boot tab and select Safe Mode, click OK, and reboot. Run DDU, config it. Select GPU and remove drivers with reboot. Wait, let it reboot. Install drivers. DON'T let it reboot. Run msconfig again. Select normal boot. OK, and boot. That's it.

Sent from my SM-A536B using Tapatalk

[YoYo]

18 minutes ago, Fiztex said:

Try setting PD 1.2 in DCS and enabling DLAA without DLSS J/K - beats MSAA 4x+MFAA for sure, and 4090 is well capable of that with Quest Pro + VDXR Godlike. QV helps a ton as well if not CPU limited as DLAA is excellent at blending the low res periferal section of QV.

In DCS I have 1.0 but Im using OTT (for Meta Quest) for upscaling with better results (like FOV etc. However thx for the tip.

15 minutes ago, MAXsenna said:

@Ready A little late. If you boot up in Safe Mode and use DDU to wipe the drivers. You should be able to revert back to any driver.
Press LWin+R on your keyboard. Type in msconfig, press Enter. Click the Boot tab and select Safe Mode, click OK, and reboot. Run DDU, config it. Select GPU and remove drivers with reboot. Wait, let it reboot. Install drivers. DON'T let it reboot. Run msconfig again. Select normal boot. OK, and boot. That's it.

Sent from my SM-A536B using Tapatalk
 

I don't know if you know but there is an easier way to start safe mode in Windows. Use the Start menu > click LShift and hold > click restart (Windows).

After starting you will immediately have The safe mode. I always use this to remove drivers using DDU.

[Fiztex]

2 часа назад, YoYo сказал:

In DCS I have 1.0 but Im using OTT (for Meta Quest) for upscaling with better results (like FOV etc. However thx for the tip.

Unless you use ASW I seriously suggest running VDXR Godlike instead as it is simply superior to whatever you can get through ODT/OTT. You can connect via RJ45 cable as well and avoid WiFi troubles. Use H264+ 500 Mbps. Use 400 Mbps for Quest Pro and 500 Mbps for Quest 3.

As for the resolution it indeed doesn't matter how you force the game to render the pixels you need, you just need to do it to not have issues with spotting dots when using temporal AA like DLAA. You should target something like 3500 pixels before foveating and then apply DLAA on top.

Edited February 2 by Fiztex

[MAXsenna]

41 minutes ago, YoYo said:

I don't know if you know but there is an easier way to start safe mode in Windows. Use the Start menu > click LShift and hold > click restart (Windows).

After starting you will immediately have The safe mode. I always use this to remove drivers using DDU.

Thanks! I had forgotten about that one.  

I just use msconfig so regularly, and then I don't have to remember pressing the sequence as I'm always juggling multiple things at once.

[VR Flight Guy in PJ Pants]

35 minutes ago, Fiztex said:

You can connect via RJ45 cable as well and avoid WiFi troubles. Use H264+ 500 Mbps.

Seriously want to know how.

13 minutes ago, MAXsenna said:

Thanks! I had forgotten about that one

DDU is a must. I would avoid both OTT and the NVIDIA app...

Edited February 2 by VR Flight Guy in PJ Pants

[MAXsenna]

DDU is a must.

I was referring to the key sequence, not DDU!

Sent from my SM-A536B using Tapatalk

[VR Flight Guy in PJ Pants]

Alright, I will give you a pass this time.

[MAXsenna]

1 minute ago, VR Flight Guy in PJ Pants said:

Alright, I will give you a pass this time.

Excellent!

1 hour ago, MAXsenna said:

click OK, and reboot. Run DDU, config it. Select GPU and remove

For prosperity. 

[VR Flight Guy in PJ Pants]

Just now, MAXsenna said:

Excellent!

(In Bill and Ted's voices, but don't link me to that hardware YouTuber)

To be fair, using the VD performance indicator says I am at 60fps as I have forced the FG, SR, and RR enabled using the NVIDIA Inspector. still a little blurry and a little comet like for anything moving things below the horizon. I am quite happy. I am doing an A/B test later.

[Spartan111sqn]

On 2/1/2025 at 12:12 AM, 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? 

Could you share your nvidia and in game settings please?

[Qcumber]

54 minutes ago, Fiztex said:

Use H264+ 500 Mbps.

How do you get 500mbps with a QP?

[Qcumber]

DLSS 4 is still crashing for me. CTD after about 1-2 minutes. I have removed all DLSS tweaks files, tried all versions of the DLSS 4 versions. Tried J and K. Multiple repairs of DCS then replace the DLSS file. It still crashes every time. 

[Fiztex]

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

How do you get 500mbps with a QP?

Sorry, probably 400 is indeed the limit on Pro, 500 is for Quest 3. 400 is still going to be better than Oculus link IMHO.

Edited February 2 by Fiztex

[YoYo]

1 hour ago, Fiztex said:

Unless you use ASW I seriously suggest running VDXR Godlike instead as it is simply superior to whatever you can get through ODT/OTT. You can connect via RJ45 cable as well and avoid WiFi troubles. Use H264+ 500 Mbps. Use 400 Mbps for Quest Pro and 500 Mbps for Quest 3.

As for the resolution it indeed doesn't matter how you force the game to render the pixels you need, you just need to do it to not have issues with spotting dots when using temporal AA like DLAA. You should target something like 3500 pixels before foveating and then apply DLAA on top.

Thx. However I dont use ASW, dont like it. Prefer stable 72 FPS with 72 Hz. Only PCVR (Link cable, 650mbps) .

Edited February 2 by YoYo