Qcumber

VD can be a bit twitchy sometimes unless you have very good latencies. Can you post a screenshot of your VD overlay (the one in your headset) then we can see what your latencies look like.

Sorry typo regarding VRAM. Thankfully I don't fly the Chinook. Please keep the "angry" bleed away from this thread otherwise it will deter new VD users. Your comments relate to very specific factors and it derails the point of this thread.

DLSS in DCS is an older version so using DLSS 4 and preset K will give you much better visuals. Sharper and much less ghosting.

Have you followed all the setup guide for VD, including using the right router setup etc?

Everything I have tested so far does not go above 13Gb with the 5080. Including F-4 on Marianas map on takeoff. But yes simpler maps and modules use much less.

You need to download NVIDIA profile inspector and then you can select to automatically use the most up to date DLSS release and can select preset K. https://github.com/Orbmu2k/nvidiaProfileInspector/releases Check out this thread too:

Is that VRAM allocation or VRAM use?

If it was early '90s it was probably a 386 or 486 with a 40 or 60 MB HDD. That was my first desktop PC.

I have found the best results with DLSS quality preset K. QVFR centre resolution set to equivalent of about 5000 pixels with peripheral about half native. This gives a really sharp image with no ghosting and good AA.

I've been there. That or accidentally putting my prescription lens inserts in the wrong orientation.

I gave up with Q link last night and switched back to VD. The latest update gives 2-pass encoding with good performance.

For me it appears random. Just sudden crash of link app. DCS still runs in the background. It usually happens within about 5 minutes of starting a mission.

5080 works fine with latest driver. I've had no issues with earlier drivers either.

To expand on this CPU or GPU limited is just a binary toggle in DCS. The reality is much more subtle. It's like 50 shades of grey. It's better to look at the CPU and GPU latencies and variance of overall frame time.

Good point. You have made me go upstairs to check now. All those wasted calories! VD 1.34.2 Meta 76.0.0.452.315

I have just updated to the latest update from meta (official not PTC) and I keep getting random dropouts. Connects ok but just randomly stops. Back to VD which is excellent since the last update.

Have you tried using Quad Views Foveated Rendering?

There isn't a huge difference in price for AIO liquid coolers and air coolers. I mainly went for the liquid cooler as I can access the motherboard without having to remove the cooler.

That might depend on what headset you are using. If I limit the FPS to 60 I do not get a smooth experience. I find that it is better to aim for an FPS which matches refresh rate. 72Hz most of the time although in light missions I can use 90Hz. I avoid using reprojection.

I like the look of the Pimax Dream Air SE

1) The tests above should state if DLSS is used and which preset. My default setup now is to use DLSS quality with preset K. I am in the process of comparing different presets which l will post when completed. There is a significant difference between "C" and "K". 2) If you are referring to reproduction then no, this is not applied. In terms of DLSS then frame generation does not work with VR.

The 5080 seems to particularly shine in VR (with racing sims at least).

I just did a quick test comparing preset C to preset K. I used the methods in the link. The results support what we have a all noticed. An increase in GPU latency. But there is also an increase in the CPU latency. Mean GPU increases from 9.5 to 12 ms. CPU increases from 6.5 to 8.8 ms. The FPS remains at a constant 72 FPS but there is lower variance in frame interval with C over K and a slightly smoother experience (92% vs 90%). All tests are done with DLSS quality and QFVR on Quest Pro. The same DCS settings in each run. PC specs are in the signature. Dark blue is "C". Light blue is "K" Test flight is F-16 flying over Syria from the instant action mission.

I stopped using PTC a while ago as the beta updates broke things for me more than once. I now just stick with official updates.