Skip to content
General 15 min read 426 views

How do I set up head and eye tracking for flight simulation?

Ian Stephens
In short

Set up head and eye tracking for flight simulation, with MSFS 2020/2024 steps, laptop webcam setup, calibration, curves and fault fixes.

To set up head and eye tracking for flight simulation, install the device driver or tracking app, position the sensor, calibrate from your normal seat, select an output the simulator supports, and start tracking before the simulator. Confirm movement in both previews, bind centre and pause, then tune curves, smoothing and limits.

This answer covers general PC flight simulation. You do not need both technologies: head tracking is the more useful foundation for deliberate cockpit movement, while eye tracking adds gaze response or interaction only where the simulator and device integration support it. Console users must use hardware explicitly supported by the simulator and platform.

Which type of flight simulator tracker should you use?

Choose infrared tracking for the most consistent six-axis movement, a dedicated eye tracker for a headset-free installation, or webcam tracking when cost matters more than precision and low latency.

Tracking typeChoose it whenMain limitation
Infrared camera with reflector or active clipYou want precise, dependable six-degree-of-freedom head trackingRequires something worn on the head; sunlight and poor clip alignment can interfere
Dedicated eye trackerYou want head pose and supported gaze features without a cap or clipScreen size, seating distance, glasses and simulator support affect results
Webcam with pose or marker softwareYou want an inexpensive starting point using equipment you already ownLighting, frame rate, exposure, CPU load and camera placement matter more

Six-degree-of-freedom tracking covers yaw, pitch, roll, left/right, up/down and forward/back. It lets you look around, lean towards instruments and move around a windscreen pillar rather than merely rotating a fixed camera.

For reflector or active-clip hardware, our detailed TrackIR mounting and profile instructions cover clip selection, sensor visibility and axis tuning in greater depth.

What is native tracking, and when is third-party software required?

Native support means the simulator understands a particular tracking input; it does not mean every camera or eye tracker will work without its driver, calibration software or an output translator.

SourceWhat the simulator receivesWhat is required
TrackIR hardwareTrackIR head-pose dataThe TrackIR application must detect the clip and run before the simulator
Supported Tobii deviceHead pose and, where implemented, separate gaze dataTobii services, device calibration and a simulator-supported integration
OpenTrack with webcam or another sensorUsually emulated TrackIR or FreeTrack head-pose dataA compatible camera input, OpenTrack configuration and the correct output protocol
Generic webcam appNothing unless it produces a protocol the simulator understandsThird-party pose estimation and output software
Console camera or USB trackerOnly data explicitly supported by that simulator and consolePlatform support; Windows tracking applications cannot be installed on a console

A TrackIR-compatible output carries head-pose axes; it does not automatically carry true eye-gaze coordinates. A dedicated eye tracker may therefore provide head tracking through one route while gaze control depends on a separate native or vendor-supported integration. A mistake we see constantly is assuming that any detected webcam or eye tracker automatically becomes a cockpit controller.

How do you set up head and eye tracking?

The reliable order is hardware, source preview, calibration, output, simulator detection and only then sensitivity tuning.

  1. Position the sensor. Mount it squarely towards your normal seating position. An infrared camera must see every reflector or LED throughout the intended movement range; an eye tracker must remain within its supported screen and seating geometry.
  2. Control the lighting. Remove direct sunlight, bright reflections and exposed infrared sources from the sensor’s view. Webcam tracking needs even frontal light rather than a bright window behind your head.
  3. Install the required driver and one tracking chain. The device service may run underneath the tracking app, but do not have two applications capturing the same camera or sending competing view outputs.
  4. Verify the source preview. Turn, lean and move vertically before opening the simulator. If the preview freezes or loses your face or clip, fix that first.
  5. Select the simulator-compatible output. Use native integration when it provides the features you need. Otherwise choose TrackIR-compatible or FreeTrack-compatible output as required by the simulator.
  6. Start tracking before the simulator. Some simulators detect an external tracker only during launch. If detection fails, close the simulator rather than repeatedly changing curves.
  7. Bind centre and pause. Put both commands on accessible yoke, joystick or throttle buttons. Centre restores the natural forward view; pause lets you use menus or change posture without moving the cockpit camera.
  8. Test inside a cockpit. Check yaw, pitch and translation while reading instruments, viewing the overhead panel and looking towards each wing. Add gaze influence only after head movement works correctly.

Microsoft Flight Simulator 2020 and 2024 setup

On PC, Microsoft Flight Simulator 2020 and Microsoft Flight Simulator 2024 support TrackIR input, supported Tobii integrations and OpenTrack when it sends a suitable TrackIR-compatible output.

  1. Start the tracking source. For TrackIR, select the correct reflector or active-clip mode and activate the intended simulator profile. For Tobii, start its required services and complete device calibration. For OpenTrack, select the camera or sensor input and start processing.
  2. Confirm the tracker preview. Make sure yaw, pitch and translation move in the correct directions. Tobii users should validate both head pose and gaze; OpenTrack users should check the raw camera view as well as the pink octopus or pose preview.
  3. Confirm the output. TrackIR software supplies its own TrackIR data. In OpenTrack, choose its TrackIR-compatible output; the commonly used option is freetrack 2.0 Enhanced. A supported Tobii device should use the simulator’s intended integration rather than converting gaze into head axes unnecessarily.
  4. Launch Microsoft Flight Simulator after the output is active. Load far enough to reach a cockpit before deciding detection has failed; menu screens do not always show meaningful camera movement.
  5. Check the correct version’s settings. Use the table below rather than following an old screenshot from the other release.
  6. Bind centre and pause. Prefer the tracker application’s centre and pause commands, or the corresponding simulator tracking command where the integration requires it. Do not assign the same button to a conflicting snap view or unrelated cockpit-camera reset.
  7. Test detection before tuning. Turn your head, lean towards the panel and move sideways. TrackIR-compatible head pose does not normally need six joystick-axis assignments; creating them can introduce duplicate inputs.
SimulatorSettings to check
Microsoft Flight Simulator 2020Open General Options, then the camera settings, and confirm TrackIR is enabled for TrackIR or OpenTrack input. For supported Tobii hardware, confirm its head- and eye-tracking camera options are present and enabled. Use Controls Options search to find any tracking toggle or reset command you intend to bind.
Microsoft Flight Simulator 2024Open the camera settings and confirm head tracking, TrackIR or supported eye tracking has not been disabled. In Controls, search for tracking, TrackIR, centre and reset rather than copying the reorganised MSFS 2020 menu path. Check that you are editing the active control profile.

If a tracker worked until the simulator or device software was restarted, close the simulator, start the tracker and its output again, verify the preview, and relaunch the simulator. Our expanded MSFS detection and profile walkthrough covers device-specific centring and launch-order problems.

These desktop instructions do not apply directly to the Xbox versions of MSFS 2020 or MSFS 2024, or to MSFS 2024 on PlayStation 5 and PS5 Pro. Those consoles cannot run Windows TrackIR, Tobii or OpenTrack applications, and connecting a generic USB webcam does not create tracking support.

Laptop with webcam head tracking

A laptop with webcam head tracking can work well enough for general cockpit viewing if the camera holds a clear, evenly lit image and the display remains in the same physical position after calibration.

  • Camera placement: Place the lens centrally above or just below the screen, close to eye level. A sharply off-centre view makes pose estimation less consistent when turning towards one side.
  • Practical webcam specification: A stable 720p image at 30 frames per second is a sensible practical starting point, not a universal compatibility guarantee. A clean 60 fps feed can reduce latency, but stable exposure and an unblurred face matter more than 4K resolution.
  • Built-in camera: It is convenient and uses no extra cable, but its angle changes whenever the laptop lid moves. Narrow framing, limited exposure control and low-light blur are common restrictions.
  • USB camera: It can be positioned independently and may offer better exposure or frame-rate control. Connect it directly where possible; an overloaded hub, loose cable or aggressive USB power saving can cause freezes.
  • Lighting: Use soft light from in front or slightly to the side. Avoid a bright window behind you, rapidly changing screen illumination and reflections from glasses.
  • Laptop movement: Do not adjust the screen angle after centring or calibrating. On a flexible desk, typing or operating a yoke can move the display and make the virtual viewpoint drift.
  • CPU load: Face-pose estimation consumes processor time. If tracking becomes delayed, lower the camera resolution or processing frame rate, disable unnecessary filters and close other camera applications before reducing simulator graphics settings.
  • Privacy conflicts: Open the physical privacy shutter, grant camera permission to the tracking app and close conferencing software, browsers, camera utilities and presence-detection tools that may already own the webcam.

Concise OpenTrack-compatible webcam setup

An OpenTrack-compatible webcam setup needs a working camera input, a pose-estimation method and a TrackIR-compatible output.

  1. Prepare the camera. Fix the screen angle, provide even frontal light and close every other application using the webcam.
  2. Select the input. In OpenTrack, choose an installed and supported face-pose, marker or point-tracking input appropriate to your setup.
  3. Check the input preview. Confirm that your face or marker remains detected through the full head-turn range. Correct camera exposure and placement before touching response curves.
  4. Set the neutral position. Sit naturally, look at the screen centre and bind an OpenTrack centre command to an accessible controller button.
  5. Select the output. Choose the TrackIR-compatible output expected by the simulator, commonly freetrack 2.0 Enhanced, then press Start.
  6. Launch and test. Open the simulator after OpenTrack is producing output. Test yaw and pitch first, then add translation and roll one axis at a time.

For a complete no-cost MSFS example, use our webcam-to-OpenTrack setup for MSFS 2024.

How to calibrate head and eye tracking (Come calibrare)

Calibration should be performed from the exact seating position, posture, screen angle and lighting used while flying.

  1. Set your normal seat. Place the chair, controls and monitor first. Sit naturally rather than stretching upright or leaning towards the screen for calibration.
  2. Align the sensor. Centre the camera or eye tracker on your usable viewing area and point it towards your eyes or tracking clip. Confirm that the sensor remains unobstructed by a yoke, microphone or monitor edge.
  3. Check head-tracker visibility. In the preview, turn and lean through the movement range you expect to use. Reposition the camera or clip if a reflector, LED, marker or facial feature disappears. Curves cannot repair a tracking dropout.
  4. Set and bind neutral centre. Face the middle of the screen with relaxed shoulders, then issue the centre command. Bind that command before flying so a small posture change can be corrected without opening settings.
  5. Run eye calibration for the actual user. Wear the same glasses or contact lenses used for flying and follow every target without moving your head unnecessarily. Eye calibration is user-specific; another person should create a separate calibration where the software allows it.
  6. Validate eye accuracy. Use the device’s validation display or gaze indicator to check the centre, corners and lower instrument-panel area. A completed calibration is not necessarily an accurate one. Reposition the tracker and repeat it if the indicator consistently lands to one side.
  7. Test the full movement range. Check left and right windows, the overhead panel, lower controls and a forward lean. Set movement limits before increasing sensitivity so the viewpoint cannot pass through the seat, canopy or instrument panel.
  8. Recalibrate only when needed. Re-centre head tracking after an ordinary posture change. Repeat full eye calibration after changing glasses, monitor position, laptop-lid angle, seating distance, lighting or habitual posture, or when gaze validation starts missing consistently.

What is a curve, and how should tracking curves be adjusted?

A curve maps physical head movement to virtual camera movement: a shallow centre gives fine instrument control, while steeper outer sections let a modest head turn reach side, rear or overhead views.

  • Dead zone: Use only enough to stop unwanted movement while looking straight ahead. A large dead zone causes a visible jump when tracking finally starts.
  • Smoothing: Add the minimum needed to remove tremor or camera noise. Too much creates delayed, floating movement.
  • Yaw and pitch: Keep the centre controlled, then increase the outer response until side and overhead views are reachable without losing sight of the monitor.
  • Translation: Limit left/right, vertical and forward movement before the viewpoint clips through cockpit geometry.
  • Roll: Reduce or disable it if normal head tilts make a desktop cockpit feel unstable.
  • Forward movement: Treat it as physical leaning, not automatic zoom. Do not map the same motion to both cockpit translation and field-of-view zoom.
  • Gaze influence: Keep it lower than head influence and use a calmer central area. Your eyes scan instruments constantly, so aggressive gaze response makes the view wander.

Airliners and instrument flying usually benefit from a calmer centre and slightly more smoothing. Helicopters and combat aircraft often need a faster outer response. Save separate profiles when possible rather than forcing one curve to suit every cockpit.

Can you use eye tracking without head tracking?

Eye tracking can work alone only where the simulator or supported integration accepts gaze input, but gaze-only camera control is rarely comfortable for normal cockpit use.

Your eyes move continually between labels, instruments and controls. If every glance rotates the camera, the view feels restless. Use head pose as the primary view control, keep gaze influence modest and reserve direct gaze interaction for simulators that explicitly support it.

A generic TrackIR-compatible output does not turn an unsupported eye tracker into native gaze control. It may carry head pose estimated by the eye-tracker software, but the simulator will not receive true eye position unless the integration supplies it separately.

How does setup differ between flight simulators?

Each simulator differs mainly in its accepted protocol, camera enable switch, binding names and treatment of gaze; the hardware checks and calibration order remain the same.

DCS World commonly consumes six-axis TrackIR-compatible head pose, while gaze behaviour depends on the supported eye-tracking route rather than ordinary TrackIR axes. X-Plane 12 may use native device support, an external output or a plug-in depending on the tracker; our X-Plane 12 output and binding steps explain that workflow.

Older simulators may require a plug-in or FreeTrack-compatible interface. Confirm the simulator’s accepted input before buying hardware: a good sensor cannot compensate for an unsupported protocol.

It’s still not working: priority diagnostic flow

Work through these checks in order; changing curves, smoothing or graphics settings cannot fix a tracker that is not producing valid data or has not been detected.

  1. Verify the tracker preview. If raw camera or pose movement is absent, frozen or reversed, stay outside the simulator. Check power, privacy shutter, camera permission, clip visibility, calibration and lighting.
  2. Allow one capture owner and one output sender. The device driver may remain active, but close conferencing apps, camera previews and competing trackers. If one application intentionally feeds OpenTrack, ensure only the final application sends view data to the simulator.
  3. Verify the output protocol. Confirm that output is running and matches what the simulator accepts: native device integration, TrackIR-compatible output, FreeTrack-compatible output or a required plug-in. A moving source preview proves only that input works.
  4. Restart in the correct order. Exit the simulator, stop the tracking output, reconnect the device if necessary, start its driver or service, open the tracking app, verify the preview, start output and only then relaunch the simulator.
  5. Check simulator detection and bindings. Enable head tracking in the camera settings, select the active control profile and remove duplicate view axes, snap views or a latched mouse-look command. Confirm centre and pause are not bound to conflicting actions.
  6. Isolate the remaining variable. Load a default tracker profile, disable gaze, test yaw and pitch only, simplify the lighting, try a direct USB port and reduce webcam processing resolution. Add translations, custom curves and aircraft-specific profiles back one at a time.
SymptomMost likely fix
The tracker preview moves, but the simulator does notCorrect the output protocol, start output before the simulator and check the simulator’s camera-tracking switch or required plug-in.
The view jumps, snaps back or fights the trackerRemove duplicate camera axes, close the second output application and release any latched free-look or snap-view command.
Movement is reversedInvert the affected axis in either the tracker or simulator, but not both.
Tracking freezes when looking sidewaysThe sensor is losing the reflector, LED, marker or facial features. Reposition it and retest the complete range in the preview.
The centre view jittersBlock direct sunlight and reflections, improve webcam exposure, reduce centre sensitivity and add a small amount of smoothing or dead zone.
Webcam tracking feels delayedReduce excessive smoothing, camera resolution or processing load; close filters and other camera applications.
Eye tracking misses instrumentsReturn to the calibrated seat, clean and realign the sensor, validate the gaze result and recalibrate while wearing the usual glasses or contact lenses.
The neutral view is offsetSit naturally, face the screen centre and use the bound centre command. Repeat full calibration only if centring does not correct the offset.
AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members