Why are TrackIR and joystick controls not working in FSX?

TrackIR and joystick controls usually stop working in FSX or FSX: Steam Edition because Windows has lost a USB device, FSX controllers are disabled, assignments conflict, TrackIR is paused, or camera software is blocked by mismatched administrator permissions. Test each device outside FSX first, then fix only the failing layer.

Nothing happens: what should I check first?

The first test is whether Windows and the TrackIR software can see their respective devices without FSX running. A mistake we see constantly is resetting simulator settings before establishing whether the hardware works at all.

1. Test the joystick in Windows. Press the Windows key and R, enter joy.cpl, select the controller and open its properties. Move every axis and press every button. No response here means a USB, driver or hardware problem rather than an FSX assignment.
2. Test TrackIR in its own software. The camera must be detected, the clip’s three tracking points should be visible, and the preview head should follow your movement. Make sure tracking is not paused.
3. Use direct USB connections. Connect the TrackIR camera and joystick before launching FSX. If both devices share an unpowered hub, dock or front-panel connection, move them temporarily to separate USB ports on the computer.
4. Start with a clean flight. Launch the TrackIR software first, then FSX, and test a default aircraft in its virtual cockpit. Leave camera add-ons, virtual-controller utilities and custom aircraft out of the test.
5. Match permission levels. Run FSX, TrackIR and control utilities normally where possible. If a legacy add-on forces FSX to run as administrator, TrackIR may need the same level; mixing elevated and non-elevated programs can block communication.

Which result identifies the fault?

The point at which input stops tells you which configuration to repair.

TrackIR 5 says “No device detected” — how do I fix it?

“No device detected” means the TrackIR software cannot communicate with the camera; FSX settings and reflector alignment cannot cause this message.

1. Close TrackIR and FSX completely. Unplug the camera, reconnect it to a direct USB port and reopen the TrackIR software.
2. Avoid hubs and adapters during diagnosis. A direct rear motherboard port is preferable on a desktop computer. Do not assume a hub is sound merely because a low-power joystick works through it.
3. Watch Windows Device Manager. Plug and unplug the camera and check whether the device list changes or an unknown device appears. No change across several direct ports points to the camera connection or hardware.
4. Reboot and repair the TrackIR software installation. This restores the camera driver if Windows detects the hardware but the TrackIR application does not. Follow the installer’s prompts about when to connect the camera.
5. Test another computer if available. A camera that remains undetected on a second Windows PC, using a direct USB port, is much more likely to have a hardware or cable fault.

The TrackClip and TrackClip Pro are not the camera. A TrackClip Pro’s USB lead powers its active LEDs, while the TrackIR camera requires its own USB connection. A broken, unpowered or badly positioned clip can cause “no tracking points”, but not “No device detected”. Our TrackIR camera, clip and profile setup guide covers target selection, reflector placement, centring and smoothness once the camera is recognised.

Why does TrackIR 5 have only one green light?

One green status light can be normal: TrackIR 5 separately reports whether it sees the tracking target and whether a supported simulator has connected. One light means only one of those conditions has been met.

• Tracking indicator on, game indicator off: the camera sees your clip, but FSX has not connected. Start TrackIR before FSX, update the software’s supported-title list and check the programs’ permission levels.
• Game indicator on, tracking indicator off: FSX has connected, but the camera cannot see a valid target. Check clip type, target mode, angle, distance, sunlight and reflective objects behind you.
• No green status lights: confirm that the TrackIR software detects the camera and that its status LEDs have not been disabled in the display settings. Software status is more reliable than the lamps alone.
• Orange or amber pause indication: unpause tracking and check that the pause hotkey is not shared with FSX or another utility.

If your symptom is “grüne LED leuchtet nicht” — the green LED does not light — first distinguish the status indicators from the dim infrared emitters around the camera face. The emitters illuminate reflective TrackClip markers; they are not the game-connection lights.

TrackIR works in its software but not in FSX

If the TrackIR preview follows your head but FSX does not, the hardware is working and the fault lies between TrackIR and the simulator’s camera system.

1. Launch TrackIR before FSX. Confirm that it is unpaused and tracking, then start the simulator. TrackIR is not configured as a joystick or flight axis inside FSX.
2. Use the virtual cockpit. A two-dimensional panel does not provide the same six-axis eyepoint movement. Test in a default aircraft’s three-dimensional cockpit before judging the integration.
3. Check the game-connection indicator. If the camera tracks the clip but the supported-game indicator stays off, use the TrackIR software’s built-in command to refresh its game-title list, then restart both programs.
4. Change conflicting hotkeys. TrackIR profiles commonly use F9 for pause and F12 for centre, while FSX also assigns function keys to views. Give pause and centre keys that FSX, the aircraft and camera add-ons do not use.
5. Clear competing view inputs. A POV hat, mouse-look mode or mapped pan axis can make the camera snap or appear frozen. Temporarily clear those assignments while testing.
6. Disable camera add-ons one at a time. If an add-on offers its own TrackIR integration, configure tracking through the route its settings expect. Two camera systems controlling the eyepoint can produce shaking, recentering or no movement.
7. Try an unmodified TrackIR profile. If the default profile works, the failed custom profile contains the problem; there is no reason to reset FSX joystick controls.

Why does the joystick work in Windows but not in FSX?

A joystick that responds in joy.cpl but not in FSX usually has disabled, missing or duplicated simulator assignments.

1. Open FSX controller settings. Go to Options, Settings, then Controls, and confirm that controllers are enabled.
2. Select every connected device. FSX has separate assignments for each joystick, yoke, throttle, pedal set, gamepad and virtual controller. Do not inspect only the device displayed first.
3. Check the axis assignments. Aileron, elevator, rudder and throttle belong under the control-axis section. Remove automatic assignments from devices that should not operate those axes.
4. Eliminate duplicate inputs. Rudder pedals and a joystick twist grip are often assigned to rudder together. The same problem occurs when both FSX and a control utility such as FSUIPC manage one axis.
5. Protect TrackIR from the POV hat. Clear joystick pan and view commands temporarily if moving or releasing the hat overrides head tracking. They can be restored later as backup controls.
6. Test calibration with the autopilot off. Use a default aircraft and confirm that its cockpit controls move with the hardware. If the aircraft drifts or an axis never reaches full travel, calibrate it in Windows before adjusting FSX sensitivity and null zones.

For missing axes, disabled controllers and bindings that refuse to stay saved, follow our step-by-step FSX joystick and throttle diagnosis. If the failing hardware is a Logitech yoke, throttle, pedals or panel, our Logitech flight-control USB and driver checks cover the device-specific layer.

When should I reset Standard.xml?

Reset Standard.xml only when Windows detects the joystick but FSX assignments are corrupted, duplicated, missing or impossible to save. This removes custom FSX mappings, so back up the file first.

1. Close FSX fully. Do not rename the file while the simulator is open because FSX may write its old settings back when it exits.
2. Open the application-data folder. Look under %APPDATA%\Microsoft\. Depending on the installation and whether boxed FSX has also been installed, the active folder may be FSX or FSX-SE.
3. Open the Controls folder. Rename Standard.xml to a backup name rather than deleting it.
4. Restart FSX. The simulator creates a fresh controls file. Configure and test one physical device at a time before restoring camera utilities or virtual controllers.

This procedure does not reset TrackIR profiles. Rebuilding Standard.xml cannot fix a TrackIR camera that reports “No device detected”.

Why is TrackIR not working in Microsoft Flight Simulator 2024?

On the PC version of Microsoft Flight Simulator 2024, the same diagnostic split applies: TrackIR must first work in its own software, then connect to the simulator’s camera system.

1. Verify camera detection and tracking points. If the TrackIR application says “No device detected”, troubleshoot USB detection; changing MSFS 2024 settings will not help.
2. Refresh the supported-game list. Use the TrackIR software’s built-in game-update function, close both applications, start TrackIR first and then launch MSFS 2024.
3. Check the connection indicator. If TrackIR sees the clip but does not show a game connection, check software versions, launch order and mismatched administrator permissions.
4. Inspect camera and head-tracking settings. Make sure tracking has not been toggled off and that pause, centre and camera-reset bindings do not share the same key or controller button.
5. Remove competing head trackers. Close other camera, face-tracking or virtual-input programs and test a standard cockpit view before restoring them individually.

Do not apply the FSX Standard.xml reset to MSFS 2024; its control configuration is separate. TrackIR 5 is a Windows PC peripheral and does not connect natively to the Xbox Series X|S, PlayStation 5 or PS5 Pro editions of MSFS 2024.

Does FSX: Steam Edition or a Steam Controller change the fix?

FSX: Steam Edition supports the same basic TrackIR and joystick arrangement as boxed FSX, but Steam Input can add a second virtual controller layer.

If both a physical controller and a virtual gamepad appear in FSX, assign each axis through one layer only. Temporarily disabling Steam Input for FSX is a useful test for ordinary joysticks; if you use an actual Steam Controller, keep the required input layer and remove the duplicate FSX assignments instead.

A Steam Controller is not a TrackIR camera, and its gyro or Steam Input configuration does not provide native TrackIR head tracking. If “Steam controller tracking number not working” means a parcel or order-tracking number, that is unrelated to FSX input settings and cannot be repaired inside the simulator.

What if it still does not work at all?

A total-failure report — “nothing happens here”, Portuguese “não funciona de jeito nenhum”, or Italian “non va” — still needs to be separated into device detection and simulator integration. “Non lo trova” usually means “it cannot find it”, which points first to USB detection.

1. Disconnect non-essential USB controllers. Leave one joystick and the TrackIR camera connected directly to the computer.
2. Repeat the external tests. Use joy.cpl for the joystick and the TrackIR preview for the camera. Repair only the device that fails its own test.
3. Load a default FSX aircraft and virtual cockpit. Keep camera add-ons and control utilities closed.
4. Add devices and utilities one at a time. The component added immediately before the fault returns is the conflict to investigate.
5. Reinstall FSX only as a last resort. A simulator reinstall can leave the existing application-data controls file in place, so it often preserves the very mapping fault you are trying to remove.

Can TrackIR and a joystick work together reliably in FSX?

Yes. The stable arrangement is TrackIR for head movement, the joystick or yoke for flight axes, and unique buttons for TrackIR pause and centre. Once each device works independently, avoid assigning the same view, axis or camera function through FSX, Steam Input and an add-on at the same time.