Thrustmaster T.Flight Hotas One not working on PC or Xbox in MSFS 2024?

The Thrustmaster T.Flight Hotas One usually stops working in Microsoft Flight Simulator 2024 because its PC/Xbox switch is in the wrong position, Windows or Xbox has not detected the hardware, or MSFS 2024 loaded a blank device profile. Unplug it, select the correct mode, reconnect it, verify detection, then repair its axis bindings.

Is the T.Flight Hotas One compatible with your platform?

The T.Flight Hotas One is supported on Windows PC and Xbox Series X|S, but not on PlayStation 5.

Do not change the PC/Xbox selector while the HOTAS remains connected. Unplug it, move the switch, then reconnect it so the platform enumerates the correct device. Also confirm that the unit is a Hotas One, not the similarly named Hotas X or Hotas 4; their platform support and presets are not interchangeable.

How do I fix the T.Flight Hotas One on PC?

Fix Windows detection before editing MSFS 2024 controls, because the simulator cannot bind a device that the operating system does not recognise.

1. Close MSFS 2024 completely. Unplug the HOTAS, set its selector to PC, reconnect it and then restart the simulator.
2. Connect it directly by USB. Remove hubs, extension leads and adapters while diagnosing the fault. Try another USB port if the unit does not power up, vanishes intermittently or repeatedly reconnects.
3. Test the controller in Windows. Press Windows+R, enter joy.cpl and open the T.Flight Hotas One properties. Move the stick, twist grip, throttle, rudder rocker and buttons. If they do not respond here, changing MSFS bindings will not help.
4. Repair the driver only if Windows detection fails. Restart Windows and reinstall the official driver package for the exact Hotas One model. Update firmware only through the matching official updater, follow its connection instructions exactly and never change mode or disconnect the unit during an update. Our broader USB and Windows controller checks cover the remaining operating-system faults.
5. Select the correct device in MSFS 2024. Open the controls settings and choose the Hotas One device entry, not the keyboard, mouse or gamepad. If no useful default preset appears, create a new custom profile.
6. Check the active profile. In MSFS 2024, including Sim Update 5, profiles are associated with each physical peripheral. Editing a gamepad profile does not edit the HOTAS. See how per-device MSFS 2024 profiles are stored if your assignments appear under the wrong controller.
7. Bind the four primary axes. Display all available commands, then assign the stick to aileron and elevator axes, the intended twist or rocker control to rudder axis, and the lever to throttle axis. Use analogue axis commands rather than commands such as aileron left, elevator up or increase throttle. Our manual joystick-axis configuration procedure gives the full mapping sequence.
8. Remove duplicate assignments and save. Clear competing flight-axis bindings from gamepads, other sticks and virtual controllers. Temporarily disable controller-remapping tools or Steam Input while testing, then save the Hotas One profile and confirm that it remains selected.

What changes on Xbox Series X|S?

On Xbox Series X|S, use Xbox mode, a direct console USB port and a fully restarted, locally installed simulator.

There is no Xbox equivalent of joy.cpl. A standard Xbox controller may still be needed for some menus, which does not mean the HOTAS has failed. If the console does not recognise it, shut down the simulator, disconnect the stick, verify Xbox mode, try another console USB port and restart the console rather than merely suspending the title.

If a Windows PC is available, you can disconnect the unit, switch it to PC mode and use joy.cpl to test the hardware. Switch it back to Xbox mode only after unplugging it.

Why does MSFS 2024 detect the HOTAS but ignore its inputs?

If the Hotas One works in joy.cpl and appears in MSFS 2024, the active profile, command type or a conflicting controller is usually responsible.

• Blank or wrong preset: Select the Hotas One itself and activate a usable default or custom profile. Do not choose a preset for another T.Flight model simply because its name is similar.
• Digital commands on analogue controls: A centred stick needs aileron and elevator axis commands, not separate left, right, up and down commands.
• Hidden command list: Change the control filter from assigned commands to all commands before searching for an axis.
• Duplicate axis: A gamepad trigger, second joystick or virtual device can continuously compete with the physical HOTAS.
• Aircraft systems overriding you: If the cockpit controls visibly follow the HOTAS, the input is reaching the aircraft. Autopilot, autothrottle, AI assistance or aircraft-specific control logic may then be taking command.

Test with a simple default aircraft placed on a runway in a ready-to-fly state. Keep autopilot and AI piloting off. If a binding scan sees the axis but the cockpit control does not move, correct the assignment; if the cockpit responds, the HOTAS itself is no longer the fault.

Why is the throttle reversed, jittery or using only part of its travel?

A moving but incorrect throttle indicates an axis-range, reversal, sensitivity or hardware-reading problem rather than total device failure.

• Idle and full power are swapped: Toggle the reversal setting for that throttle axis.
• The lever includes an unwanted reverse range: Use the 0–100% throttle-axis command for conventional idle-to-full travel. Map reverse separately unless the aircraft and your chosen setup deliberately use part of the lever for reverse.
• The lever will not reach an endpoint: Return the sensitivity curve to a simple linear setting while testing. A small extremity adjustment can compensate for limited travel, but first check the raw movement in joy.cpl.
• The input jitters: Add only enough dead zone to suppress minor noise. If the same jitter appears in joy.cpl, the source is the controller rather than MSFS.
• Another throttle takes over: Remove duplicate throttle axes from gamepads, virtual devices and other quadrants.

If forward thrust works but reverse does not, follow our reverse-thrust binding diagnosis rather than rebuilding the whole HOTAS profile.

If only rudder is missing, check the stick's physical twist lock and decide whether the twist grip, throttle rocker or separate pedals will provide rudder input. Binding several of them to the same axis often produces unstable or cancelled movement.

T.Flight Hotas One still not working on PC?

The last place at which the input works identifies whether the remaining fault is hardware, Windows, the MSFS profile or the aircraft.

Reinstalling all of Microsoft Flight Simulator should be a last resort. It rarely corrects a wrong hardware mode, failed USB detection, empty per-device profile or duplicate axis assignment. If the Hotas One remains absent from joy.cpl on more than one PC with the correct mode and driver, a cable, selector or internal hardware fault is the more likely diagnosis.