FlightGear VR uses OpenXR. Learn which builds work, how to launch with --enable-vr, connect Quest 2, choose PC specs and fix black-screen faults.
Yes. FlightGear 2020.3 and later supports virtual reality through OpenXR when the build was compiled with VR/OpenXR enabled. Official Windows packages include that support; some Linux distribution and third-party packages do not and must be replaced or rebuilt. Connect the headset, activate its OpenXR runtime, then launch FlightGear with --enable-vr.
What FlightGear VR build do you need?
The OpenXR implementation in the FlightGear 2020.3 release line and later provides stereoscopic cockpit rendering and headset tracking. It does not use a separate VR aircraft add-on, and --enable-vr is the valid launch option; --vr is not an equivalent shortcut.
The official Windows packages include the required support. Linux packages vary because distribution maintainers choose their own build options. If a packaged build rejects the option or reports that OpenXR is unavailable, use a package explicitly built with OpenXR or compile FlightGear with the OpenXR dependencies present and enabled in the build configuration. Ordinary 2D operation does not prove that VR was included.
FlightGear uses the system’s active OpenXR runtime. A headset environment such as Meta Quest Link or a PC-VR platform can supply that runtime, but only one should be active. OpenXR is the VR interface here; it is not the same setting as FlightGear’s graphics renderer.
- A FlightGear 2020.3-or-later build compiled with VR/OpenXR support
- A PC headset or connected standalone headset whose PC software provides OpenXR
- Working headset tracking and graphics drivers before FlightGear starts
- A joystick, yoke or other conventional flight controls for dependable aircraft operation
How do you enable VR in FlightGear?
Prepare and test FlightGear in 2D, start the headset environment, and then launch the simulator with --enable-vr.
- Test FlightGear normally. Load a simple included aircraft at an uncomplicated airport and verify the cockpit, scenery and controls in 2D. Our first-time FlightGear setup guide covers installation, aircraft selection and the initial 2D test.
- Start the headset software. Connect or wake the headset and confirm that its own PC-VR environment displays correctly and tracks head movement.
- Select its OpenXR runtime. If more than one headset platform is installed, use the chosen platform’s settings to make it the active OpenXR runtime. Restart the headset software after changing this.
- Add the exact launch option. Enter
--enable-vrwithout quotation marks. Do not place it in an aircraft, scenery or add-on path field. - Use a light first test. Select a simple aircraft, clear weather, modest scenery detail and little or no AI traffic. This makes an OpenXR fault easier to distinguish from poor performance.
- Check the log and re-centre. Confirm that OpenXR created a headset session, then sit in the normal flying position and use the headset runtime’s re-centre command.
Where should the VR launch argument be added?
| Platform or launch method | Where to add --enable-vr |
|---|---|
| FlightGear 2020.3-or-later Qt Launcher | Open Settings, expand Additional Settings, and enter it in the additional command-line arguments field. If that field is absent in a repackaged launcher, use the operating system’s command line. |
| Windows Command Prompt | Open the FlightGear bin directory and run fgfs.exe --enable-vr. If the directory is already on the command path, it can be run from any location. |
| Windows shortcut | Open the shortcut’s Properties and append --enable-vr to the Target, after the closing quotation mark around the executable path. |
| Linux terminal | Run fgfs --enable-vr. A distribution package that reports an unknown option or no OpenXR support may need to be replaced or rebuilt. |
| macOS launcher | Use the launcher’s additional-arguments field. Actual operation still depends on having both a VR-enabled FlightGear build and a compatible OpenXR runtime for macOS. |
FlightGear VR with Meta Quest 2: does it work without a PC?
No. FlightGear cannot run as a standalone or no-PC Quest 2 application because there is no native Quest Android version. Quest 2 must be connected to a VR-capable Windows PC through a USB Quest Link connection or Meta Quest Air Link. The same principle applies to Quest 3 and Quest 3S.
- Install and test FlightGear on the PC. Confirm that the VR-enabled build works in ordinary 2D mode.
- Open the Meta Quest Link PC application. Connect Quest 2 with a suitable USB 3 cable, or configure Air Link with the PC connected to the router by Ethernet where possible.
- Make Meta Quest Link the OpenXR runtime. In the PC application, open Settings > General > OpenXR Runtime and use the control to set Meta Quest Link as active.
- Enter Quest Link mode. Put on the headset and verify that the PC-VR environment appears and tracks correctly. Do not launch FlightGear while the headset is still in its standalone home environment.
- Start FlightGear with VR enabled. Run it with
--enable-vr, load a simple cockpit and wait for scenery loading to settle. - Re-centre from the flying position. Sit facing forward at the controls, then use the Quest runtime’s re-centre function.
For Air Link, a weak or congested wireless connection can resemble poor simulator performance: the cockpit becomes blocky, delayed or intermittently black even when FlightGear’s frame rate is adequate. A wired Link test is the quickest way to separate network trouble from an OpenXR or rendering problem. Our broader PC flight-simulator VR setup guidance explains the connection and runtime checks in more detail.
What PC specs do you need for FlightGear VR?
FlightGear has no single official VR minimum because the required performance changes sharply with headset resolution, aircraft complexity, scenery and weather. The figures below are practical planning baselines for VR, not the simulator’s much lighter ordinary 2D requirements.
| Component | Minimum practical baseline | Sensible recommendation |
|---|---|---|
| CPU | A modern four-core desktop-class processor with good single-thread performance | A recent six- to eight-core processor with strong single-thread speed, particularly for complex aircraft and busy airports |
| GPU | A dedicated, headset-supported PC-VR graphics card with about 6 GB of VRAM; integrated graphics are not a realistic baseline | An upper-midrange or faster dedicated GPU with 8–12 GB of VRAM and enough headroom for both eye views |
| Memory | 16 GB RAM | 32 GB RAM for detailed scenery, complex aircraft and background headset software |
| Headset connection | The headset’s supported wired connection, or stable 5 GHz wireless for Quest streaming | Wired USB 3 for Quest testing, or Wi-Fi 6/6E near the headset with the PC connected to the router by Ethernet |
| Render resolution | Reduced or default OpenXR render scale with moderate FlightGear settings | Enough GPU headroom to run near the headset’s normal resolution without unstable frame timing |
Higher-resolution headsets render millions of additional pixels for every frame. A newer headset can therefore run worse than an older one on the same PC unless the OpenXR render scale is reduced. For an initial Quest test, use its lower supported refresh setting and default or reduced render resolution rather than immediately increasing image quality.
If the GPU is the limit, lower OpenXR render scale, anti-aliasing, shadows, clouds and visibility first. If the CPU is the limit, reduce AI traffic, complex aircraft systems and activity around large airports. Change one group at a time and repeat the same flight so the result is measurable.
Do Quest and other VR motion controllers work in FlightGear?
Head tracking is the dependable part of FlightGear VR; tracked-controller support and direct cockpit interaction vary by build, controller profile and aircraft. Do not plan on operating every switch, knob, throttle or yoke with Quest controllers.
A physical joystick or yoke, throttle and rudder controls remain the most reliable arrangement. Keep a mouse and keyboard within reach for cockpit controls that have no convenient hardware binding.
First-flight control checklist
- Assign the main axes in 2D. Map pitch, roll and throttle, plus yaw or rudder if the hardware provides it. Check that each axis moves in the correct direction and reaches its full range.
- Bind essential commands. Put wheel brakes, elevator trim, flaps, landing gear, pause and view reset on controls that can be found without removing the headset.
- Check the aircraft before entering VR. Confirm that the joystick or yoke moves the cockpit controls and that the throttle is not reversed. Our FlightGear control setup instructions cover axis assignment and calibration faults.
- Re-centre after sitting down. Face straight ahead from the normal flying position and use the headset runtime’s re-centre command. Re-centre again after moving the chair or tracking origin.
- Keep a 2D recovery route. If nothing works, close FlightGear, remove
--enable-vrand repeat the same aircraft and airport in 2D. A fault that remains in 2D is not caused by OpenXR.
Why is FlightGear only on the monitor or black inside the headset?
Desktop-only output usually means the VR argument was not applied, OpenXR failed to create a session, or the wrong runtime is active. A desktop mirror is normal during successful VR operation, but the headset must receive its own stereoscopic view as well.
How to confirm that OpenXR initialised
Open the launcher’s log viewer if supplied by the package, or inspect fgfs.log in FlightGear’s normal per-user data directory. Standard locations are shown below; a repackaged build can override them.
| Platform | Normal log location |
|---|---|
| Windows | %APPDATA%\flightgear.org\fgfs.log |
| Linux | $HOME/.fgfs/fgfs.log |
| macOS | $HOME/Library/Application Support/FlightGear/fgfs.log |
Search the log for OpenXR. Successful wording varies by FlightGear and runtime version, but the log should show that VR was enabled and that an OpenXR runtime, headset system and session or view configuration were created. Merely finding the OpenXR loader is not enough. Messages saying that OpenXR is unavailable, disabled or failed to initialise mean the headset session was never established.
| Symptom | Exact checks and fixes |
|---|---|
| No VR option appears in the launcher | A visible checkbox is not required. Add --enable-vr to the additional command-line arguments field or launch fgfs from a terminal. Check the launcher’s summary or log to confirm the argument was passed. |
--enable-vr is rejected | Confirm that the installation is FlightGear 2020.3 or later. If it is, the package was probably compiled without VR/OpenXR support; changing graphics settings or aircraft cannot add the missing component. |
| The headset is black | Wake the headset and verify its own PC-VR home or test scene first. Confirm the correct runtime is active, restart that runtime, close optional overlays and launch FlightGear only after the headset is connected. On a hybrid-graphics laptop, ensure both the headset software and FlightGear use the dedicated GPU. |
| FlightGear appears only on the desktop | Confirm that --enable-vr reached the simulator, then inspect the log for successful OpenXR session creation. If the log contains only ordinary graphics initialisation, VR did not start. |
| The wrong OpenXR runtime opens | Open the intended headset platform’s PC settings and make it the active OpenXR runtime. Close FlightGear and all competing VR environments, restart the selected runtime, then relaunch the simulator. |
| Quest 2 connects but shows no FlightGear image | Enter Quest Link or Air Link mode before starting FlightGear. Being connected to Wi-Fi or USB while still in the standalone Quest home is not sufficient. Test wired Link if Air Link is unreliable. |
| The view begins outside the pilot’s seat | Sit normally, face forward and re-centre through the headset runtime. If only one aircraft remains misaligned, test a simpler included aircraft before changing the room-scale tracking origin. |
| One aircraft has broken displays or stereo effects | Load a simple included aircraft at the same location. If that works, the problem is in that aircraft’s cockpit, shader or display implementation rather than the general OpenXR setup. |
| Head tracking works but the aircraft does not respond | Test the joystick or yoke in 2D and remap its axes. Do not assume tracked motion controllers automatically operate the cockpit. |
| Movement judders or feels delayed | Lower OpenXR render resolution first, then shadows, clouds and anti-aliasing. Reduce traffic and aircraft complexity if GPU changes make little difference. Allow scenery loading to finish before judging performance. |