DLSS 4

[Ready]

2 hours 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
 

Thanks yes I have gone that route a coupleof times. It seems easier for me to roll back a few versions and then upgrade with the nvidia installers. I then don't have to boot in safe modes etc and I guess the end result is the same?

[MAXsenna]

Thanks yes I have gone that route a coupleof times. It seems easier for me to roll back a few versions and then upgrade with the nvidia installers. I then don't have to boot in safe modes etc and I guess the end result is the same?

What DDU does, to my knowledge, is to "completely" wipe any leftovers from older drivers etc. That could potentially conflict with newer drivers. So the answer is no. Especially if you go back and forth.
Now, DDU is not the Holy Grail I found out the hard way. I switch from two Titans to a 2080Ti. And a year ago when upgrading drivers DCS wouldn't even start. So I had to roll back to a previous driver, and even if that driver supported DLSS/DLAA, I couldn't even select the options for testing. Installing Nvidia Broadcast would fail every time, and I did notice some other nuisances. Last fall i decided to get to the bottom of it. Installed the latest driver, checked the Windows EventViewer and Googled the error in various ways. Finally I found mention of a Registry setting I had to remove. Did that and all of the problems above went away.

Sent from my SM-A536B using Tapatalk

[Fiztex]

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

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

I have a link cable as well and a Quest 3. Link at 900 Mbps looks worse than VDXR godlike at 500 Mbps H264+, even if you bring them both to the same render resolution. Oculus link is practically abandonware, VD became significantly better around mid 2023 and only becomes better. Link had some improvement recently (before it was even worse in performance to VD, a natural VRAM hog), but still not on par. If only Meta updated their encoding profile the case cold have been different, but they don't seem to bother. Hence all that BS with ethernet  cable, to squeeze maximum out of Quest...

Edited February 2 by Fiztex

[VR Flight Guy in PJ Pants]

Not sure the abandon ware part, but yup, VDXR is the way to go.

[Fiztex]

Только что, VR Flight Guy in PJ Pants сказал:

Not sure the abandon ware part, but yup, VDXR is the way to go.

Well, if you don't update the software for 2 years I'd say it is abandonware But indeed a couple months ago they suddenly fixed VRAM consumption problem without telling anyone, so maybe they'll fix the rest as well. Will see.

[VR Flight Guy in PJ Pants]

Fingers crossed for I am not using Link with DCS for a long time...

[gonvise]

2 hours ago, Fiztex said:

I have a link cable as well and a Quest 3. Link at 900 Mbps looks worse than VDXR godlike at 500 Mbps H264+, even if you bring them both to the same render resolution. Oculus link is practically abandonware, VD became significantly better around mid 2023 and only becomes better. Link had some improvement recently (before it was even worse in performance to VD, a natural VRAM hog), but still not on par. If only Meta updated their encoding profile the case cold have been different, but they don't seem to bother. Hence all that BS with ethernet  cable, to squeeze maximum out of Quest...

Sorry to disagree, but I think saying that the cable link is "abandonware" is very, very far from the truth. That the "god like" of Virtual Desktop is enough for you in your configuration seems very good to me, but with quest pro cable link, 900Mbps and, above all, supersampling x2 via OT, crisp and smooth like silk graphics... VD "god like" doesn't even come close, and if I try match SS2x resolution in VD, it's a stutterfest. Sorry, but no.

 

Edited February 2 by gonvise

[Qcumber]

2 hours ago, Fiztex said:

Link at 900 Mbps looks worse than VDXR godlike at 500 Mbps H264+, even if you bring them both to the same render resolution

With my setup I cannot get more than about 350 Mbps with VD. At that level my decide latency causes it to be a bit unstable. It's more stable with an ethernet cable but I have had issues connecting. Overall meta link gives me a smoother experience and is visually equal to VD. 

6 minutes ago, gonvise said:

Sorry to disagree, but I think saying that the cable link is "abandonware" is very, very far from the truth. That the "god like" of Virtual Desktop is enough for you in your configuration seems very good to me, but with quest pro cable link, 900Mbps and, above all, supersampling x2 via OT, crisp and smooth like silk graphics... VD "god like" doesn't even come close, and if I try match SS2x resolution in VD, it's a stutterfest. Sorry, but no.

 

I agree. With VD I need to boost the centre resolution up by about 1.2-1.3 on Godlike to get decent visuals. 

[GPatricks]

After all this DLSS stuff I ended up with MSAA 2x and my old 90FPS back.... 

[Fiztex]

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

Sorry to disagree, but I think saying that the cable link is "abandonware" is very, very far from the truth. That the "god like" of Virtual Desktop is enough for you in your configuration seems very good to me, but with quest pro cable link, 900Mbps and, above all, supersampling x2 via OT, crisp and smooth like silk graphics... VD "god like" doesn't even come close, and if I try match SS2x resolution in VD, it's a stutterfest. Sorry, but no.

Well, I disagree with that completely, and I'm not alone, very far from it. To not overload the topic with an off-topic discussion:

Спойлер

I did an extensive testing literally 2 months ago and it's simply not the case, otherwise I would not bother with an adapter. Even 4040 encode width with 900 Mbps doesn't compare to VDXR godlike with SSR enabled, even if you put PD 1.1 to make it close to VD in render resolution. I wish it was possible to demonstrate it but screenshots won't show it unfortunately since it happens due to compression, and on top Quest by itself compresses screenshots. Just a couple months ago link was asking 2.5GB more VRAM and was actually worse in performance vs VD at equal resolution. I was exclusively on link since Quest 2 times and VD was really worse till mid 2023, and could not believe that tweaked original solution can be worse than solution designed for WiFi, but since then it's somehow ahead, as simple as that. Hence abandonware conclusion, because if they actually bothered to change 2 lines of code we could have a much better Link and VD wouldn't be needed.

If you actually want to test the clarity I suggest to try some readability tables and patterns through OXR, if you don't see the difference in the cockpit immediately. I do see it in the cockpit though. Quest link obviously have a faster video compression profile which was probably selected towards better compatibility with older AMD cards which were really weak at H264. Those times long time gone, bit lack of choice is still there - you can't pick H264+ there. I admit it's not as bad as half a year ago (it's actually a tiny bit better now in VRAM consumption vs VD, which could be useful for 8GB cards), but link is still a tiny bit worse in visuals.

Plus usability is not even comparable. If link drops you are done untill game restart. If VD connection drops you can just reconnect. Helps a lot if you need to stop mid mission and come back later - you can even switch off the Quest completely.

I really have no idea what you can do to make VD at max bitrate look worse. Probably you are leaving dynamic bitrate on and getting 200 instead of full 500 of H264+, I seriously don't know. Or maybe something wrong with sharpening in one of the cases - VD gives smooth control over it where with Quest you only have 2 build in options. Or maybe it's Pro weirdness, I only had Q2 and Q3 to play with...

 

Edited February 2 by Fiztex

[Qcumber]

This has gone off topic. It should be about DLSS 4. 

11 minutes ago, Fiztex said:

Well, I disagree with that completely, and I'm not alone, very far from it. I did an extensive testing literally 2 months ago and it's simply not the case, otherwise I would not bother with an adapter. Even 4040 encode width with 900 Mbps doesn't compare to VDXR godlike with SSR enabled, even if you put PD 1.1 to make it close to VD in render resolution. I wish it was possible to demonstrate it but screenshots won't show it unfortunately since it happens due to compression, and on top Quest by itself compresses screenshots. Just a couple months ago link was asking 2.5GB more VRAM and was actually worse in performance vs VD at equal resolution. I was exclusively on link since Quest 2 times and VD was really worse till mid 2023, and could not believe that tweaked original solution can be worse than solution designed for WiFi, but since then it's somehow ahead, as simple as that. Hence abandonware conclusion, because if they actually bothered to change 2 lines of code we could have a much better Link and VD wouldn't be needed.

If you actually want to test the clarity I suggest to try some readability tables and patterns through OXR, if you don't see the difference in the cockpit immediately. I do see it in the cockpit though. Quest link obviously have a faster video compression profile which was probably selected towards better compatibility with older AMD cards which were really weak at H264. Those times long time gone, bit lack of choice is still there - you can't pick H264+ there. I admit it's not as bad as half a year ago (it's actually a tiny bit better now in VRAM consumption vs VD, which could be useful for 8GB cards), but link is still a tiny bit worse in visuals.

Plus usability is not even comparable. If link drops you are done untill game restart. If VD connection drops you can just reconnect. Helps a lot if you need to stop mid mission and come back later - you can even switch off the Quest completely.

I really have no idea what you can do to make VD at max bitrate look worse. Probably you are leaving dynamic bitrate on and getting 200 instead of full 500 of H264+, I seriously don't know. Or maybe something wrong with sharpening in one of the cases - VD gives smooth control over it where with Quest you only have 2 build in options. Or maybe it's Pro weirdness, I only had Q2 and Q3 to play with...

This is an interesting discussion. Could you please start a new thread. 

[Phantom711]

Hi...

I usually keep track of such things quite well, but this whole matter is a bit confusing. There are just so many variables...

Do we not have to rename some files anymore for this to work? That´s how it was previously, but nobody seems to mention it now anymore? Does that DLSSswapper do it for me? How would he know how the file needs to be named for DCS?

Also, there seems to be a new DLSS tweaker to set the desired Preset? So why are people now using NVidia inspector? Do I need both? 

[peachmonkey]

3 minutes ago, Phantom711 said:

Hi...

I usually keep track of such things quite well, but this whole matter is a bit confusing. There are just so many variables...

Do we not have to rename some files anymore for this to work? That´s how it was previously, but nobody seems to mention it now anymore? Does that DLSSswapper do it for me? How would he know how the file needs to be named for DCS?

Also, there seems to be a new DLSS tweaker to set the desired Preset? So why are people now using NVidia inspector? Do I need both? 

yup, the DLSSswapper does all the renaming/replacing for you...   Tweaker/Inspector are two apps that do a similar thing, I believe.  I personally used NVidia Inspector for the profile config.

edit:  dlssswapper works for Steam DCS only.

Edited February 2 by peachmonkey

[Qcumber]

2 minutes ago, Phantom711 said:

Hi...

I usually keep track of such things quite well, but this whole matter is a bit confusing. There are just so many variables...

Do we not have to rename some files anymore for this to work? That´s how it was previously, but nobody seems to mention it now anymore? Does that DLSSswapper do it for me? How would he know how the file needs to be named for DCS?

Also, there seems to be a new DLSS tweaker to set the desired Preset? So why are people now using NVidia inspector? Do I need both? 

DLSSTweaks was causing some issues when DLSS4 was first released. I think the latest release of DLSSTweaks works ok. The simplest method is replace the DLSS file in the DCS bin folder then use NVPI to change the preset. 

[sleighzy]

7 minutes ago, peachmonkey said:

edit:  dlssswapper works for Steam DCS only.

DLSS Swapper works for non-steam as well. Make sure you have the latest version and then click Add in the games tab and then add your top-level DCS game folder (not the bin and bin-mt)

[peachmonkey]

4 minutes ago, sleighzy said:

DLSS Swapper works for non-steam as well. Make sure you have the latest version and then click Add in the games tab and then add your top-level DCS game folder (not the bin and bin-mt)

rgr, thank you!

[Fiztex]

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

This has gone off topic. It should be about DLSS 4. 

This is an interesting discussion. Could you please start a new thread. 

Fair point, I've put that in the spoiler to not overload the thread. Was bored on my way home and typing on a phone, so didn't notice how long that ended up

[gonvise]

1 hour ago, Qcumber said:

This has gone off topic. It should be about DLSS 4. 

This is an interesting discussion. Could you please start a new thread. 

Sure! 

 

[sleighzy]

8 hours ago, Qcumber said:

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. 

Feel free to DM me with your DCS log file and crash zip file, I’m aware of some crashes. We can run through the DCS log analyzer, and additionally try options that don’t require dll replacements.

Edited February 2 by sleighzy

[Qcumber]

15 minutes ago, sleighzy said:

Feel free to DM me with your DCS log file and crash zip file, I’m aware of some crashes. We can run through the DCS log analyzer, and additionally try options that don’t require dll replacements.

I have managed to get it working. Not sure what I did but it now works. Thanks for the offer though. 

[mmike87]

9 hours ago, Spartan111sqn said:

Could you share your nvidia and in game settings please?

Well, it just so happens that everything I said was wrong. The driver update was NOT the cause of the huge performance drop ... as the next time I played, even with the Dev drivers, the issue came back. I re-installed the release drivers and was able to get it smooth again. But, the issue came back AGAIN after shutting down and coming back later today to fly some more.

I have now uninstalled the nVidia app and I'll see if that helps. I monitored my GPU and CPU when the performance was bad ... and 1 or 2 p-cores were pegged at 100% and the in-game FPS counter was red for CPU render thread. When it's smooth, it's not doing that. I messed with core affinities ... I have Process Lasso sticking the game on P-Cores 0-8 (HT is disabled) on my 13900k. Nothing is throttling ... when the FPS is bad, GPU is 50% or less, CPU package temps are about 52C, and no cores are thermal throttling. Everything else is shut down and what can't be shut down is running on and e-core via PL.

I may roll back to the previous DCS release. I have never had this issue before, and I moved to the latest release and DLSS 4 around the same time. It's not DLSS causing the issue, as I can fly with all AA off and the issue persists, until it magically goes away for awhile.

I swear this game is like dating a smoking-hot chick who is amazing in bed but occasionally goes nuts and throws things at you. Or, so I hear.

[Aapje]

I made a new topic for the video encoding discussion, with way for you to help to make it happen (perhaps):

 

 

[VR Flight Guy in PJ Pants]

This post here claims you need to update the Streamline also:

 

[sleighzy]

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

This post here claims you need to update the Streamline also:

 

Not sure if that applies here as DCS doesn't do frame generation.

[Phantom711]

nullWhat is that <profanity>? Why are they putting another pile of <profanity> in my way? Why is there no "Go <profanity> yourself and install anyways" button?

Any ideas anybody?

EDIT: Sorry for the rant...but stuff like this drives me crazy. 

Edited February 3 by Phantom711