Use Virtual Desktop with Microsoft Flight Simulator VR: set VDXR, follow the correct launch order, tune Wi-Fi and fix detection or stutter.
To use Virtual Desktop with Microsoft Flight Simulator VR, run Virtual Desktop Streamer on the PC, connect from the headset, select VDXR as the OpenXR runtime, launch MSFS on the streamed desktop, load a flight, then press Ctrl+Tab to enter VR. Keep the PC wired to the router for reliable wireless streaming.
What do I need for Virtual Desktop and MSFS VR?
You need the Windows version of Microsoft Flight Simulator 2020 or 2024, a VR-capable PC, a Virtual Desktop-compatible standalone headset and the companion Streamer app running on the PC. Virtual Desktop is a PC streaming method; it cannot add VR to the Xbox or PlayStation versions of MSFS.
The headset and PC must be on the same local network. Connect the PC to the router or access point by Ethernet, then place the headset on a clear 5 GHz or 6 GHz Wi-Fi band near that access point. Internet speed is largely irrelevant because the video stream stays inside your home network.
Quest 3 owners can also use our Quest 3-specific Virtual Desktop connection checklist, including headset and wireless setup details.
Virtual Desktop launch order for MSFS VR
The most reliable method is to establish the Virtual Desktop and OpenXR session before asking Microsoft Flight Simulator to enter VR.
- Start Virtual Desktop Streamer: Open the Streamer app on the PC and complete any account or pairing step displayed by your version of Virtual Desktop.
- Select the OpenXR runtime: Set Virtual Desktop's OpenXR runtime option to VDXR. Do not start SteamVR when using VDXR.
- Connect the headset: Open Virtual Desktop inside the headset, connect to the PC and confirm that the Windows desktop appears correctly.
- Launch Microsoft Flight Simulator: Start MSFS normally from the streamed Windows desktop. Loading into the cockpit before enabling VR usually gives the cleanest launch.
- Enter VR: Press
Ctrl+Tab, the default Toggle VR command. If you use a customised control profile, verify that Toggle VR still has a binding. - Recentre and check audio: Use MSFS's Reset VR Position command and select the Virtual Desktop audio device if sound remains on the monitor speakers. Our guide to MSFS VR controls, recentring and headset audio covers those simulator-side steps.
Your yoke, joystick, throttle, pedals, keyboard and mouse remain connected to the PC. Virtual Desktop only carries the headset tracking, picture and audio; it does not replace the flight controls.
Should I use VDXR or SteamVR for Microsoft Flight Simulator?
Use VDXR first because Microsoft Flight Simulator is an OpenXR application and VDXR avoids adding SteamVR to the rendering chain.
| Runtime | Choose it when | Main consideration |
|---|---|---|
| VDXR | For the normal Virtual Desktop and MSFS setup | Usually the simplest route with the least runtime overhead |
| SteamVR OpenXR | When a required VR utility depends on SteamVR, or VDXR repeatedly fails | Adds another layer and must be selected as the active OpenXR runtime |
Use one path at a time. A common mistake is selecting VDXR but opening SteamVR or another PC-headset connection first, leaving MSFS attached to the wrong OpenXR runtime. Fully close MSFS before changing runtimes; switching while the simulator is open normally will not repair the session.
Why does MSFS not detect the Virtual Desktop headset?
If Ctrl+Tab does nothing, Microsoft Flight Simulator has usually started without access to the active OpenXR session.
- Close MSFS, connect the headset through Virtual Desktop, then relaunch the simulator.
- Confirm that VDXR is selected rather than leaving the runtime on an unexpected automatic or SteamVR setting.
- Close competing VR connections such as SteamVR or another wireless-link session when using VDXR.
- Click inside the MSFS window before pressing
Ctrl+Tab, and check the Toggle VR binding in the active keyboard profile. - Restart both Virtual Desktop Streamer and the headset after changing the runtime.
- Confirm that you are running MSFS locally on Windows rather than streaming a console or cloud version.
If detection still fails, work through the OpenXR and launch-order checks for an undetected MSFS headset. Entering VR successfully but seeing a black image is a different fault; return Virtual Desktop to default streaming options, disable conflicting VR overlays or injectors and restart the simulator before changing several graphics settings at once.
How do I fix stutter or a blurry cockpit over Virtual Desktop?
Use Virtual Desktop's performance overlay to determine whether the delay comes from MSFS rendering, video encoding, the wireless network or headset decoding.
- Network latency spikes: Move closer to the access point, avoid guest networks and wireless mesh backhaul, reduce streaming bitrate, and keep the PC on Ethernet. Guest-network isolation can also prevent the headset finding the PC.
- Game or rendering latency: Lower the MSFS VR render scale, terrain and object level of detail, clouds or glass-cockpit refresh settings. The simulator's VR graphics profile is separate from its normal monitor profile.
- Encoding or decoding delay: Return the codec to Automatic, lower the Virtual Desktop quality preset or bitrate, and retest. The highest bitrate is not automatically the clearest setting if the network cannot sustain it.
- Uneven frame pacing: Start with Synchronous Spacewarp set to Automatic. On headsets offering 72 Hz, that is a practical initial refresh-rate target for MSFS; raise it only when the PC has consistent headroom.
Compression artefacts that change as you turn your head point to the wireless stream. Permanently soft gauges and text more often indicate low MSFS render resolution or an aggressive upscaler. Raising bitrate will not repair a cockpit rendered at insufficient resolution; our detailed MSFS 2020 VR tuning guidance explains how to balance render scale, level of detail, clouds and reprojection once the connection itself is stable.