Fix a Thrustmaster Z axis that is not working. Test it in Windows, check the twist lock and device mode, then correct bindings and conflicts.
A Thrustmaster flight stick Z axis usually stops working because a twist lock is engaged, Windows is reading it under another axis name, the simulator lacks a rudder-axis binding, or a second controller is overriding it. Test the control in Windows first; that separates a device fault from a simulator configuration problem.
What does the Z axis control on a Thrustmaster stick?
On a twist-equipped flight stick, the Z axis normally controls the rudder or yaw, but axis labels vary between Thrustmaster models and simulators. Windows may identify the twist as Z Rotation or Rz, while another device may use Z for its throttle lever.
Move one control at a time and watch which indicator responds rather than relying on its name. Some Thrustmaster HOTAS sticks have no twist rudder, while others include a physical twist lock; do not force a locked or non-twisting grip.
How do I find where the Z-axis problem is?
The quickest diagnosis is to check whether Windows receives any movement before changing simulator settings.
- Check the hardware: gently twist the grip through its normal travel. If the model has a rudder-lock switch, release it first.
- Open the Windows controller panel: press
Win+R, enterjoy.cpl, select the Thrustmaster device and open its properties. - Move only the suspect control: watch every axis bar or crosshair, including rotation and slider indicators. Our Windows joystick testing procedure explains how to interpret this panel.
- Test the full travel: confirm that the indicator moves smoothly from one end to the other and returns close to centre when released.
| Test result | Likely cause |
|---|---|
| The controller is not listed | USB connection, platform selector, driver or device-detection problem |
| A differently named axis moves | Normal axis labelling; bind the moving input in the simulator |
| The axis works in Windows only | Missing assignment, wrong profile or duplicate simulator binding |
| Only the twist remains completely static | Twist lock, unsupported twist axis or possible hardware fault |
| The indicator jumps or will not centre | Calibration, dead-zone or sensor-noise problem |
Why does the Z axis work in Windows but not in the simulator?
If the axis moves correctly in joy.cpl, the Thrustmaster hardware and Windows input are working; the fault is inside the simulator's control profile.
- Bind it to the continuous Rudder Axis or Yaw Axis command, not separate rudder-left and rudder-right button commands.
- Make the assignment under the correct controller. A common mistake we see is editing the keyboard, throttle or gamepad column instead of the flight stick.
- Clear duplicate rudder assignments from pedals, gamepads, throttles and other connected controls. A noisy second axis can override the stick.
- Check that the dead zone has not been set so high that normal movement is ignored, and that sensitivity or saturation has not reduced the usable range to almost nothing.
- Save the profile and reload the aircraft. Some simulators maintain separate control profiles for different aircraft or controller presets.
Thrustmaster TARGET can also present a virtual combined controller instead of the physical devices. If a TARGET profile is running, bind only the intended virtual controller; otherwise stop the profile, reconnect the hardware and restart the simulator. Our Thrustmaster installation, mode and TARGET checklist covers this distinction.
What should I do if Windows cannot see the axis?
An axis that does not respond anywhere in Windows must be fixed at the device level before simulator assignments can help.
- Verify that the axis exists: check that the model supports stick twist and that any lock is disengaged.
- Reconnect directly: unplug the controller, restart the PC if necessary and connect it directly to another USB port rather than an unpowered hub.
- Check the platform mode: where the device has a PC or console selector, set it to the correct position before reconnecting it.
- Remove virtual-profile interference: stop any active TARGET script and retest both the physical controller and any virtual controller shown in
joy.cpl. - Check the model-specific software: install or repair the supported Thrustmaster driver package if that model uses one. Do not substitute software intended for a similar-looking device.
Calibration cannot restore an axis that produces no signal at all. If movement exists but the centre or range is wrong, follow our safe calibration process for Thrustmaster controls instead.
What if the Z axis moves erratically or drifts?
An axis that jumps, flickers or moves without being touched has a different fault from a completely missing axis. Start with a modest dead zone and calibration, then use our specific fixes for Thrustmaster Z-axis drift if the raw Windows signal is unstable.
Do not hide severe noise with an enormous dead zone. That may stop unwanted rudder movement, but it also removes fine yaw control during take-off and landing.
When is a hardware fault likely?
A hardware fault is likely when the unlocked twist axis remains static in Windows across different USB ports or another PC while the stick's X and Y axes continue to work normally. That pattern points to the twist sensor, its wiring or the grip mechanism rather than a simulator profile.
If the entire controller disappears, investigate its cable, USB connection, platform compatibility and device mode first. Avoid opening a controller that remains under warranty; internal repairs can damage wiring and may affect warranty cover.
What if the HOTAS is connected to a console?
A PC-compatible Thrustmaster controller is not automatically compatible with every console. Confirm that the exact model supports the console, select the correct hardware mode and reset the simulator's controller profile; Windows testing with joy.cpl applies only to a PC connection.