Qcumber

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.

If ASW is disabled you should just see the actual FPS. It will only toggle between 72 and 36 if ASW is auto. I usually leave this to auto but there are some situations where I want it off or forced on. My Encode Resolution is the same as yours but I run the Bitrate at 960. Just to clarify I am using a Quest Pro.

Use the Tray Tool keybinds to set the various ASW toggles. That way you can change on the fly. I have mine mapped to my HOTAS via JoytoKey. I switch between on (auto), off and forced in.

Godlike is OK but only with QVFR. Full frame at Godlike taxes even a 4090.

QVFR also works in fixed foveated mode. This means that peripheral vision is reduced. This can be set so it is less noticeable but gives you a significant performance boost. It offsets some processing from GPU to CPU. As you have a lot of CPU room it could make a big difference. Yes. Everything above assumes you (op) are using a decent cable which meets the meta link minimum requirements.

I would start by making sure you have optimal settings with meta link. Inactivate any open XR layers or mods. The meta link app defaults to x1 resolution which is not the full native resolution of the headset for some reason. Set the slider to 1.5 and see how the resolution looks. From that baseline you can start to adjust for performance. With your setup you will probably need to settle for 72 Hz with reprojection most of the time at moderate DCS settings. The next thing to try is Quad View Foveated Rendering. Try this at default fixed foveated settings and see how it looks. Leave turbo mode enabled as this might help smooth things out. Are you using default meta settings? If so then next thing to try is to use Open XR toolkit to adjust the bitrate. I can manage up to 960 Mbps but some people have problems this high so try about 500. You can also reduce the rendered FOV to about 0.92x0.92 which saves a bit of performance. Can you post a screen shot with the DCS with the FPS/frame time overlay so we can see what it looks like when you get stutters.

I have both the rift s and Quest Pro. I previously owned a Pico 4 which has the same resolution to a Q3. You should be able to run a Q3 OK on a 3080 but with compromises. I can suggest some starter settings if that would help.

Your decoding latency is a bit high so you might try reducing the bitrate to 150, or perhaps try h264+ at 200. Have you tried enabling video buffering? This gives a smoother experience. Is that a representative test situation for you? i.e. is this average performance or is it in a stress situation? If the former then I would suggest reducing some graphics settings as your game latency is quite high.

I would recommend posting an image of the in game overlay. This is enabled in the streaming options tab. That way we can see your bitrate and latencies etc. The best codec can depend on your bitrate. For example, I use h264+ with my Quest Pro. The max bitrate I can get with my router setup is about 300-350 Mbps but the decoding latency is about 13-14ms. At 200 Mbps I get a decoding latency of 8-10 ms and overall a much smoother experience.

Some photos from Duxford finale air show last month

Aliasing is better with DLAA or DLSS but you have to accept the (variable) ghosting.

VD works best with a dedicated router. I bought my WiFi 6 router for about £40 and don't run anything else from it. It's connected to my pc by ethernet cable and is about 2-3 ft from my headset. https://amzn.eu/d/4QBvsbN WRT meta link are you using a decent cable? I use this one from Amazon. https://amzn.eu/d/26BjWcA

It was good thanks. I got a few good pics but have not had chance to post any yet. I'm off this week so will upload some.

XR necksafer is the one to use now. https://gitlab.com/NobiWan/xrnecksafer

By my reckoning this means that your output resolution will be about 2300. I'm not at my computer but I think the resolution at x1 in meta link is about 1750. So 1750 x PD 1.3 = 2275. Ideally you want to aim for the native resolution of the headset x1.5 for a total of 3312 (2208x1.5). This is the "godlike" setting used in Virtual Desktop. It will make the image look a lot sharper and more detailed and spotting dots should look a better size. You can set the resolution in OTT but leave PD at x1 in DCS. If your base resolution is 1750 you will need to dial in x1.9 in OTT to get 3312 pixels. Have you tried using QVFR? You can use this to set the centre resolution to x1.9 and leave the periphery at x1. This would give you centre clarity without impacting too much on performance.

What are your settings in meta link? Do you have the resolution slider set to 1 or pushed to the right for max resolution? Any other supersampling via Oculus Tray Tool or oculus debug tool? The reason I ask is that it is difficult to compare between headsets without knowing what the final supper sampled-resolution is. For example, someone running a Q3 with an output of 2700 pixels is going to see bigger dots than someone running at 3500 pixels. I run my Quest Pro at 3500 pixels (centre Res equivalent via QVFR) and the dots don't look too bad.

What headset are you using? If possible avoid using Steam VR. QVFR works very well with Virtual Desktop including turbo mode. You might want to try that.