How do I set up Virtual Desktop VR for Quest flight sims?

To set up Virtual Desktop VR for a Meta Quest flight sim, install the Quest headset app and Virtual Desktop Streamer on the Windows PC, wire the PC to the router, connect the headset over fast local Wi-Fi, select VDXR or SteamVR as required, then launch the simulator and enter its VR mode.

This setup covers PC flight simulators generally rather than one specific title. The gaming PC still renders the simulator; Virtual Desktop encodes that image and sends it to the Quest as a wireless PC-VR display.

Is there a Virtual Desktop VR version, and what should I download?

Virtual Desktop on Quest is already the VR-capable headset app; there is no separate “VR version” or flight-sim plug-in to download.

• On the Quest: Install Virtual Desktop through the headset’s official app library.
• On the Windows PC: Download and install the official Virtual Desktop Streamer companion supplied by its developer.
• In the simulator: Use the simulator’s own native VR mode. Virtual Desktop cannot add stereoscopic VR or cockpit head tracking to a title that lacks PC-VR support.

A similarly named desktop application, an unofficial APK or Streamer by itself is not enough. Both the Quest app and the Windows Streamer are required. A non-VR simulator can still appear on a large virtual flat screen, but that is not the same as sitting inside a scale VR cockpit.

Virtual Desktop streams PC software only. It does not connect a Quest to Xbox or PlayStation editions of a flight simulator. If the hardware or software requirements are unclear, see our breakdown of PC-VR and flight-simulator requirements.

What must be ready before setup?

A VR-capable Windows PC, compatible Quest headset and low-latency local network must all be ready before Virtual Desktop can provide a usable flight-sim experience.

• PC network connection: Connect the flight-sim PC directly to the router or access point by Ethernet. A PC using Wi-Fi adds another variable and often produces avoidable network spikes.
• Quest Wi-Fi: Use a 5 GHz or 6 GHz band supported by both the headset and access point. Stay close to the access point and avoid walls, distant mesh nodes and congested channels.
• Local network: Keep the Quest and PC on the same LAN. Guest networks, client isolation, VPNs and some wireless extenders can block discovery or add latency.
• Flight controls: Connect the yoke, joystick, throttle and pedals to the PC, not the headset. Quest controllers work only where the simulator supports VR-controller interaction.

Internet download speed is not the main performance measure once the session is authorised and connected: the VR stream travels across the local network. A dedicated access point can help in a busy household, but it is not mandatory if the existing router provides a clean, nearby connection.

How do you set up Virtual Desktop for a Quest flight sim?

Install both components, establish the wireless desktop connection and choose the intended VR runtime before opening the simulator.

1. Install the Quest app: Add Virtual Desktop to the headset and let the installation finish before opening Streamer on the PC.
2. Install Virtual Desktop Streamer: Run the official companion installer on the flight-sim PC. Enter the Meta account identity requested by Streamer, matching the identity shown by the headset account, and leave Streamer running.
3. Prepare the network: Wire the PC to the router, connect the Quest to its fastest suitable Wi-Fi band and disable any guest-network or client-isolation setting affecting either device.
4. Connect the controls: Attach the flight hardware to the PC and confirm that Windows and the simulator recognise it before putting on the headset.
5. Choose a safe baseline: Leave the codec on Automatic, select moderate streaming quality and bitrate, and begin with a conservative headset refresh rate. Maximum settings make initial faults harder to identify.
6. Select the VR runtime: Choose VDXR for a native OpenXR simulator or SteamVR when the title specifically requires SteamVR or OpenVR.
7. Connect from the headset: Open Virtual Desktop on the Quest and select the PC advertised by Streamer.
8. Launch the simulator: Use Virtual Desktop’s Games panel when it recognises the title. Otherwise, view the Windows desktop and start the simulator normally.
9. Enter and recenter VR: Activate the simulator’s VR command after it has loaded, then recenter the view so the virtual seat, controls and instrument panel align with your physical position.

Do not start a Quest Link or Air Link session at the same time. Virtual Desktop is already providing the PC-to-headset transport; running two connection systems can switch audio devices, select the wrong runtime or leave the simulator on a flat screen.

For cockpit controls, view alignment and runtime concepts that vary between titles, our simulator-independent VR setup explains the remaining flight-sim steps.

Which OpenXR runtime should Virtual Desktop use?

Use VDXR for a native OpenXR flight simulator unless the title or a required add-on specifically depends on SteamVR.

Set the runtime before launching the simulator. After changing it, close the simulator and any open VR runtime completely, then relaunch. Microsoft Flight Simulator users should follow the exact MSFS Virtual Desktop launch sequence for VDXR and the VR toggle; the default VR command is normally Ctrl+Tab unless it has been rebound.

Which codec should I use in Virtual Desktop?

The best Virtual Desktop codec is Automatic for initial setup; choose AV1, HEVC or H.264 manually only after the simulator is stable and according to the headset, graphics encoder and network.

Not every codec appears on every Quest and GPU combination. AV1 is not better merely because it is newer, and 10-bit colour does not make unreadable instruments sharp. Cockpit text depends heavily on render resolution, streaming quality and antialiasing before the image reaches the encoder.

Compare codecs at the same refresh rate, quality level and approximate bitrate. Keep the one that preserves instrument text and scenery without adding network, encoding or decoding spikes. If a manual codec produces black frames, heavy latency or connection failures, return to Automatic before changing anything else.

How should bitrate, resolution and refresh rate be tuned?

Tune rendering load before raising bitrate, because extra network bandwidth cannot repair a frame that the PC rendered at insufficient resolution or delivered late.

1. Stabilise the refresh rate: Start with a conservative headset rate. A higher rate makes the PC render and encode more frames while the Quest must receive and decode them faster.
2. Set streaming quality: Choose a level appropriate to the graphics hardware rather than selecting the maximum automatically. Reduce it if encoding delay rises or the GPU has no headroom.
3. Adjust the simulator: Lower render scale, clouds, shadows or other GPU-heavy settings when game latency is high. Traffic, glass-cockpit processing and dense scenery can be CPU-bound, so reducing bitrate will not fix them.
4. Increase bitrate gradually: Stop when the image no longer improves materially or network latency begins to spike. High bitrate is useful only while the wireless path remains stable.
5. Change one control at a time: Fly the same aircraft and location long enough to distinguish a persistent improvement from a momentary change in scenery load.

Virtual Desktop’s performance overlay separates Game, Encoding, Networking and Decoding delay. High Game latency points to the simulator or PC; Encoding points to GPU load; Networking points to Wi-Fi or excessive bitrate; Decoding calls for a lighter codec, bitrate, quality level or refresh rate.

What is SSW in Virtual Desktop, and should flight simmers use it?

Synchronous Spacewarp (SSW) is Virtual Desktop’s headset-side frame generation, used to make head movement appear smoother when the PC cannot render at the full headset refresh rate.

Flight simulators often benefit because busy airports, detailed cockpits and traffic can prevent a steady native frame rate. A consistent half-rate target with generated frames may feel better than an unstable rate that moves continuously above and below the target.

• Use Automatic first: Let Virtual Desktop invoke SSW when needed while establishing a baseline.
• Force it only for a reason: An always-on or equivalent mode can help when the simulator holds a steady half-rate but cannot approach the native refresh rate.
• Disable it for artefacts: Propeller discs, rotor blades, cockpit-frame edges, labels and scenery moving sideways across the view can wobble, double or smear.
• Do not use it to hide network faults: SSW can compensate for late game frames, not Wi-Fi packet loss or erratic decoding.

SSW is not the same setting as OpenXR or SteamVR motion reprojection. When troubleshooting, avoid forcing several frame-generation or reprojection systems simultaneously; test one at a time so the source of artefacts remains clear.

Why is Virtual Desktop VR not working with the flight simulator?

Most Virtual Desktop flight-sim failures come from PC discovery, an incorrect runtime, the wrong launch order or an overloaded wireless connection.

If the PC cannot use Ethernet, the headset must connect through a distant mesh node, or Networking latency remains erratic at a low bitrate, a wired Quest connection is usually the more dependable transport. Lowering cockpit graphics cannot repair an unstable wireless path.