Learn how to calibrate a Thrustmaster joystick or HOTAS on PC, open Flight Control Panel properties, fix drift and set up HOTAS One.
To calibrate Thrustmaster flight controls on a PC, set the device to PC mode before connecting it, install the correct model-specific driver or firmware, test its raw axes in Windows with joy.cpl, then bind analogue axes in the simulator. Calibrate only if Windows shows bad centring or incomplete travel; otherwise tune the simulator profile.
This is a general Windows PC flight-simulator workflow for Thrustmaster joysticks, HOTAS units, throttles and pedals. On a console, use compatible hardware in the correct platform mode and configure it inside the simulator; the Windows testing and calibration tools are not available there.
How do I calibrate a Thrustmaster joystick on PC?
The reliable order is hardware mode, Windows testing, model-specific calibration if required, and simulator configuration last.
- Set the hardware mode while disconnected. If the controller has a PC, Xbox, PlayStation, combined or separate selector, choose the required mode before plugging in its USB cable. Changing the selector later can make it appear as another device and load a different simulator profile.
- Release all spring-centred controls. Place the stick, twist grip, rudder rocker and pedals at neutral while connecting the device. Do not hold them off-centre while Windows detects hardware that performs automatic start-up calibration.
- Use a direct USB connection for diagnosis. Connect to the PC rather than an unpowered hub. Once the controls work reliably, a powered hub can be tested if additional ports are needed.
- Install software intended for the exact product. Some Thrustmaster controls use standard Windows drivers, while others have a dedicated control panel, firmware updater or driver package. Never install firmware for a similar-looking model. Our Thrustmaster driver, firmware and connection setup covers the recognition checks to make before calibration.
- Open the Windows controller test. Press the Windows key and R, enter
joy.cpl, select the Thrustmaster device and open Properties. Move every axis slowly through its complete physical range and press each button. - Calibrate only when the Windows-level input is wrong. If an axis is off-centre, fails to reach an endpoint or moves erratically, reconnect the device with centred controls and retest. If a previous Windows calibration may be responsible, use Reset to default on the Settings tab where that option is available. Run the Windows Calibrate wizard only when the model supports it; otherwise follow that product's hardware calibration procedure.
- Create a clean simulator profile. Bind each physical control to its matching analogue axis, remove duplicate assignments and reverse an axis only where necessary. Validate the cockpit controls before adding response curves or dead zones.
Where do I find Thrustmaster Flight Control Panel properties?
Enter joy.cpl in the Windows Run box, select the controller, and choose Properties.
The exact panel depends on the model and installed driver. Windows may show standard Test and Settings tabs, while a Thrustmaster driver may replace them with a branded control panel. A throttle, joystick and USB-connected pedals can also appear as separate devices, so test each entry rather than assuming one panel covers the whole setup.
Healthy input has several recognisable characteristics:
- Spring-centred stick and rudder axes return close to the middle and remain stable.
- Each axis moves smoothly without jumps, gaps or unexplained movement in another axis.
- Full physical travel reaches both displayed endpoints.
- A throttle remains where it is placed; it is not expected to return to the centre.
- Toe brakes rest at an endpoint rather than the middle and may require reversal later in the simulator.
Windows labels such as X, Y, Z, Rz and Slider vary between products. Watch which indicator responds to the physical control instead of relying on an axis letter used by another model.
Which calibration method should you use?
The result in joy.cpl determines whether the fault belongs to the hardware layer or the simulator.
| What you observe | Correct action |
|---|---|
| All axes are smooth, centred where appropriate and reach full travel | Do not recalibrate the hardware. Fix assignments, reversal, sensitivity or aircraft-specific settings in the simulator. |
| An axis is wrong in Windows immediately after connection | Reconnect with spring-centred controls released, test another direct USB port, and use the exact model's reset or calibration procedure. |
| The problem began after using the Windows wizard | Use Reset to default if offered, reconnect and retest before attempting another calibration. |
| Windows is correct but one aircraft has mismatched throttle detents | Use that aircraft's throttle or detent calibration page rather than changing the Windows calibration. |
| A virtual controller appears alongside the physical device | Close mapping software and establish a clean physical-device test before rebuilding the virtual profile. |
A mistake we see constantly is recalibrating a clean Windows axis to fix a simulator binding conflict. Calibration cannot remove a duplicate assignment, change a digital command into an analogue axis or correct an aircraft-specific detent map.
How do I calibrate a Thrustmaster T.Flight HOTAS One?
The T.Flight HOTAS One normally establishes its hardware input automatically, so PC setup starts with the selector in PC mode and the spring-centred controls released during connection.
- Disconnect the HOTAS and move its platform selector to PC.
- Release the stick, twist rudder and any spring-centred rudder control so they sit at neutral.
- Connect the unit, allow Windows to detect it, and install only the driver or firmware intended for the HOTAS One.
- Open
joy.cpl, select the HOTAS One and inspect every axis in its Properties panel. - Move the stick, throttle and rudder controls gently through their full travel, then return the spring-centred axes to neutral.
- If the panel still shows restricted or displaced input, disconnect and repeat the neutral connection test before using any product-specific reset procedure.
Do not borrow a calibration button sequence from another T.Flight model: similar HOTAS units can use different procedures or firmware. On Xbox, set the selector to Xbox mode before connecting and perform assignments or sensitivity changes through the supported simulator. The Windows joy.cpl panel cannot be used on the console.
Is there a Thrustmaster joystick calibration tool?
There is no single Thrustmaster calibration tool that is correct for every joystick, HOTAS, throttle and pedal set.
Depending on the product, “calibration tool” may mean the standard Windows wizard, a Thrustmaster control panel, an automatic hardware routine or a model-specific utility. If a dedicated utility is prescribed, it must match the exact product; calibration tools and firmware are not interchangeable between devices.
Thrustmaster TARGET is primarily mapping and programming software for supported products, not a general calibration utility. It can create a combined virtual controller for macros or shifted button layers. When using that feature, clear corresponding bindings from the physical devices or the simulator may receive the same movement twice. Close TARGET when establishing a baseline test in joy.cpl.
How should Thrustmaster axes be configured in the simulator?
Once Windows input is clean, assign every continuous physical control to the equivalent analogue simulator axis.
| Physical control | Correct assignment | Avoid assigning |
|---|---|---|
| Stick or yoke, side to side | Aileron or roll axis | Aileron left and right buttons |
| Stick or yoke, forward and back | Elevator or pitch axis | Elevator up and down buttons |
| Twist grip, rocker or rudder pedals | Rudder or yaw axis | Rudder left and right buttons |
| Throttle lever | General throttle axis or an individual engine axis | Throttle increase and decrease commands |
| Left and right toe brakes | Separate left and right brake axes | Parking brake or a single brake button |
Check every connected stick, throttle, pedal set, gamepad and virtual controller for duplicate pitch, roll, yaw, throttle and brake bindings. Reverse an incorrect axis in one layer only; reversing it in both the driver and simulator leaves the direction unchanged and makes diagnosis harder.
For Microsoft Flight Simulator 2024, follow our MSFS raw-input, axis and sensitivity workflow. Simulator sensitivity settings can shape a clean signal, but they do not repair malformed input already visible in Windows.
How should throttle detents and reverse thrust be calibrated?
Physical throttle detents must be matched to the simulator and, for some detailed aircraft, calibrated again inside the cockpit tablet or aircraft configuration system.
Reverse thrust may occupy part of an analogue axis or be triggered by a button below idle, depending on the controller and aircraft. Establish normal axis travel first, then set idle, climb, maximum thrust and reverse positions in the aircraft where supported. Owners of Airbus-style hardware should use the model-specific TCA Airbus throttle calibration procedure rather than applying a generic joystick routine.
Why are my Thrustmaster controls still moving incorrectly?
If calibration does not fix the controls, compare Windows and simulator behaviour to identify the layer causing the fault.
| Symptom | Likely cause and fix |
|---|---|
| Aircraft rolls or yaws without input | If joy.cpl is stable, remove duplicate assignments and check automation or assistance settings. If Windows also moves, try a direct USB port and apply only a minimal dead zone after ruling out calibration. |
| Control jumps straight to full deflection | An analogue control is probably assigned to a digital left, right, up or down command. Replace it with the matching axis assignment. |
| Axis moves in the opposite direction | Use the simulator's reverse-axis option. Toe brakes often need individual reversal when they appear fully applied at rest. |
| Full hardware movement gives partial cockpit travel | If Windows also shows partial travel, use the model-specific calibration method. If Windows reaches both ends, inspect simulator saturation and aircraft calibration. |
| Throttle does not line up with detents | Configure the detents inside the aircraft and confirm whether reverse is treated as part of the axis or as a button. |
| One movement controls two functions | Remove duplicate bindings from other devices and check whether TARGET or another profile has created a virtual controller. |
| The wrong profile loads after reconnection | Confirm that the platform or combined-device mode has not changed. A different mode can present another device identity to the simulator. |
How much dead zone and sensitivity should I use?
Start with a linear response, full axis range and zero dead zone, then change only the setting needed to correct a measured problem.
- Dead zone: add the smallest amount that stops centre drift or unwanted brake input. It cannot fix missing travel or duplicate bindings.
- Response curve: soften the centre when a short desktop stick feels too sensitive. Long-throw sticks and yokes generally need less curve.
- Saturation: retain full range unless clean Windows input still cannot move the cockpit control to its stop.
- Reversal: apply it once, preferably in the simulator profile where it is easy to see and change.
For the difference between curves, dead zones and saturation, use our flight-control sensitivity tuning guidance.