Set up Virtual Desktop for Oculus or Meta Quest flight sims with the right network, OpenXR runtime, launch order and fixes for blur or stutter.
To use Virtual Desktop with a Meta/Oculus Quest for PC flight simulation, install Virtual Desktop on the headset and its Streamer app on the PC, connect the PC by Ethernet to the local router, select the simulator’s VR runtime, connect from the headset, then start the simulator and enter VR mode.
For PC flight simulation generally, the Quest is a wireless PC-VR display; the gaming PC still runs the simulator. Virtual Desktop cannot add VR support to a simulator that does not provide it, and it does not replace a yoke, joystick, throttle or pedals.
What do you need for Virtual Desktop flight simulation?
You need a VR-capable Windows PC, a supported Quest headset, the Quest edition of Virtual Desktop, its PC Streamer companion and a strong local network. Installing only a desktop edition of Virtual Desktop is not enough; the headset app and Streamer perform the wireless PC-VR connection.
- PC connection: Connect the computer to the router or access point with Ethernet rather than Wi-Fi.
- Quest connection: Use 5 GHz Wi-Fi, or 6 GHz where both the router and headset support it. Keep the headset close to the access point.
- Local network: Put the PC and Quest on the same LAN. Guest networks, wireless client isolation, VPNs and some mesh repeaters can prevent discovery or add latency.
- Flight controls: Connect the joystick, yoke and pedals directly to the PC. Quest controllers are mainly for VR menus and supported cockpit interaction.
Internet download speed is not the main factor once connected: the VR video stream travels across the local network. If the headset cannot find the computer, our Quest-to-PC connection checks cover account, pairing, network and firewall problems.
How do you set up Virtual Desktop for a Quest flight sim?
Install both parts of Virtual Desktop, establish the wireless desktop connection and choose the correct VR runtime before opening the simulator.
- Install the headset app: Add the Quest edition of Virtual Desktop to the headset and allow it to update.
- Install Virtual Desktop Streamer: Install the companion Streamer on the flight-sim PC. Enter the Meta account identity requested by the app and leave Streamer running.
- Prepare the network: Wire the PC to the router, connect the Quest to its fast Wi-Fi band and avoid guest or isolated networks.
- Set a conservative baseline: Use automatic codec selection, a moderate streaming bitrate and the lowest practical headset refresh rate. Medium streaming quality is a sensible starting point for an untested PC.
- Select the VR route: Choose VDXR for a native OpenXR simulator such as Microsoft Flight Simulator, or SteamVR when the title specifically requires SteamVR/OpenVR.
- Connect from the Quest: Open Virtual Desktop in the headset and select the PC shown by Streamer.
- Launch the simulator: Use Virtual Desktop’s Games panel for recognised VR titles, or display the Windows desktop and start a standalone flight simulator normally.
Do not open an Air Link session at the same time. Virtual Desktop is already providing the PC-to-headset transport, and running two VR connection systems commonly causes incorrect runtimes, audio switching and failed launches.
Which OpenXR runtime should you choose?
Choose VDXR first for a native OpenXR flight simulator; use SteamVR only when the simulator or a required add-on depends on it.
| Runtime route | Choose it when | Main consideration |
|---|---|---|
| VDXR | The simulator supports OpenXR directly, including Microsoft Flight Simulator 2020 and 2024 | Usually avoids the extra SteamVR layer when streaming through Virtual Desktop |
| SteamVR | The simulator uses SteamVR/OpenVR or does not work correctly through VDXR | Adds another VR layer and must be running before a SteamVR-only title enters VR |
| Automatic | You use several VR applications and they already launch through the intended runtime | Convenient, but explicit VDXR or SteamVR selection makes troubleshooting easier |
Set the runtime before starting the simulator. If you change it while the sim is open, close the simulator completely and relaunch it. Microsoft Flight Simulator users can follow our steps for confirming the active MSFS OpenXR runtime.
How do you start a flight simulator in VR?
Connect the Quest through Virtual Desktop first, then launch the simulator and activate its own VR mode.
For Microsoft Flight Simulator 2020 or 2024, start the simulator on the virtual desktop, load into the cockpit and switch to VR. The default VR toggle is normally Ctrl+Tab unless it has been rebound. Our MSFS-specific Virtual Desktop sequence covers the exact launch order and VDXR setup.
Other simulators may use a VR checkbox, a dedicated VR executable or a launcher option. Start SteamVR only if that simulator requires it. Once inside the cockpit, recenter the view using the simulator or headset command so the virtual seat aligns with your physical position.
Getting a clear and responsive cockpit
A stable baseline at moderate quality is better than maximum resolution with missed frames and network spikes. Change one setting at a time so the cause remains obvious.
- Start with refresh rate: Use a lower refresh rate first. Raising it increases the number of frames the PC must render, encode, transmit and decode every second.
- Adjust rendering before bitrate: If the simulator cannot maintain frame rate, reduce Virtual Desktop quality or the simulator’s render scale. Traffic and complex scenery often burden the CPU; render scale, clouds and shadows usually place more load on the GPU.
- Raise bitrate carefully: Increase streaming bitrate only while network latency remains stable. Excessive bitrate causes stutter even when the PC renders the simulator fast enough.
- Leave codec selection automatic initially: Codec support depends on both the graphics hardware and Quest model. Manual codec changes are useful only after establishing a stable baseline.
- Use spacewarp deliberately: Synchronous Spacewarp can make a simulator feel smoother when it cannot hold the headset refresh rate, but propellers, gauges and cockpit edges may show artefacts.
Virtual Desktop’s performance overlay separates game, encoding, network and decoding delay. High game latency points to simulator or PC settings; network spikes point to Wi-Fi or bitrate; encoding or decoding delay calls for lower streaming quality, bitrate or refresh rate.
If the PC cannot be wired to the router, or the Quest must connect through a distant mesh node, a wired Quest Link connection is often more dependable. Lowering cockpit graphics cannot repair an unstable wireless path.
Virtual Desktop flight-sim troubleshooting
Most failures come from PC discovery, runtime selection, launch order or an overloaded wireless connection.
- The PC does not appear: Confirm Streamer is running under the expected account, both devices are on the same local network and the Windows network is not treated as an untrusted public connection. Temporarily disconnect VPN software and avoid guest Wi-Fi.
- The simulator remains on a flat screen: The desktop stream is working, but the sim has not entered VR. Activate its VR mode and verify that VDXR or SteamVR matches the simulator.
- SteamVR opens unexpectedly: Recheck Virtual Desktop Streamer’s OpenXR runtime selection, close both SteamVR and the simulator, then relaunch. Some older titles genuinely require SteamVR, so do not force VDXR where it is unsupported.
- The image is sharp but head movement stutters: Reduce refresh rate and inspect the performance overlay. Stable game timing with network spikes usually means Wi-Fi congestion or excessive bitrate.
- The cockpit is blurry but motion is stable: Increase streaming quality or simulator render scale gradually. Cockpit text benefits more from rendering resolution than from pushing bitrate beyond what the network can sustain.
- Audio stays on the monitor: Select the Virtual Desktop playback device in Windows or the simulator’s audio settings. Restore the normal device after leaving VR if Windows does not switch it back.
- The yoke or joystick disappears in VR: VR does not change USB control detection. Keep the hardware connected to the PC and verify the simulator’s active control profile rather than trying to pair it with the Quest.