Qcumber

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

This is a more extreme track. An F-4 take off from Syria. The results between the two runtimes are much closer although there is still more variation in GPU frametimes with VD. T12 is run using meta cable link (grey), T13 is with VD (green). Mean GPU time is 13.49 ms (Meta) vs 13.73 ms (VD). Mean FPS is 72.6 (Meta) and 71.4 (VD) Missed frames (those that exceed 13.9 ms) are 25% for Meta and 43% for VD Subjectively the experience was virtually identical between the two runs in terms of quality.

On a scale of 0-10 how fast?

I really hope they do. A 1943/1944 map would be great. Especially if expanded West across the Netherlands towards the UK. Long range missions.

Try enabling OXRTK and override the resolution there. Then you will have exactly the same resolution with meta and VD. Or just stick with VD if you are happy. After my testing above I am going to stick with meta app as this gives me significantly better performance and a more stable latency.

It does sound like something is not set up correctly. If you have OXRTK installed then you could override the resolution as I did above. Try setting it to 3072 x 3216 so that you know it is comparable.

I have done a comparison of VD versus Meta link in terms of performance. Quality is subjective but I could not see much difference between the two. To make sure that all settings were comparable I used OXRTK to override the resolution to 3072 x 3216. Both are run at 72Hz refresh. Link cable is using the settings above (but ignore the pixel setting as OXRTK has overridden it). VD is H.264+ at 200 mbps. WiFi 6 router with cat 6 ethernet cables. QVFR smoothen_focus_view_edges=0.1 sharpen_focus_view=0.2 horizontal_focus_section=0.25 vertical_focus_section=0.25 peripheral_multiplier=0.5 focus_multiplier=1.1 All DCS settings are identical. I ran a recorded track of an F-16 flying low over Syria (instant action free flight) for 60 seconds. These are the results. They are shown as a measure of GPU latency logged into bins of 0.1 ms. Each frame is counted and then allocated to the relevant bin. The taller parts of the chart show a higher number of frames falling into that bin. I ran each test three times. The purple traces (T1, 5 and 6) are the ones run using cable link. The blue ones (T2,3 and 4) are run using VD. This is a surprising result. I expected performance to be equal but clearly the meta link gives better performance. A mean GPU frametime of 9.62 ms vs 13.04 ms. A 3.42 ms difference. The red dotted lines show the 13.9 ms cut-off for 72 fps. Anything above this will result in missed frames. This is what the frametimes look like over the full 60 seconds. As you can see the VD trace (blue) is consistently higher latency with a lot more random spikes. GPU VRAM FPS Meta 9.62 7.22 72.1 VD 13.04 7.91 72.6 ms diff 3.42 0.69 0.58 VRAM was a little lower with meta link but mean FPS was the same. Basically, both meta link and VD can maintain 72 FPS, but VD is prone to much more variation in GPU frametimes which can lead to more jitter. EDIT: Fred Emmott has advised that it is difficult to directly compare GPU render times between different run times so please interpret this with caution.

These are my settings for the Quest Pro. The native resolution is 1808 x 1856 per eye. With a 1.73 Pixel override this is now 3127 x 3210. This is close to the Godlike resolution of 3072 x 3216. For the Q3 you will need a pixel override of 1.45 (native 2064 x 2208, x1.45 = 2993 x 3201. The values might be different when you look on the link app. I got these from a Google search. If you can't manage the 960 bitrate then try dropping to about 800. Its still a lot higher than you can get with VD. nullnull

Have you done the cable check test on the link app? It's in the device settings. I'll post my settings in a few minutes.

What is your slider setting in the Link app? To compare with VD godlike you need the overall scaling set to at least 1.45. It's easiest to do this in one place so leave it at 1x in the Link app and set it to 1.45 in ODT Otherwise you are running at native resolution of 2064 x 2208. VD Godlike is about 3072 x 3216.

Are you sure you are comparing the same resolutions? Also factor in different sharpness settings etc. I find that at the same final resolution they are both very similar in terms of quality.

Yes. QVFR works well. There is a setup guide on the GitHub site.

To expand on what LucShep said, VR is not plug and play and takes a lot of time and effort to get good results. Out of the box, and without any previous experience with VR, the results of any headset can be underwhelming. That said, if you don't get on with the comfort factor and "scuba dive" experience, then it's probably not worth taking further at the moment. It won't be long before we have much smaller form factor headsets at a reasonable price. By then hopefully they will be a lot easier to use.

Screen door is really obvious on the Rift S but I don't notice it on my Quest Pro. Weirdly I did on the Pico 4 even though it's higher resolution.

It's still the same. Just slightly wetter due to global warming.

I think it is "motion smoothing" but I don't have any experience with Varjo. It's a process for dropping the frame rate by half and "adding" extra frames.

Sorry. I thought you had a quest 3. ASW is the oculus reprojection. Do you have the Varjo equivalent of reprojection enabled?

Have you disabled ASW? What are your GPU frametimes? I would suggest using 72Hz refresh as this is less demanding. You get a smooth experience with up to 13.8ms. with 90Hz you need to maintain 11.1ms. I might be worth seeing what your performance is like without any Antialiasing to see if something else has changed on your system/settings that you are not aware of.

Typhoon fly past at RAF Coningsby for the funeral of Squadron Leader Mark Long last June who was killed whilst flying a Battle of Britain memorial Spitfire.

NVIDIA profile inspector. The latest version allows to to select "always use latest" for DLSS. You only need to reset this after an NVIDIA driver update.

Have you tried using Quad Views Foveated Rendering in fixed mode? https://github.com/mbucchia/Quad-Views-Foveated Also try using Virtual Desktop instead of Steam? It uses less VRAM.

If you use NVPI and the latest NVIDIA drivers it should automatically apply the latest version of DLSS. No need for DLSS tweaks anymore. Presets J and K come with a noticable impact on performance. I don't think anything has changed. I've certainly not noticed any difference in the last update. It might be worth clearing out your shader files and doing a slow repair.

Oculus Link is more stable for me. Very steady frametimes and smooth fps. With VD the frametimes are more erratic and there is microstutter. This is eliminated when I use an Ethernet cable to the headset but I can no longer get a decent bitrate this way. Overall, link cable is a better experience.

UK version cockpit. Not much space for a crew of three.

Just stick with one place then it's easier to work things out. I prefer to increase the resolution in the oculus app/oculus debug tool rather than in DCS.