Set up the Thrustmaster T.Flight HOTAS One on PC: install drivers, test axes, map controls, tune dead zones and fix detection problems.
Set the Thrustmaster T.Flight HOTAS One's selector to PC before connecting it, install the official driver, use a direct USB port and test each axis in Windows. Then map pitch, roll, throttle, rudder and the POV hat in your simulator, removing duplicate bindings and adding only the dead zone required.
For general PC flight simulators, treat setup as three separate stages: hardware detection, Windows testing and simulator assignment. Finishing them in that order makes faults much easier to isolate.
T.Flight HOTAS One PC setup, step by step
- Disconnect the HOTAS. Move its Xbox/PC selector to PC while the USB cable is unplugged. Do not change modes while it is connected.
- Position the controls. The throttle and stick can sit together or apart, but avoid pulling on the cable between them. If using compatible rudder pedals, make sure their connector is fully seated before testing.
- Install the correct driver. Use the official Thrustmaster PC package specifically offered for the T.Flight HOTAS One. If it asks when to attach the controller, follow that sequence rather than connecting it early.
- Connect directly to the PC. Use a motherboard or other direct USB port for initial setup, not an unpowered hub. Keep the stick and rudder centred and leave the controls untouched while Windows identifies the device.
- Test it in Windows. Press
Win+R, enterjoy.cpl, select the HOTAS One and open its properties. Slowly test the stick, throttle, twist rudder or rocker, POV hat and every button. Our Windows joystick testing and calibration steps cover incomplete travel, off-centre axes and calibration resets. - Create a simulator profile. Assign analogue controls to commands labelled as axes, then remove automatic assignments that duplicate them. This distinction is covered in our axis and button-mapping guide.
- Save and name the profile. Keep a basic aeroplane profile before making aircraft-specific versions. Some simulators store profiles per aircraft or control category, so confirm which profile is active before troubleshooting it.
Does the HOTAS One need a PC driver?
We recommend installing the official PC driver even if Windows initially recognises the HOTAS One as a generic controller. The correct package supplies the intended device support and control panel and may include the matching firmware tool.
Select the package for the T.Flight HOTAS One, not the similarly named HOTAS X or HOTAS 4. If the supplied instructions call for a firmware update, connect directly to USB and never unplug the controller while the update is running.
Which HOTAS One controls should I bind?
Bind the four main flight controls as analogue axes; buttons should handle discrete actions such as gear, brakes or trim.
| Physical control | Suggested assignment | Common mistake |
|---|---|---|
| Stick forward and back | Elevator or pitch axis | Using separate elevator-up and elevator-down button commands |
| Stick left and right | Aileron or roll axis | Leaving an automatically assigned gamepad axis active |
| Stick twist or throttle rocker | Rudder or yaw axis | Allowing both rudder controls to move accidentally |
| Throttle lever | Throttle axis | Binding throttle increase and decrease instead of the analogue axis |
| POV hat | Cockpit view or camera pan | Assigning it to both view and trim commands |
| Buttons | Brakes, trim, flaps, gear, autopilot disconnect or push-to-talk | Duplicating keyboard, mouse or gamepad assignments |
The twist grip and throttle rocker provide alternative rudder inputs and may feed the same logical rudder channel. Lock or avoid the twist function if you prefer the rocker or attached pedals, otherwise slight unintended movement can make the aircraft wander.
Microsoft Flight Simulator may offer a preset, but it should still be inspected for duplicated commands and digital rather than analogue assignments. For its profile menus and filtering controls, use our MSFS 2024 and 2020 joystick setup instructions.
How much dead zone should the HOTAS One use?
Start with a linear response and zero dead zone, then add the smallest dead zone that stops visible centre jitter. A few noisy input points do not justify sacrificing a large part of the stick's movement.
If an aircraft feels too sensitive around the centre, soften the response curve before applying a large dead zone. Use axis reversal when the throttle or control surface moves backwards; recalibration is not the correct fix for a reversed assignment.
Why is the T.Flight HOTAS One not detected?
Detection problems usually come from the wrong selector position, an unsuitable USB connection, an incorrect driver package or software intercepting the controller.
| Symptom | What to check |
|---|---|
Not shown in joy.cpl | Unplug it, select PC mode, restart if required and reconnect through a direct USB port. Reinstall the exact HOTAS One driver package if it remains absent. |
| Works in Windows but not in the simulator | Enable the controller in the simulator, create a fresh profile and remove any input filter hiding unassigned devices. For a Steam-launched simulator, disable Steam Input for that title as a test. |
| Buttons work but axes do not | Replace digital increase/decrease commands with assignments explicitly labelled as an axis. |
| Aircraft rolls or yaws by itself | Check every connected controller for duplicate bindings, centre jitter or an unlocked twist grip. Add a small dead zone only after finding the noisy axis. |
| Throttle operates backwards | Use the simulator's reverse-axis option. Do not reinstall the driver or run Windows calibration solely for reversed direction. |
| Rudder does not respond | Check the twist lock, throttle rocker and pedal connection in joy.cpl before changing simulator settings. |
| Random disconnections | Remove USB hubs and extensions, try another direct port and check that neither the USB cable nor the throttle-to-stick cable is under strain. |
If every control moves correctly in joy.cpl, the hardware and Windows side are working. At that point, concentrate on the active simulator profile, axis selection and duplicate bindings rather than repeatedly reinstalling the driver.