Set up Oculus Rift or Rift S for PC flight simulation with the right ports, Meta software, OpenXR settings, control bindings and practical fixes.
For general PC flight simulation, install the Meta Quest Link PC software, connect a Rift CV1 by HDMI and USB or a Rift S by DisplayPort and USB 3, complete headset setup, make the Meta/Oculus runtime active when OpenXR is required, then enable VR inside the simulator. Bind physical flight controls separately.
What is different between Rift CV1 and Rift S setup?
The Rift CV1 and Rift S use the same family of PC software, but their video connections and tracking systems are different.
| Headset | PC connections | Tracking | Main setup issue |
|---|---|---|---|
| Oculus Rift CV1 | HDMI, headset USB and separate sensor USB connections | External Constellation sensors | HDMI must connect to the dedicated graphics card; sensors need clear sight of the headset |
| Oculus Rift S | DisplayPort and USB 3 | Inside-out cameras on the headset | Requires a suitable DisplayPort path from the dedicated graphics card and adequate room lighting |
Do not plug the headset's video cable into a motherboard socket when a separate graphics card is installed. On a laptop, the port must be wired to the dedicated GPU; a physically compatible port is not enough. Rift S does not work through an ordinary HDMI port, while USB-C-to-DisplayPort only works when that USB-C port carries DisplayPort output from the correct GPU.
Our headset-to-PC connection notes explain these port differences in more detail.
Oculus Rift and Rift S setup steps
Use this order so that hardware, runtime and simulator faults remain easy to separate.
- Confirm simulator support. Check that the installed simulator version has native VR or supports an appropriate VR runtime. Microsoft Flight Simulator, modern X-Plane releases and DCS have built-in VR paths; FSX does not.
- Install the Meta PC software. This may be labelled Meta Quest Link or the Oculus PC app, depending on the installed release. Complete its sign-in and device setup, then restart the PC before diagnosing cable warnings.
- Connect directly to the PC. Use graphics-card video ports and, initially, direct motherboard USB ports rather than an unpowered hub or long extension. For CV1, connect the external sensors and position at least one where it can see the headset throughout the seated cockpit area.
- Complete headset configuration. Follow the software's display, tracking and audio checks. With Rift S, use a well-lit room without direct sunlight or large reflective surfaces. Choose a seated or stationary boundary if the software offers one, leaving enough physical clearance around the yoke, throttle and desk.
- Select the required runtime. Make Meta/Oculus the active OpenXR runtime for an OpenXR simulator. If the simulator offers a native Oculus mode, select that instead of adding an unnecessary compatibility layer.
- Prepare physical controls. A Rift does not replace a yoke, joystick, throttle or pedals. Calibrate and bind the flight controls before using VR, including brakes, trim, landing gear, view reset and the simulator's VR toggle.
- Launch and centre the view. Open the Meta software, confirm that the headset is recognised, start the simulator and activate its VR mode. Sit in the normal flying position before using Reset VR View or Re-centre View; leaning forward while resetting places the virtual seat incorrectly.
Touch controllers are optional in many flight simulators. A mouse plus physical flight controls is often easier for detailed cockpit operation, although simulator support varies.
Which PC flight simulators support Oculus Rift?
Rift CV1 and Rift S work with simulators that provide Oculus, OpenXR or another compatible PC VR mode.
| Simulator | Typical VR route | Setup note |
|---|---|---|
| Microsoft Flight Simulator 2020 and 2024 | OpenXR | Set Meta/Oculus as the active OpenXR runtime and bind Toggle VR |
| X-Plane 11 and 12 | Built-in VR | Enable VR hardware in the simulator; runtime behaviour can differ between releases |
| DCS | Native VR or OpenXR, depending on configuration | Enable its VR option and avoid running redundant compatibility layers |
| Prepar3D | Version-dependent VR support | Use the VR mode supported by the exact Prepar3D version installed |
| FSX | No native VR | Requires specialised third-party software, so Rift setup alone is insufficient |
For either Microsoft Flight Simulator release, follow our full MSFS OpenXR and control-binding setup after the Meta software detects the headset.
Which VR runtime should I use with Rift?
Use Meta/Oculus as the active OpenXR runtime for OpenXR simulators, or the simulator's native Oculus mode when one is explicitly available.
- OpenXR simulator: Select Meta/Oculus as the system's active OpenXR runtime in the Meta PC software. Only one OpenXR runtime can be active at a time.
- Native Oculus option: Choose it directly where the simulator provides one; this normally avoids an extra translation layer.
- OpenVR-only simulator: Use the compatible runtime path required by that simulator, but do not run multiple VR layers merely because they are installed.
The headset's home environment working does not prove that the simulator is using the right runtime. Runtime selection, in-simulator VR activation and headset detection are separate stages.
Why does Rift work on the desktop but not in the simulator?
When the headset environment works but the flight simulator remains flat or black, the usual cause is the wrong runtime, a missing VR binding or unsupported simulator mode rather than the headset cable.
- Simulator stays on the monitor: Confirm that the simulator supports VR, select its correct VR mode and bind or use Toggle VR. Recheck the active OpenXR runtime after installing other VR software.
- Black headset display: Reseat both video and USB connections, restart the Meta software and remove passive extensions or adapters. For Microsoft Flight Simulator, use our MSFS black-screen recovery checks for runtime, driver and launch-order faults.
- Rift S repeatedly disconnects: Try another direct USB 3 port, disconnect non-essential high-bandwidth USB devices and check Windows power management if the drop-outs continue.
- CV1 tracking jumps: Restore sensor line of sight and distribute sensors across suitable USB ports. One well-placed sensor can cover basic seated head tracking; Touch controllers and wider movement benefit from additional coverage.
- Rift S tracking drifts: Clean the tracking cameras, provide steady room lighting and reduce reflections or featureless surfaces around the cockpit.
- Heavy stutter: Change supersampling or render scale in one place only. Reduce render scale, clouds, shadows and traffic before lowering cockpit readability. A fall to 45 fps on CV1 or 40 fps on Rift S can be the runtime's half-refresh ASW behaviour rather than a hardware fault.
- Wrong cockpit scale or eye position: Set the available IPD adjustment for the headset, then reset the VR view from the normal seated position. Rift S uses software IPD adjustment rather than physically moving its lenses.
- No headset audio: Select the Rift audio device in Windows and inside the simulator; some simulators retain the output device chosen before VR was activated.
Legacy headset limitations
Rift CV1 and Rift S remain usable for PC flight simulation when their cables, sensors and software are working, but they are legacy headsets with model-specific replacement parts and lower cockpit clarity than newer hardware.
Once the installation is stable, avoid unnecessary USB-driver, runtime and adapter changes. A direct GPU connection, one active VR runtime and a bound Reset VR View command prevent most repeat failures.