Use Meta Quest 3 with Virtual Desktop in MSFS 2020: get the right VDXR launch order, network setup, Ctrl+Tab step and stutter fixes.
Yes. Meta Quest 3 works wirelessly with the PC version of Microsoft Flight Simulator 2020 through Virtual Desktop. Install Virtual Desktop on the headset and its Streamer app on the PC, select the VDXR OpenXR runtime, connect the headset, launch MSFS 2020, then press Ctrl+Tab to enter VR.
What do you need for Quest 3 and Virtual Desktop?
You need the Windows PC version of Microsoft Flight Simulator 2020, a Meta Quest 3, Virtual Desktop on the headset and the matching Streamer application on the PC. The Xbox version cannot send VR output to a Quest headset.
- Connect the PC to the router by Ethernet where possible.
- Connect Quest 3 to a nearby 5 GHz or 6 GHz Wi-Fi access point rather than a congested 2.4 GHz band.
- Keep the headset and PC on the same local network, without guest-network isolation.
- Use a mouse, keyboard, gamepad, yoke or HOTAS for reliable aircraft control. Quest controllers can operate parts of the cockpit, but support varies between aircraft.
Virtual Desktop does not make a weak PC suitable for MSFS VR. The computer still renders the simulator twice, encodes the result and streams it to the headset.
How do you set up Meta Quest 3 with Virtual Desktop?
The reliable method is to establish the Virtual Desktop connection and OpenXR runtime before starting Microsoft Flight Simulator 2020.
- Start the Streamer application on the PC and confirm that it recognises the account used by the Quest headset.
- Select VDXR as the OpenXR runtime in the Streamer settings. Automatic selection may also work, but explicitly choosing VDXR prevents another installed VR platform from taking control.
- Open Virtual Desktop on Quest 3 and connect to the PC. Make sure the Windows desktop is visible inside the headset.
- Launch MSFS 2020 from the streamed desktop or its normal PC launcher. Do not open SteamVR when using VDXR.
- Wait for the simulator to reach a usable menu or cockpit, give its window focus, then press
Ctrl+Tab. This invokes the MSFS command named Toggle VR. - Centre the cockpit view with the assigned Reset VR Camera control, then check that the mouse, flight controls and audio are using the intended devices.
Our detailed Virtual Desktop launch sequence covers the connection order and VDXR procedure in more depth.
Which OpenXR runtime should you use?
VDXR is the best starting point for Virtual Desktop because it connects MSFS 2020 to the headset without adding SteamVR between them.
| OpenXR runtime | Choose it when | Main consideration |
|---|---|---|
| VDXR | Using Virtual Desktop normally | Direct route with less software running between MSFS and Quest 3 |
| SteamVR | A specific add-on or VR workflow requires it, or VDXR fails on that PC | Adds another processing layer and must be the active OpenXR runtime |
| Meta runtime | Using Quest Link or Air Link instead of Virtual Desktop | Do not run a Link session alongside the VDXR connection |
Only one OpenXR runtime should handle the simulator. If the PC has been switched between Virtual Desktop, SteamVR and Quest Link, use our OpenXR runtime configuration checks to remove the conflict.
Why does Ctrl+Tab not switch MSFS 2020 to VR?
Ctrl+Tab usually fails because MSFS cannot see an active OpenXR headset, the simulator window lacks focus or the Toggle VR binding has been changed.
- Confirm the headset connection: Virtual Desktop should display the PC desktop before MSFS starts.
- Check the binding: search the MSFS Control Options for Toggle VR and assign it again if necessary.
- Close competing VR software: do not run Quest Link, Air Link and Virtual Desktop together. Close SteamVR when using VDXR.
- Restart after changing runtimes: fully close MSFS, change the OpenXR runtime, reconnect Virtual Desktop and relaunch the simulator.
- Check security software: allow the Streamer application through the Windows firewall if the headset cannot discover the PC.
If MSFS enters VR but the headset remains dark, follow our black-screen and launch-order troubleshooting.
How do you fix Virtual Desktop stutter in MSFS 2020?
First determine whether the delay comes from MSFS rendering, video encoding, the network or headset decoding; lowering simulator graphics will not repair a poor Wi-Fi connection.
Virtual Desktop's performance overlay separates these latency stages. If Game latency rises, reduce demanding MSFS settings such as render scale, clouds, terrain detail and traffic. If Network latency spikes, lower the streaming bitrate, use Ethernet between the PC and router, move closer to the access point and avoid mesh or repeater hops.
High encoding or decoding latency points to the streaming quality, bitrate, codec or other GPU workloads rather than scenery complexity alone. Set a sensible Virtual Desktop quality level first, then adjust the simulator's render scale; changing both at once makes the cause difficult to identify. Our MSFS 2020 VR optimisation settings cover the in-simulator side once the wireless link is stable.
Does Virtual Desktop need Quest Link or a USB cable?
No. The normal Virtual Desktop and VDXR setup streams across the local network and does not require an active Quest Link or Air Link session. A USB connection belongs to the Quest Link route; running both connection methods at once is a common cause of incorrect OpenXR selection and failed VR switching.