Does ChasePlane support VR, TrackIR, Tobii and Xbox controllers in MSFS?
Learn how ChasePlane works with MSFS VR, TrackIR, Tobii and Xbox controllers on PC, plus tracking conflicts and Xbox console limits.
Yes, with one platform limit: ChasePlane works alongside Microsoft Flight Simulator VR, TrackIR, Tobii Eye Tracker and Xbox controllers on a Windows PC. It cannot run on an Xbox console. Use only one head-tracking source at a time, and remove overlapping controller bindings to prevent doubled movement or unwanted camera changes.
What works with ChasePlane in MSFS?
All four options are usable with ChasePlane on PC, but they perform different jobs and should not all control the camera simultaneously.
| Device or mode | ChasePlane support | Main caveat |
|---|---|---|
| VR headset | Yes, in MSFS on Windows | The headset and MSFS must remain responsible for head tracking; use ChasePlane camera movement conservatively. |
| TrackIR | Yes | Do not let both native MSFS tracking and ChasePlane process the same movement. |
| Tobii Eye Tracker | Yes | Head and gaze contributions depend on the selected settings; avoid duplicate native tracking. |
| Xbox controller | Yes, when connected to a PC | Buttons assigned in both MSFS and ChasePlane can trigger two camera commands at once. |
This support applies to the Windows versions of MSFS 2020 and MSFS 2024. The installed ChasePlane release must support the simulator version you are running.
Can ChasePlane run on an Xbox console?
No. ChasePlane is a Windows companion application that connects to a locally running copy of Microsoft Flight Simulator, so it cannot be installed on an Xbox Series X or Series S. Streaming an Xbox or cloud-hosted simulator to a PC does not turn it into a compatible local installation.
An Xbox-branded controller is different: it works as a Windows input device when connected to a PC. Our ChasePlane installation and simulator-connection guide explains the PC requirement in more detail.
How should TrackIR or Tobii be configured?
Choose either ChasePlane or MSFS to process TrackIR or Tobii camera movement, rather than allowing both applications to react to the same input.
- Verify the hardware first. Confirm that the TrackIR or Tobii software can see the device and respond to your head movement.
- Select one tracking route. If ChasePlane is handling the device, disable the equivalent native MSFS camera-tracking input.
- Set a neutral position. Sit in your normal flying posture, centre the tracker and then centre the ChasePlane view.
- Tune one layer only. Set sensitivity, curves, smoothing and dead zones in one application wherever possible. Stacking adjustments makes movement difficult to diagnose.
- Test cockpit and external views. Check that changing camera presets does not reactivate a second tracking input or load an unsuitable aircraft profile.
A common mistake we see is native MSFS head tracking being left active after ChasePlane tracking has been enabled. The result is exaggerated movement, shaking or a view that slowly walks away from its saved position. See our detailed TrackIR and Tobii configuration steps for the device-specific setup.
How does ChasePlane behave in VR?
ChasePlane can be used while MSFS is in VR, but the headset must remain the sole source of physical head movement. TrackIR and an external Tobii Eye Tracker should normally be disabled as camera inputs during a VR session.
- Keep ChasePlane motion, inertia and turbulence effects low at first; strong artificial camera movement can be uncomfortable in a headset.
- Retain a dedicated MSFS VR recentre control. Recalling a ChasePlane camera position does not replace headset recentering.
- Do not assign the same button to VR recentre and a ChasePlane preset, or the viewpoint may jump twice.
- Eye tracking built into a VR headset for rendering or interface selection is separate from using Tobii to steer the MSFS camera.
Our practical ChasePlane VR setup covers view positioning and the settings most likely to cause discomfort.
How do I bind an Xbox controller without conflicts?
On a Windows PC, spare Xbox controller buttons can trigger ChasePlane camera commands, saved views and related functions. Set up the aircraft controls in MSFS first, then add ChasePlane bindings around them.
- Create or clone an MSFS controller profile. This avoids disrupting a working aircraft-control layout.
- Choose spare buttons or button combinations. Prioritise saved-view recall and camera switching rather than sacrificing primary flight controls.
- Search for duplicate MSFS assignments. Clear any simulator camera command that uses the same button unless both actions are genuinely intended.
- Keep recentering separate. Use distinct controls for MSFS VR recentering, tracker centering and ChasePlane camera reset functions.
- Test each binding individually. If the view snaps, changes mode or moves twice, temporarily remove the ChasePlane assignment to identify which layer is responding.
If the controller itself is not behaving properly in the simulator, start with our MSFS controller setup for Windows PC before assigning ChasePlane functions.
Fixing doubled movement, drift and unexpected camera changes
- Movement is doubled: both ChasePlane and native MSFS tracking are processing TrackIR or Tobii input.
- The view drifts: centre the tracking device again, check its dead zone and disconnect the controller temporarily to rule out analogue-stick drift.
- A button performs two actions: inspect assignments in both MSFS and ChasePlane, including aircraft-specific controller profiles.
- The VR viewpoint jumps: separate the headset recentre command from ChasePlane preset and reset bindings.
- The wrong view loads: confirm that ChasePlane has selected the intended aircraft profile rather than a similarly named variant.