Tobii Eye Tracker 5 not working in DCS World? Fix Unable to track game window, wrong DCS.exe paths, calibration, conflicts and VR issues.
If Tobii Eye Tracker 5 is not working in DCS World, verify that it tracks correctly in Tobii Experience, then make Game Hub rediscover the DCS.exe you actually launch. Start Game Hub before DCS, run both at the same privilege level, and close TrackIR, OpenTrack, VR and other competing trackers.
Tobii unable to track game window: how to fix it
The "Unable to track game window" message usually means Game Hub cannot attach its DCS profile to the running simulator process.
- Close DCS World completely. Exit the simulator and confirm in Windows Task Manager that its game process is no longer running. Closing only the DCS launcher is not enough.
- Find the executable DCS actually uses. Launch DCS through your normal Steam or standalone route, locate the running DCS process in Task Manager and use the open-file-location command. Note that location, then close DCS again.
- Rediscover DCS in Game Hub. Use the available scan, add-game or rediscovery control and select the confirmed
DCS.exe, not a desktop shortcut, updater or launcher. This is especially important after moving DCS, changing editions or installing an update that changes which executable is launched. - Start the programs in the right order. Open Game Hub first and leave it running, then launch the same DCS edition whose executable you confirmed.
- Match administrator privileges. DCS and Game Hub must run at the same privilege level. We recommend running both normally; an elevated DCS process can block a normally launched Game Hub from attaching to it.
- Check the calibrated display. The main DCS render window should be on the monitor selected during Tobii display setup. This often catches multi-monitor problems, although exported MFDs can remain on secondary screens.
If Game Hub shows the message while DCS is closed, there is no game window to detect. Judge the result after DCS has reached its main window or, preferably, after loading a cockpit.
Is Tobii Eye Tracker 5 compatible with DCS World?
Yes, Tobii Eye Tracker 5 supports DCS World through Tobii Game Hub when DCS is running in desktop mode.
| Tracker | DCS support path | What to verify |
|---|---|---|
| Tobii Eye Tracker 5 | Tobii Experience and Game Hub | The device is detected and calibrated, and the DCS profile points to the installation you launch |
| Tobii Eye Tracker 4C | Legacy Tobii Core and Game Hub path | Legacy software recognises the tracker and Game Hub still offers a DCS profile on that PC |
| EyeX, SteelSeries Sentry and older devices | Not supported through this DCS Game Hub route | Desktop gaze movement alone does not establish DCS compatibility |
| Integrated Tobii hardware | Depends on the computer and OEM implementation | Game Hub must recognise the device and provide an active DCS profile |
If you are configuring a supported device from scratch, compare each stage with our complete DCS eye-tracking setup and calibration sequence. Reinstalling DCS cannot make an unsupported tracker compatible.
Where is Tobii Eye Tracker 5 failing?
The quickest diagnosis is to identify the first application in which head or eye movement stops being detected.
| Test result | Likely fault | Next action |
|---|---|---|
| No movement in Tobii Experience | Tracker, USB connection, display setup, driver or calibration | Repair detection before opening DCS |
| Experience works, but Game Hub has no tracker or DCS profile | Game Hub installation or device compatibility | Update or repair the Tobii components and restart Windows |
| Game Hub reports "Unable to track game window" | Wrong executable, launch order or privilege mismatch | Rediscover the running DCS.exe and match privileges |
| Game Hub attaches, but no cockpit movement occurs | Disabled profile, competing tracker or DCS view-input problem | Enable the profile, close competing software and test another aircraft |
| Only one aircraft fails | Module-specific DCS input configuration | Back up and reset only that aircraft's input folder |
Saying "it doesn't work" is not enough to choose a fix. The most useful detail is the first row in that table where the expected movement disappears.
What should I do if the tracker fails in Tobii Experience?
If Tobii's own tracking preview cannot follow your eyes and head, the fault is outside DCS World.
- Reconnect the tracker directly to the PC rather than through an unpowered hub.
- Install offered Tobii software and firmware updates, then restart Windows if requested.
- Confirm the tracker is mounted beneath the display selected in Tobii's setup.
- Clean the sensor window with a dry microfibre cloth without spraying liquid onto it.
- Calibrate from your normal flying position, including any glasses you usually wear.
- Reduce direct sunlight, reflections and strong backlighting, and sit within the tracking area.
Do not continue changing DCS controls until the Tobii preview follows both gaze and head position reliably.
How do I enable Tobii in DCS World?
DCS responds only when the Game Hub profile is active and its combined tracking output reaches the simulator's view system.
- Open the DCS profile in Game Hub. Confirm the correct executable and make sure the required head- and eye-tracking contributions are enabled rather than set to zero.
- Assign one recenter control. Use a convenient button, but avoid binding the same button to centre several tracking programs at once.
- Close other tracking software. Fully exit TrackIR, OpenTrack, AITrack, FaceTrackNoIR and any other tool capable of sending cockpit-view movement.
- Launch DCS after Game Hub. Test in desktop mode and load a simple single-player cockpit rather than judging tracking from the menus.
- Inspect the aircraft's controls. DCS may identify Tobii's output as TrackIR or as a generic head tracker. The label does not mean TrackIR software must be installed.
- Recenter and test all movement. Look straight ahead, recenter, then turn, lean forwards and move sideways. Rotation and translation should respond; gaze should add movement when eye contribution is enabled.
Six-degree-of-freedom tracking is commonly supplied automatically rather than through ordinary joystick-style camera bindings. Our DCS head-tracking input and centring checks explain how the shared view side works.
Why does head tracking work but eye tracking do nothing?
If head movement controls the view but gaze appears inactive, DCS is already receiving Game Hub output; the usual causes are zero eye contribution, poor eye calibration or movement too subtle to notice.
Recalibrate your eyes, confirm eye contribution is enabled in the DCS profile and increase it gradually. Tobii gaze normally contributes to camera movement. Looking at a cockpit switch does not automatically move or click the mouse cursor, and DCS does not need to show a visible gaze dot.
How can I tell whether eye tracking is working?
Temporarily reduce the head contribution and set a noticeable but controlled eye contribution, then keep your head still while looking towards the edges of the cockpit.
If your honest assessment is "not that I can tell", compare the same movement with eye contribution set to zero. A clear difference confirms gaze input; no difference points back to calibration or the DCS Game Hub profile. Restore comfortable values after the test.
What if Tobii works in Elite Dangerous but not DCS World?
If Tobii works in Elite Dangerous but not DCS World, the tracker, driver and basic calibration are functioning; the remaining fault is specific to the DCS profile, executable or view-input path.
Game profiles are independent. Rediscover the exact DCS executable, confirm the DCS profile is enabled, match Game Hub and DCS privilege levels, and close any tracker that also produces TrackIR-style output.
Why does Tobii fail in only one DCS aircraft?
A one-aircraft failure usually comes from that module's saved input configuration rather than Tobii Game Hub.
Test a second aircraft in the same DCS session. If tracking works there, back up the affected module beneath your DCS profile's Saved Games\DCS...\Config\Input folder, then rename or reset only that module's input folder so DCS can rebuild it. Do not delete the entire Input folder unless you intend to lose bindings for every module.
Are TrackIR, OpenTrack or VR blocking Tobii?
Competing programs can override, duplicate or repeatedly recenter the same DCS cockpit-view input used by Tobii.
- Exit TrackIR, OpenTrack, AITrack and FaceTrackNoIR rather than merely minimising them.
- Remove duplicate view axes if a joystick hat, ministick or another device continually pulls the camera back.
- Use only one recenter command while testing.
- Keep DCS and Game Hub at matching administrator levels.
- Restart DCS after closing a competing tracker so the input devices are detected afresh.
If DCS shows a TrackIR-style device or the view drifts, freezes or snaps back, use our tracker-conflict and privilege troubleshooting steps to isolate the application taking control.
Can Tobii control the DCS cockpit view in VR?
A monitor-mounted Tobii tracker should be tested with DCS in desktop mode because a VR headset supplies its own head tracking and hides your eyes from the monitor sensor.
Disable DCS VR and close the headset runtime while diagnosing Tobii. Headset tracking and monitor-based Tobii tracking are not interchangeable; our guide to how DCS headset tracking works in VR explains the separate input path.
Should I reinstall DCS World?
Do not reinstall DCS until Tobii Experience passes its tracking test, Game Hub detects the tracker and the correct profile attaches to the running DCS executable.
A DCS reinstall will not fix a disconnected tracker, wrong monitor, failed calibration, unsupported model, stale Game Hub path or privilege mismatch. Repair or reinstall Tobii Experience and Game Hub first if their own tests fail.
If every aircraft still fails after a clean Tobii test, correct executable detection, matched privileges and removal of competing trackers, use the DCS installation's repair facility before considering a full reinstall. Record the tracker model, Steam or standalone edition, selected executable, profile status and exact error text first; otherwise the same configuration fault can be recreated immediately.