Learn how to set up FlightGear VR with OpenXR, map controls, optimise performance, and fix black screens or missing headset output.
Yes. FlightGear supports virtual reality through OpenXR on builds compiled with VR support. Install and select the OpenXR runtime for your headset, connect the headset before launch, then start FlightGear with --enable-vr. Head tracking and stereoscopic cockpit views work, but motion-controller interaction and aircraft compatibility are less consistent.
What do you need for FlightGear VR?
You need a VR-capable FlightGear build, a working OpenXR runtime and a headset recognised by that runtime. VR support is part of FlightGear rather than a separate aircraft add-on, but not every operating-system package is necessarily compiled with OpenXR enabled.
Run the headset’s own environment before attempting FlightGear. If that cannot display correctly, FlightGear will not be able to initialise the headset either. Make sure the intended headset runtime is selected as the system’s active OpenXR runtime; competing or incorrectly selected runtimes are a common cause of a desktop image with nothing inside the headset.
VR renders separate views for both eyes and places substantially more load on the graphics card. You can check your PC against FlightGear’s base hardware requirements, but regard those as a starting point rather than a VR performance guarantee. If a demanding airport and aircraft already run poorly in 2D, they will not become smoother in VR.
How do you enable VR in FlightGear?
Enable FlightGear VR by passing the --enable-vr option to a build that includes OpenXR support.
- Confirm normal FlightGear operation. Start the simulator in 2D first, load a simple included aircraft and check that the cockpit, scenery and controls work.
- Prepare the headset. Connect it, start its runtime and confirm that head tracking is active before launching FlightGear.
- Select the correct OpenXR runtime. Systems with more than one headset environment can retain the wrong runtime as the active one. FlightGear uses whichever OpenXR runtime the operating system presents.
- Add the VR launch option. Enter
--enable-vrin the launcher’s field for additional simulator arguments, if that field is available. Alternatively, start the executable from a terminal or command prompt withfgfs --enable-vr. Iffgfsis not on the command path, invoke it from its installation directory. - Start with conservative graphics settings. Use a simple aircraft, ordinary weather, limited traffic and moderate scenery detail for the first test. This separates OpenXR setup faults from performance problems.
- Re-centre the seated view. Sit in your normal flying position and use the headset runtime’s re-centre function. Re-centre again after changing seats or moving the tracking origin.
- Configure physical flight controls. A joystick or yoke, throttle and rudder pedals remain the most dependable arrangement. Our FlightGear controller configuration guidance covers axis assignment, calibration and common mapping faults.
If FlightGear rejects --enable-vr, or its log reports that OpenXR is unavailable, the installed build probably lacks the required VR component. Changing aircraft or graphics settings will not correct a missing OpenXR-enabled build.
Which VR headsets work with FlightGear?
A headset can work when its software supplies a functional OpenXR runtime for the operating system and graphics driver in use. FlightGear therefore does not rely solely on a fixed headset model list: the runtime, platform and way the FlightGear package was built all matter.
OpenXR compatibility on the headset specification is necessary but not an absolute guarantee. Platform support can be constrained by missing headset drivers or runtimes, particularly on operating systems with limited native VR support.
Do FlightGear motion controllers work?
Head tracking is the dependable part of FlightGear VR; motion-controller bindings and direct cockpit interaction vary by build, controller profile and aircraft. Do not assume every switch, knob or yoke can be operated naturally with tracked hands.
For regular flying, we recommend physical flight controls supplemented by a mouse and keyboard. Keep essential commands such as view control, brakes, trim and pause within reach; the FlightGear keyboard command reference helps when planning those bindings.
FlightGear VR troubleshooting
Most FlightGear VR failures come from the OpenXR runtime, a non-VR build, excessive rendering load or an aircraft-specific cockpit effect.
| Symptom | Likely cause | What to do |
|---|---|---|
| The VR option is rejected | The installed FlightGear build does not expose VR support | Use a newer or OpenXR-enabled build for the operating system; graphics changes cannot add missing VR components. |
| FlightGear appears only on the monitor | OpenXR did not initialise, or the wrong runtime is active | Confirm the headset environment works, select its OpenXR runtime and relaunch FlightGear after the headset is ready. A monitor mirror is normal, but the headset should also receive an image. |
| Black display or OpenXR initialisation error | Inactive headset, runtime conflict, driver fault or interfering overlay | Restart the headset runtime, close unnecessary overlays and test with default FlightGear rendering settings. |
| The viewpoint starts outside the seat | The tracking origin was captured from the wrong position | Sit normally, face forward and re-centre through the headset runtime. |
| Only one aircraft has visual faults | Its cockpit, shader or display implementation is not behaving correctly in stereo | Test an included, simpler aircraft. If that works, treat the fault as aircraft-specific rather than rebuilding the whole VR setup. |
| Head movement works but flight controls do not | The VR controller is unbound or unsupported by that cockpit | Map a conventional joystick, yoke, throttle and rudder axes instead of relying on tracked controllers. |
| Judder, delayed head movement or unstable frame rate | The CPU or GPU cannot maintain the headset’s frame timing | Reduce settings in stages and retest from the same airport and cockpit. |
VR performance settings to reduce first
Lower headset render resolution and GPU-heavy effects first when the graphics card is saturated; reduce traffic and scene complexity when the main processor is the bottleneck.
- GPU-limited: reduce the OpenXR runtime’s render scale, anti-aliasing, shadows, cloud quality and visibility.
- CPU-limited: reduce AI traffic, complex aircraft systems, detailed scenery and activity around large airports.
- Aircraft-specific slowdown: compare the same location with a simpler included aircraft before changing every global setting.
- Intermittent stutter: allow scenery loading to settle, avoid unnecessary background applications and check that the simulator is not repeatedly loading new terrain during the test.
Change one setting group at a time. Otherwise, it becomes difficult to tell whether the limiting factor was OpenXR resolution, FlightGear’s rendering load or the selected aircraft.