Qcumber

What do the rest of your VD latencies look like? Can you do a screen shot of the in game overlay? I suspect you are trying to run too high a bitrate. Anything over 200mbps for me at h264+ causes big networking and deciding latencies. You could try reducing this to 200. I gave also found that HEVC at 150 is more stable. Have you looked at your CPU latencies look like? Is the load spread over all CPU cores or maxing out on one?

In DCS for the standard scaling. In DLSSTweaks or NVPI for the bespoke scaling.

You can still change the scaling and you can see the difference between performance (0.5) and quality (0.66). You can also set bespoke scaling. I have tried up to 0.9 and this gives you great quality but with better performance than DLAA.

I've got +420 and +2000 stable in DCS..I can manage higher in synthetic benchmarks but it does not carry through to DCS. It might be because I use DLSS.

I did a quick test comparing DLSS K using DLSSTweaks and NVPI Resolution set to 4900x5000 in OXRTK Quest pro with Meta cable link at 72Hz smoothen_focus_view_edges=0.1 sharpen_focus_view=0.2 horizontal_focus_section=0.28 vertical_focus_section=0.28 peripheral_multiplier=0.28 focus_multiplier=1.0 All DCS settings were the same. Driver 572.82 This is a recorded track of an F-16 flying over Syria map (F-16 instant action free flight) for 1 minute. DLSS 3.10.2 quality (set using either DLSSTweaks (T1, blue) or NVPI (T2, purple) [I ran the one with NVPI before installing DLSSTweaks]. As you can see there is no difference with a 5080, although there were slightly fewer dropped frames using NVPI (0.2% vs 2.8%). Another test comparing preset K (T1, blue) with preset C (T3, green). Both are using DLSSTweaks. In this case, as expected, "C" has a shorter GPU latency than "K" (8.65 ms vs 10.04 ms) but was a noticeably softer image. I was unable to properly compare ghosting in this track. CPU latencies for the same runs.

Thanks for the heads-up. I might give it a go and see if it makes a difference for me. What does ghosting look like for you with these settings?

OXRTK still has some relevance but it's not a magic bullet. Turbo mode can help but it can also make things worse in some cases. It very much depends on your setup. If it works for you now that's great but it's not something that should be automatically enabled by everyone in VR.

Try OTT

This is the encode resolution. It is different to the rendering resolution. This is set through supersampling. The native resolution of the Quest Pro is about 1900 x 1800. Super sampling of 2 would give you 3700 x 3600. It would be worth mentioning that super sampling can be set in several places so it can become confusing. It's best practice to use a single place for SS. For example set the resolution slider in the Meta app to x1 and pixel density in DCS to 1. Then use OTT or ODT to SS to at least 1.5 native resolution. It might be worth posting some starting settings which match different CPU/GPUs. It might be worth having some starter settings here and expectations. Especially regarding presets. DLSS 4 is very good but you need to SuperSample very high to get rid of ghosting. I use a QVFR foveated SS of equivalent to 5000 pixels and then about 1500 for the periphery. This gives very good results with DLSS quality preset K. Equivalent to DLAA with a much lower impact on performance. Thanks for putting this together. I think it will be very useful for VR newbies.

You will need to restart DCS after each change. Another option is Oculus Tray Tool. It accesses all the same settings as ODT but you can use it from your desktop so its a bit easier. https://www.guru3d.com/download/oculus-traytool-download/

Being CPU limited in the DCS monitor does not necessarily mean that what you might think. It's best to look at your CPU and GPU render times in OXRTK or XRFrametools (or similar). This will give you a much better idea if how much load is on your CPU and GPU. Also look at individual core performance of your CPU to see if a single core is maxed out. OXRTK is an add on tool. It does not replace ODT. Although it is no longer officially supported it still has some useful tools.

It sounds like Asynchronous Space Warp us kicking in. Try disabling this in Oculus Debug Tool. You can also change these on the fly with these keybinds CTRL+KP1 - Disable ASW and USE ATW CTRL+KP2 - Force apps to 45hz, DISABLE ASW CTRL+KP3 - Force apps to 45hz, ENABLE ASW CTRL+KP4 - Enable ASW to operate automatically I would advise looking at your CPU and GPU latencies in the DCS FPS game overlay or better still using OXRTK. This will let you know how close you are to maintaining 72 FPS. The magic number for you GPU is 13.88ms. Having recently had chance to try the 5070ti you should be able to maintain 72 fps in most situations. Don't forget that VR is like running two 4k monitors so it is very demanding.

I did a test comparing performance with preload at 60 vs 150. There was a small difference in GPU latency and about a 1Gb difference in VRAM use.

I was just interested to see if it helps VR. From your comment I would suggest not.

I am having the same issue. I ran the crash log through the discord log analyser and this is the report. "Errors There is a GPU-related error (Re-)install the latest GPU drivers. Don't overclock your GPU or RAM. Your DCS has crashed The crash occurred inside dx11backend.dll. Try a !repair. Delete Saved Games\DCS\fxo and metashaders2 and try again. Next, delete %LOCALAPPDATA%\TEMP\DCS and try again. Next, try renaming Saved Games\DCS to DCS.old and try again. Stacktrace (dx11backend): RenderAPI::DX11Renderer::setNewFrameBuffer + 0x37 (dx11backend): RenderAPI::DX11Renderer::pushFrameBuffer + 0x68 (SceneRenderer): BRDFRenderer::onWaterUpdated + 0xBA8 (SceneRenderer): DCSSceneRenderer::updateAuxViewport + 0xCEDA (GraphicsCore): render::BaseRenderingPass::execute + 0x27 [...] Carry out the suggested repair steps one after the other. If all fails, open a !support ticket." I have tried all these options and it still crashes. Everything works fine when Motion Blur is disabled. dcs.log-20250406-104152.zip

I would also factor in eye tracking as it can give a big performance boost.

I think I have discovered the issues I have been having with VD. Everything is much better with HEVC. With my 4070 h264+ was always a better choice as HEVC had too long a decode latency. With the 5080 this latency is much lower. h264+ is not very stable with the 5080. I wonder if it a driver issue?

Great. Thanks. I just want to see what it's like for a full blown air battle. An air start is fine. Cheers.

Only just seen this so late to the party. Great vid. Do you have the mission file for this? I'd like to give it a go.

Thanks. I do use a dedicated router. I can get around 350-360 Mbps but the network latency is to high and the deciding latency becomes high and/or very unstable. HEVC works fine at 150 but again the decoding latency causes too much lag. This is especially noticeable when you move your head quickly. I found the optimal setup is h264+ at 200 Mbps. The only way to overcome these limitations is to use an ethernet cable (it requires an Android hack of the headset but it works). I can then get 400 Mbps and a low network/decode latency. However, this still lags behind the Meta app at 960 Mbps. The image quality of the two is comparable but the difference in latency and variation in frame times is noticeable. Are you sure that when using the meta app your are at the same resolution as VD Godlike?

I'll post some me screenshots of my settings later. With GPU-Z the o/c is about 3060. However the actual boost clock speed running on MSI Afterburner is 3320. This drops to about 3150-3220 when running DCS missions. I don't fully understand the reasoning so perhaps others can comment.

It is strange how different setups can behave so differently. I would prefer to use VD but I just cannot get it to work as well as meta link. What Bitrate are you managing on your network? I wonder if my router is an issue. I can't get above 200 with WiFi without a big increase in latency and there are lots of frame spikes. With an ethernet cable I can manage 400 Mbps and it's smoother but still not as good as with Meta.

Yes. MSI Afterburner. The review by TechPowerUp managed to get a 12% boost with Time Spy Extreme but they managed to overclock the core to +500 and memory to +3000. I can get the core clock stable to +447 with synthetic benchmarks but it's not stable in DCS. It's probably related to DLSS4 and preset K as these are supposed to be temperamental l to overclocking. It depends on how much you paid and if you can get a better deal. I was lucky to get the FE at MSRP. I had bought a 5070ti for £799 but then managed to get the 5080 for £949 which is what I really wanted in the first place. So the 5070ti went back.

Hopefully that won't affect performance. You should be able to get a decent overclock with that. I can manage +420MHz core clock and +2000MHz memory. That gives me a base if 3320MHz clock boosted and about a 10-11% increase in synthetic benchmarks.

Great to hear you are getting good results. Which card have you got (manufacturer) and have you tried overclocking yet?