Install and configure a Thrustmaster joystick or HOTAS on PC, including drivers, axis bindings, calibration, TARGET software and common fixes.
To install a Thrustmaster joystick or HOTAS on PC, connect it directly by USB, install the correct model-specific driver if required, verify every axis in Windows, then create a simulator profile and bind analogue flight axes rather than button commands. Add small dead zones only where the hardware jitters.
For general PC flight simulation—including Microsoft Flight Simulator, X-Plane, DCS, FSX and Prepar3D—the hardware process is broadly the same. Console users do not install Windows drivers or TARGET software; the exact controller must be supported by both the console and the simulator.
How do I install a Thrustmaster joystick on PC?
The reliable order is hardware identification, driver installation, Windows testing and then simulator configuration.
- Identify the exact model. Check the label beneath the stick and throttle rather than relying on its appearance. Thrustmaster has produced similarly named devices with different drivers and platform support. If the unit has a platform selector, put it in the documented PC position before configuring it.
- Install the correct software. Some Thrustmaster controllers work as standard USB devices, while others gain a control panel and firmware support from the model-specific package. Follow the installer’s connection order because some packages expect the controller to remain unplugged until prompted. Our guide to identifying the correct Thrustmaster package and updating firmware safely covers this separately.
- Use a direct USB connection initially. Connect the stick and throttle directly to the PC while troubleshooting. Separate HOTAS components may appear as separate Windows controllers. Once everything works, a suitable powered hub can be tested if extra ports are needed.
- Check the hardware in Windows. Press the Windows and R keys, enter
joy.cpl, select each Thrustmaster device and open its properties. Move every axis through its full range and press every button. Use our Windows joystick testing procedure if an axis, hat switch or throttle is not responding. - Create a simulator profile. Select each physical device in the simulator’s controls screen and create or duplicate a profile. A separate stick and throttle usually need separate profiles or separate device columns.
- Remove unwanted default assignments. Presets often bind pitch, roll or throttle to more than one controller. Clear duplicates before adding your preferred controls, then save the finished profile under a recognisable name.
Do not run Windows calibration merely because the option exists. If the controller centres correctly and reaches both ends in joy.cpl, unnecessary calibration can create a new problem. Calibrate only when the raw Windows response is wrong and the model’s documented procedure supports it.
Which axes and buttons should I assign?
Bind every primary flight control to an analogue axis, not to a pair of digital button commands.
| Physical control | Simulator assignment | Avoid assigning |
|---|---|---|
| Stick left and right | Aileron or roll axis | Aileron left/right buttons |
| Stick forward and back | Elevator or pitch axis | Pitch up/down buttons |
| Twist grip or pedals | Rudder or yaw axis | Rudder left/right buttons |
| Main throttle lever | Throttle axis | Throttle increase/decrease buttons |
| Separate toe brakes | Left and right brake axes | A single brake button |
| Hat switch | View directions or cockpit look | Primary flight axes |
If an axis moves backwards, use the simulator’s reverse or invert option. Do not replace it with digital commands. A throttle that only jumps between idle and full power is almost always bound to increase/decrease commands rather than a throttle axis.
Start with zero dead zone and a neutral response curve. Add the smallest dead zone that stops centre jitter, then soften the response curve only if the aircraft feels too sensitive around the centre. Saturation or endpoint reduction should be a last resort after confirming that Windows sees the full physical travel.
Useful button assignments include elevator trim, brakes, flaps, landing gear, view controls, push-to-talk and autopilot disconnect. We recommend leaving rarely used functions on the keyboard until the primary axes and essential buttons have been flight-tested.
Simulator-specific binding differences
The same physical mapping applies across simulators, but profiles and calibration are handled differently.
- Microsoft Flight Simulator 2020 and 2024: create a profile for every connected device, filter the list to assigned controls and use input search to find hidden duplicates. The full profile and axis setup process for MSFS 2020 and 2024 explains the simulator-specific controls screen.
- X-Plane 12: calibrate each recognised controller inside X-Plane, assign every coloured axis bar and reverse only the axes that move in the wrong direction. Follow the detailed X-Plane 12 calibration and binding steps for that workflow.
- DCS: controls are normally stored per aircraft. Check every controller column because DCS may automatically assign pitch, roll, rudder or view axes to several devices.
- FSX and Prepar3D: inspect both axis and button assignments. Older default profiles can place the same control on a joystick, throttle and gamepad at once.
Do I need Thrustmaster TARGET software?
No—Thrustmaster TARGET software is optional and is unnecessary for straightforward axis and button assignments.
Use it only when a supported controller needs shifted button layers, macros or a combined virtual controller. It adds another layer between the hardware and simulator, which makes troubleshooting harder. A mistake we see constantly is binding both the TARGET virtual device and the original physical controllers, producing doubled axes or repeated button presses.
If TARGET is used, start its profile before opening the simulator and bind the resulting virtual controller. If the simulator can still see the physical devices, clear their duplicate assignments. Without TARGET, bind the physical stick and throttle directly and let the simulator store the profile.
Why is my Thrustmaster HOTAS not working correctly?
Most Thrustmaster HOTAS problems are caused by an incorrect platform mode, duplicate assignments, the wrong type of binding or a mismatch between physical and virtual devices.
- Nothing is detected: check the platform selector, reconnect to a direct USB port and confirm whether the device appears in
joy.cpl. Reinstall only the package intended for the exact model. - Buttons work but axes do not: select the correct controller in the simulator and bind controls labelled as axes. A button command cannot interpret proportional stick movement.
- The aircraft rolls, yaws or changes power by itself: search every connected controller for duplicate axes, including gamepads, throttles and virtual TARGET devices. Also check for a small amount of centre noise in Windows.
- An axis moves in the wrong direction: enable the simulator’s reverse setting for that axis. This is common with throttles, toe brakes and some sliders.
- The control spikes across its range: test it in Windows. A small dead zone can hide minor centre jitter, but it will not repair large spikes visible in
joy.cpl. - A saved profile disappears or stops responding: reconnect the components to the same USB ports and check whether TARGET is running. Physical and virtual controllers are treated as different devices.
- Only the stick or throttle is recognised: remember that many HOTAS sets expose their components separately. Test and configure each Windows controller rather than expecting one combined entry.