Qcumber

@johnbowzer I would agree with slughead. It sounds like latency issues, probably the decode latency. Please can you post a screenshot of the VD overlay?

Have you tried XR necksafer? https://gitlab.com/NobiWan/xrnecksafer

The aim of these changes is first to see the best clarity of objects (as per op question), then to optimize for performance. DLSS is not a good option for clarity of objects. You need to find the right balance of SS, AA, refresh rate and game settings that works for you.

Try pushing SS higher. Turn off any antialiasing. Are you using any sharpening?

2024 has been a good vintage. A fine, acquired taste, which might not be for everyone. I'm looking forward to the 2025 harvest (although my wallet isn't; it's already hiding away somewhere).

You are really pushing the limits on your system. The decoding latency is very high. You want to keep it below 12 ms. Try using h264+ at 200. You could also reduce refresh rate to 72 Hz that would then allow you to increase the supersampling to 1.3 or higher. Then see how distant objects look. What AA are you using?

Thanks for the F5 update. It's my favourite jet. When you fly in VR the cockpit is not great so any improvement is greatly appreciated. Can I please ask that you do the same for the K4? It's my favourite prop plane. Even better, give us a 109 G6.

Looks amazing!

Spotting dots?

Try disabling OXRTK and any other open XR layers that you have active (e.g. XRNS).

Anyone fancy making this livery?

My Tamron 150-500mm is heavy but not as heavy as most. I mainly hand hold although I do have a monopod and gimbal head tripod. With second camera and a couple of other lenses, a folding stool, waterproofs etc., it adds up to quite a lot of weight!

I have tried DLSS 3.8.10 and have not noticed any significant improvement from the last version in terms of ghosting in VR using either preset E or F and various scaling settings. I have confirmed this version is running in the DLSSTweaks overlay. Quest Pro with VD and meta link. QVFR set with supersampling so centre resolution is equivalent to about 3300 pixels. Periphery about 1000 pixels.

OK. That's not what I am seeing with Quest Pro. I still have my Rift s so I might try comparing the two at different resolutions over the weekend.

That's what I said. 2000 pixels has bigger spotting dots. 4000 pixels has smaller spotting dots. In the same headset.

Not quite the same. With most VR headsets the best quality is with supersampling so someone running a Q3 at 2000 pixels would see bigger dots than someone running at 3000 or 4000. This is where the issue is and why it is so difficult for ED to solve.

That encode resolution is fine. However it is not the same as the output resolution. With the slider set to 1.2 your resolution is 2570x2752 per eye. You need to aim for about 3000x3300 for the best resolution. Leave the meta resolution slider at x1.0 and set the OTT supersampling at 1.5 to 1.7.

I think I'm lucky. Most people report 960 is too much.

VD does not support cable link as meta have not released the coding. The only way to connect via a cable now is by an ethernet adaptor which only helps with regards poor WiFi connection.

Default settings for Bitrate etc. However you will need to add some supersampling somewhere. If the resolution slider is set to x1 in the meta link app then set the ss value to between 1.5 and 1.7 and set sharpening to normal. See if that looks any better.

How do you get link cable to work through vd? Doesn't it need third part software?

Most of this looks OK. I prefer to set distortion curvature to normal and sharpening to "quality". You could try setting the FOV multiplier to 0.92, 0.92. Have you tried pushing the Bitrate to 960 Mbps?

That is not officially supported by VD.

Meta link software automatically defaults to ASW auto. OTT let's you switch it off and on (and other options).

It often does that. If you set it to off in oculus debug tool it keeps shifting on again. That's why I use the keybinds with OTT. Once set it stays set until you restart DCS.