After reviewing the LINK method and comparing it to VD method, honestly, Virtual Desktop wins for me. I am not sure what the problem with LINK is for my system, but it’s not working properly with MSFS2020 via the Oculus app and using the Oculus OpenXR runtime. Note that this could be only my system or some part of the chain that makes link have like 2x the latency for no reason. I have heard someone mentioned using a dedicated PCI hub for the link connection, but eh, VD just works
You can have network latency spikes with VD, sure, my router is downstairs as well, so my latency will probably be worse compared to someone who has their router next to the headset. Unless you have network problems, link in comparison just stutters and lags much more for some reason, also takes much longer to load into VR, sometimes freezes and gets stuck at home with a black screen, then you need to restart everything, and turn on link… then you start the Tray tool… Just too many steps?
I cannot say for sure why this happens and what the problem is for the link connection. All I know is, I managed to fit into 60ms total latency with VD, while via Link, the latency is always minimum 100 ms.
This does not make any sense at all, but it is what it is. Overall latency will always impact general smoothness of VR, so you want this as low as possible. On link there was clearly more stuttering.
If anyone wants to simply stop fiddling, and play the simulator, just use VD with the Quest 2 if you have a proper Wi-FI solution. Then, use High preset in VD settings, 90 FPS (could use the other fps modes for FPS test) and then set in game render scale to 70~. This will net you the best visuals (that are high res, and not low res + upscale like in the guide) for least performance impact. With this I was able to get 30-40fps with Almost native resolution. If you want higher framerates you WILL have to lower the render resolution of the MSFS2020 settings, even the 3090 can’t run biggest resolutions more than 35-45 fps.