How do I set up Meta Quest 2 for Microsoft Flight Simulator?
To set up Meta Quest 2 for Microsoft Flight Simulator VR on PC, install the Meta Quest Link app, connect the headset by a data-capable USB cable or Air Link, select Meta Quest Link as the active OpenXR runtime, start the simulator, then enter VR mode and reset the cockpit view.
Quest 2 acts as a PC VR headset; it does not run Microsoft Flight Simulator by itself. The connection process is broadly the same for Microsoft Flight Simulator 2020 and 2024 on PC, and it does not apply to the console editions.
What do you need for Quest 2 VR in Microsoft Flight Simulator?
You need a VR-capable Windows PC, a Quest 2, the Meta Quest Link PC app and either a USB data connection or suitable Wi-Fi.
- A capable PC: Running the simulator on a monitor does not guarantee acceptable VR performance because VR renders a high-resolution view for each eye. Our practical PC hardware and VR settings breakdown explains the CPU, GPU and memory considerations.
- A connection: Use a USB 3 data cable for Quest Link, or Air Link over a good 5 GHz wireless network. A charge-only USB cable will not work.
- Flight controls: A joystick, yoke or HOTAS is strongly preferable. Keep a mouse and keyboard within reach for menus and cockpit controls.
- Updated software: Update the Quest headset software, Meta Quest Link app and graphics driver before troubleshooting the connection.
How do you connect Quest 2 to Microsoft Flight Simulator?
Set up and verify the Meta PC VR connection before opening Microsoft Flight Simulator.
- Install Meta Quest Link: Install the Meta Quest Link app on the PC, sign in and add the Quest 2 if prompted.
- Connect the headset: For wired Link, attach a data-capable cable directly to a suitable PC USB port. For Air Link, place the PC and headset on the same local network, open Quest Link in the headset and pair it with the PC.
- Enter the PC VR session: Launch Quest Link from inside the headset. Confirm that you can see the Link environment or PC desktop rather than only the Quest standalone interface.
- Select the OpenXR runtime: In the Meta Quest Link PC app, open its general settings and find the OpenXR Runtime control. Set Meta Quest Link as the active runtime. If it already reports itself as active, leave it unchanged.
- Start Microsoft Flight Simulator: Launch the simulator normally on the monitor. Loading a simple flight in 2D before switching to VR makes initial troubleshooting easier.
- Enter VR mode: Use the command assigned to
Toggle VR Mode. The usual default isCtrl+Tab, but an imported control profile may have replaced it. - Centre the cockpit view: Sit in your normal flying position and use
Reset VR View. This is commonly assigned to the space bar; search for the command in the simulator's control settings if it does not respond.
Changing the OpenXR runtime while the simulator is open may not take effect until Microsoft Flight Simulator is restarted. The simulator's store edition does not determine which runtime you should use, so there is no need to start SteamVR merely because the simulator was purchased through Steam. Our PC VR and OpenXR setup checklist covers the underlying runtime sequence in more detail.
Cockpit controls and sound
Quest Touch controllers can operate some supported cockpit controls, but they are not a reliable replacement for physical flight controls in every aircraft. We recommend flying with a yoke, joystick or HOTAS and using the mouse for switches that are awkward to reach in VR; our control-binding walkthrough for Microsoft Flight Simulator explains how to build and save a suitable profile.
If sound remains on the monitor or speakers, choose the Quest or Oculus virtual audio device in Windows. You can use a different output deliberately, but automatic switching is easier to diagnose during the first setup.
Should you use Quest Link cable or Air Link?
Use a Quest Link cable for the most predictable first setup, and choose Air Link when freedom from the cable matters more than removing network-related variables.
| Connection | Choose it when | Main requirements | Likely drawback |
|---|---|---|---|
| Quest Link cable | You want consistent latency or need to diagnose a new setup | Data-capable USB cable and a reliable PC USB port | The cable restricts movement, and some ports cannot keep the headset charged indefinitely |
| Air Link | You want wireless VR and have a strong local network | PC connected to the router by Ethernet, Quest 2 on 5 GHz Wi-Fi and the router near the headset | Interference, congestion and weak signal can cause compression, stutter or disconnections |
For Air Link, avoid a guest network that isolates wireless devices from the PC. A faster internet package does not improve Air Link by itself; local communication between the headset, router and PC is what matters.
Why isn't Microsoft Flight Simulator detecting Quest 2?
Detection failures usually mean the headset is not in a PC VR session, Meta Quest Link is not the active OpenXR runtime, or the USB or wireless connection is unstable.
- The Meta app cannot see the headset: Confirm that the USB cable carries data, try a direct rear motherboard port rather than a hub, and test another port or cable. For Air Link, verify that both devices are on the same local network and pair them again.
- Meta Quest Link works but VR mode does nothing: Make Meta Quest Link the active OpenXR runtime, close unnecessary VR software, restart the simulator and click the simulator window before pressing
Ctrl+Tab. - The shortcut has no effect: Search the simulator's controls for
Toggle VR Modeand assign it manually. Check the keyboard profile actually selected for the flight. - The headset shows three dots or a black display: Restart the Link session and the PC app. With a cable, remove hubs and extension leads; with Air Link, test close to the router or temporarily use a cable to separate a network problem from a simulator problem.
- The cockpit position is wrong: Sit upright in the intended flying position, then invoke
Reset VR View. Recentring from a standing or leaned-forward position places the virtual seat incorrectly. - The image is blurred or stutters: Start with the headset at 72 Hz and automatic or default Link resolution. Raising headset resolution, simulator render scaling and refresh rate together is a common cause of poor frame pacing.
Performance settings after connecting Quest 2
A conservative baseline is more useful than maximum image quality during setup: use 72 Hz, leave the Link render resolution near its default and begin with moderate Microsoft Flight Simulator VR settings. Establish a stable flight before changing codec, bitrate or diagnostic-tool options.
Adjust one layer at a time: headset resolution, simulator VR render scaling or upscaling, terrain detail, clouds and traffic. Compare changes using the same aircraft, airport, weather and camera position. If Air Link looks blocky while wired Link is clear at similar simulator settings, investigate the wireless connection rather than increasing render scale.
Microsoft Flight Simulator 2024 can be particularly demanding in dense areas and complex aircraft. Once the connection itself works, use our MSFS 2024 VR performance-tuning procedure to balance render scale, reprojection, VRAM use and frame-time consistency.