Prepar3D supports Meta Quest 3 VR through a Windows PC. Learn how to connect it, enable VR and fix black screens, stutter or headset detection.
Yes. Prepar3D can display VR on a Meta Quest 3 when the headset is connected to a capable Windows PC through Quest Link or Air Link and recognised by a VR runtime supported by that Prepar3D version. It does not run natively on the Quest 3 as a standalone headset.
The distinction matters: Prepar3D renders the flight on the PC and streams the image to the headset. Our guide to VR headset compatibility with Prepar3D explains the broader headset and runtime limitations.
Does every Prepar3D version work with Quest 3?
Use a Prepar3D release with built-in VR support; Prepar3D v3.4 introduced native support for Oculus Rift and HTC Vive-era PC runtimes. The early implementation is documented in our summary of the Prepar3D v3.4 VR additions. Builds older than v3.4 lack that built-in VR route.
Quest 3 was released long after those original headset lists were written. It works by presenting itself to the PC as a compatible VR headset through Meta's Quest Link software, rather than through a Quest-specific Prepar3D mode.
The exact interface differs between Prepar3D branches. Some use the Meta/Oculus PC route, while others also expose different PC VR interfaces. Changing the active OpenXR runtime is not a universal fix because Prepar3D versions do not all handle Oculus, OpenVR and OpenXR in the same way. Our Prepar3D v5 VR and performance notes provide useful context for that branch.
How do I connect Meta Quest 3 to Prepar3D?
Connect and activate the Quest 3 as a PC VR headset before enabling Prepar3D's VR mode. If Quest Link itself is unfamiliar, follow our Quest 3 PC flight-simulator connection checklist first.
- Check the Prepar3D release: confirm that your installed version includes built-in VR and that the PC meets the headset software and graphics requirements.
- Install the Meta PC software: connect the headset and verify that the software reports it as available. A charging-only USB cable will not work for wired Link.
- Choose the connection: use Quest Link with a suitable USB data cable, or Air Link over a fast local wireless network.
- Enter PC VR mode: put on the headset and start the Link environment. Merely leaving the headset in its standalone Quest interface is not enough.
- Start Prepar3D normally: load a simple flight on the monitor, then use Prepar3D's Enable Virtual Reality command. Its exact menu location varies between major versions.
- Centre the cockpit view: use the simulator or runtime's recenter command and assign it to an accessible button. Set up the seated position before adjusting the cockpit camera.
Touch-controller and hand-tracking behaviour is not consistent across Prepar3D versions or complex add-on aircraft. A physical yoke or joystick, throttle, pedals and mouse remain the dependable control arrangement.
Should I use Quest Link or Air Link?
Wired Quest Link is the better first test because it removes wireless-network quality from the troubleshooting chain; Air Link is preferable once the basic VR setup works and freedom of movement matters more.
| Connection | Choose it when | Main drawback |
|---|---|---|
| Quest Link cable | You want consistent latency and the simplest diagnosis | The cable restricts movement and requires a reliable data-capable USB connection |
| Air Link | The PC is connected to the router by Ethernet and the headset has a strong, uncongested wireless signal | Network interference can cause stutter, compression artefacts and disconnects |
A third-party wireless layer can add another runtime or translation step. Do not begin there unless you know that your Prepar3D version supports the interface it provides.
Why does Quest 3 VR fail or stutter in Prepar3D?
Most Quest 3 failures in Prepar3D come from the wrong runtime path, starting the simulator before Link is active, add-on conflicts or settings that leave too little performance headroom.
- No headset detected: open the Meta PC software, wake the headset, enter Link mode and only then launch Prepar3D. Confirm that the Meta software sees the headset before changing anything inside the simulator.
- Black headset while the monitor works: test Prepar3D in windowed mode, close unnecessary overlays and avoid launching multiple VR runtimes together. On a laptop, ensure Prepar3D and the VR compositor use the discrete graphics processor.
- Crash when enabling VR: load a default aircraft at a simple airport and temporarily remove camera, weather or display-injection add-ons. This separates a core VR problem from an add-on incompatibility.
- Heavy stutter: begin with the headset's lower refresh-rate option and a conservative render resolution. Reduce shadows, reflections, traffic and dense scenery before increasing headset resolution.
- Blurred instruments: stabilise frame delivery first, then raise render resolution gradually. Stacking high Meta resolution, simulator supersampling and aggressive anti-aliasing can exhaust GPU headroom without producing a proportionate improvement.
- Viewpoint is offset: place the headset in the normal seated position and recenter after the aircraft has loaded. Recentring in a menu or loading screen can establish the wrong cockpit origin.
Prepar3D can also be limited by the CPU, particularly with complex aircraft, traffic and detailed airports, so a lightly loaded GPU does not guarantee smooth VR. If wired Link reaches a default flight and Prepar3D enters VR, Quest 3 compatibility is established; remaining problems are normally settings, add-ons or the wireless connection.