Why is my T.Flight Hotas One not working in MSFS 2024?

The Thrustmaster T.Flight Hotas One usually fails in Microsoft Flight Simulator 2024 because its PC/Xbox selector is in the wrong position, the operating system has not detected it, or MSFS has loaded an empty or incorrect control preset. Set the platform mode before connecting it, verify detection, then repair the axis bindings.

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

The Hotas One works with Windows PCs and Xbox consoles, but it must be placed in the correct hardware mode before its USB cable is connected.

Do not move the PC/Xbox selector while the unit remains connected. Unplug it, change the position and reconnect it so the platform identifies the correct device mode.

How do I fix the Hotas One in MSFS 2024?

Work through hardware detection before changing bindings; Microsoft Flight Simulator cannot map a controller that Windows or Xbox cannot see.

1. Close MSFS 2024 completely. Disconnect the HOTAS, put its selector in the correct position and reconnect it before restarting the simulator.
2. Use a direct USB connection. Temporarily remove hubs, extension cables and adapters. Try another USB port if the device does not power up or repeatedly disconnects.
3. Test it in Windows. Press Windows+R, enter joy.cpl, select the T.Flight Hotas One and open its properties. Move the stick, twist or rudder control, throttle and buttons. If nothing responds here, the fault is outside MSFS.
4. Repair the driver or firmware on PC. Reinstall the official Thrustmaster support software and restart Windows. Firmware maintenance for an Xbox-used unit is also performed through Windows; follow the updater's mode instructions exactly. Our Thrustmaster HOTAS installation and detection checklist covers this stage in more detail.
5. Open the MSFS control settings. Select the T.Flight Hotas One device tile rather than the mouse, keyboard or gamepad tile. Activate its default preset if one exists, or create a new custom preset if the selected one is empty.
6. Assign the primary axes. Change the command filter so all assignments are visible, then bind aileron axis, elevator axis, rudder axis and throttle axis. Use axis commands rather than digital commands such as aileron left, elevator up or increase throttle.
7. Remove duplicate controls. Search by input and clear competing flight-axis assignments from gamepads, virtual controllers and other connected sticks. Translation or remapping software can also hide the physical HOTAS behind a virtual device, so disable it temporarily while diagnosing the problem.
8. Save and activate the preset. Confirm that the custom preset remains selected for the Hotas One. If profile changes disappear after leaving the screen, follow our instructions for mapping and saving MSFS 2024 controller bindings.

On Xbox, there is no equivalent to the Windows controller test. After setting Xbox mode, try another console USB port and perform a full console restart. The need to use a standard Xbox controller in some menus does not by itself mean the HOTAS has failed.

Why does MSFS 2024 detect the HOTAS but ignore it?

If the HOTAS responds outside the simulator and appears in MSFS, the active preset or its assignments are normally at fault.

• Wrong preset: MSFS may have selected a blank preset or one made for another device. Select the Hotas One tile and verify the preset shown there.
• Button commands used for analogue controls: A centred stick needs aileron and elevator axis commands, not left/right or up/down button commands.
• Assignment filter hiding commands: A filter showing only assigned controls can make an empty preset look as though no commands are available. Display all commands before searching.
• Conflicting controller: A gamepad trigger, keyboard command or virtual joystick assigned to the same axis can continuously override the HOTAS.
• Aircraft automation: If the cockpit yoke or throttle visibly follows the HOTAS, the controller is working. Autopilot, autothrottle or an aircraft-specific system may be commanding the aeroplane instead.

Test with a simple default aircraft on a runway, with its engine running and autopilot disengaged. This separates a controller problem from aircraft start-up procedures, add-on systems and complex automation.

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

A reversed or unstable throttle is a calibration and assignment problem rather than a complete HOTAS detection failure.

• Toggle the axis reversal option if idle and full power are exchanged.
• Choose the throttle-axis range suited to the aircraft; a simple idle-to-full lever normally uses a 0–100% command rather than a range incorporating reverse thrust.
• Add only enough dead zone to stop genuine jitter. A large dead zone reduces useful travel and does not repair a failing potentiometer.
• Remove duplicate throttle bindings from the gamepad, keyboard and any virtual controller.

Use our MSFS 2024 joystick and throttle calibration procedure when the raw axes are detected but move incorrectly. If only the power lever remains unresponsive, check the throttle-specific causes in MSFS 2024, including aircraft automation and incorrect axis ranges.

If rudder alone is missing, check the stick's physical twist lock and confirm that either the twist grip, throttle rocker or connected pedals—not several of them at once—control the rudder axis.

Hardware fault or MSFS profile fault

The point at which the input disappears identifies the likely cause.

• If the Hotas One is absent from joy.cpl in PC mode after trying direct USB ports and reinstalling its driver, investigate the cable, selector, firmware or hardware.
• If it works in joy.cpl but is absent from MSFS, reset the simulator's device preset and disable controller-remapping software.
• If its input bars move in MSFS but the cockpit does not respond, correct the bindings or remove duplicate assignments.
• If the cockpit controls move correctly but the aircraft does not follow them, examine autopilot, autothrottle and aircraft-specific systems.

Reinstalling the entire simulator should be a last resort. It rarely fixes an incorrect platform switch, failed USB detection or a blank per-device control preset.