Set up the Thrustmaster TCA Captain Pack Airbus Edition in FSX, including sidestick, throttles, detents, reverse thrust and common fixes.
To configure the Thrustmaster TCA Captain Pack in FSX or FSX: Steam Edition, install and test both USB devices, enable controllers, assign the sidestick and quadrant separately, then remove every duplicate axis. FSX treats the Airbus detents as ordinary axis positions, so reverse thrust and some switches need extra mapping or aircraft-specific configuration.
Before opening FSX, verify both TCA devices
Windows must recognise the sidestick and quadrant as separate working controllers before FSX can map them. Attach the flap and speed-brake modules to the unplugged quadrant, install the official Thrustmaster driver and firmware package according to its prompts, then connect the sidestick and quadrant to USB.
Press Windows+R, enter joy.cpl, and test every axis and button. Each axis should move smoothly without jumping or remaining short of an endpoint. If either device is missing, work through our FSX joystick detection and assignment checks before creating bindings.
How do I assign the TCA Captain Pack controls in FSX?
Configure each controller separately in FSX and remove the automatic assignments that FSX often applies to the wrong device.
- Open the control settings. Go to
Options > Settings > Controls. PressAltfirst if the menu bar is hidden, then make sure controllers are enabled. - Remove duplicate axes. Select each entry in the Controller Type list and inspect its Control Axes assignments. Delete unwanted mappings before adding new ones. In particular, clear the sidestick's small throttle slider when using the quadrant, and remove any aileron, elevator or rudder assignments automatically given to the quadrant.
- Assign the main axes. Use Change Assignment and move only the intended control through a wide sweep. If FSX detects a different, jittering axis, centre every lever and try again.
| TCA control | FSX assignment | Setup note |
|---|---|---|
| Sidestick left/right | Ailerons axis | Use Reverse only if the cockpit control moves oppositely. |
| Sidestick forward/back | Elevator axis | Forward stick must command nose-down elevator. |
| Sidestick twist | Rudder axis | Leave unassigned and lock the twist if using pedals. |
| Sidestick base slider | None | Leaving this mapped to throttle causes conflicting inputs. |
| Left throttle lever | Engine 1 throttle axis | Recommended for the default FSX Airbus A321. |
| Right throttle lever | Engine 2 throttle axis | Reverse the assignment only if movement is backwards. |
| Speed-brake lever | Spoilers axis | Check that fully retracted does not leave spoilers deployed. |
| Flap lever | Flaps axis | Test every physical detent against the cockpit indication. |
For a four-engine aircraft, assigning only Engine 1 and Engine 2 leaves the other engines uncontrolled. If one lever should operate every engine across a mixed fleet, assign it to the general throttle axis and leave the second lever unused. FSX has no convenient native per-aircraft controller profiles, so choose the arrangement that suits the aircraft you fly most.
What sensitivity and null-zone settings should I use?
Start with high or full sensitivity and a very small null zone, then add only enough dead zone to stop unwanted movement around the centre. Large null zones hide calibration faults and make the sidestick feel unresponsive.
Throttle, flap and speed-brake axes should normally have little or no null zone. If a throttle cannot reach idle or maximum, or the two levers produce different outputs, use the proper TCA throttle hardware calibration procedure rather than trying to compensate inside FSX.
Do the Airbus throttle detents work in FSX?
The physical IDLE, CL, FLX/MCT and TOGA detents do not activate authentic Airbus thrust modes in the default FSX A321. FSX reads the levers as ordinary continuous throttle axes, so a marked detent is simply a particular throttle position unless the aircraft add-on interprets it.
Native FSX also does not consistently turn the quadrant's below-idle travel into usable reverse thrust. For default aircraft, the dependable method is to bring both levers to idle and use the control bound to F2 to decrease thrust into reverse. If the reverser mechanism appears as a button, that button can be assigned to the same command and held while reverse is required.
More capable Airbus add-ons may provide their own detent and reverse-range calibration. Follow that aircraft's configurator and remove any duplicate FSX throttle bindings it tells you not to use. Our quadrant-specific detent, reverser and add-on-module setup explains the hardware side in greater depth.
Which Captain Pack switches can FSX use?
FSX can use most controls that Windows presents as ordinary axes or buttons, but it has no direct command for every Airbus-labelled function.
- Assign the sidestick hat to view panning and a spare button to the autopilot master or brakes as preferred.
- Map the landing-gear lever to the available gear command. If FSX sees only one button rather than separate positions, use the gear toggle and verify the cockpit state after loading a flight.
- Assign the parking-brake control to the parking-brake command.
- The rudder-trim control can use rudder-trim left and right commands if FSX detects its movement as buttons.
- Engine master switches, the engine mode selector and autobrake positions may lack suitable generic FSX assignments. Leave them unassigned or configure them through the aircraft add-on.
A latching hardware switch can become out of sync with a toggle command after loading or resetting a flight. Use explicit on/off or up/down commands where FSX offers them; otherwise cycle the physical switch once to restore agreement.
Why do the controls move on their own or conflict?
Unexpected control movement nearly always comes from duplicate assignments, reversed axes or a second virtual controller.
| Symptom | Likely fix |
|---|---|
| Moving a throttle also moves the elevator, mixture or view | Select the quadrant in FSX and delete every automatically assigned axis except the intended controls. |
| The cockpit throttle moves backwards | Toggle Reverse for that specific axis; do not reverse unrelated controls. |
| Only one engine responds | Check that the levers are assigned separately to Engine 1 and Engine 2, or use the general throttle axis for all engines. |
| The rudder twitches or never centres | Do not map both the sidestick twist and pedals. Lock and unassign the twist when following a dedicated rudder-pedal and toe-brake setup. |
| FSX appears to receive each input twice | A TARGET profile or other virtual-controller layer may be exposing another device. Map either the direct TCA devices or the virtual controller, never both. |
| Assignments disappear or move to another device | Reconnect the hardware to the same USB ports before starting FSX and avoid changing hubs after saving the setup. |
| Flap or speed-brake modules are absent | Disconnect the quadrant from USB, reseat the module cables, reconnect it and retest in joy.cpl. |
Do complex Airbus add-ons need different settings?
Complex Airbus add-ons often need their own throttle calibration and switch assignments rather than the default FSX mappings. Their systems may interpret CL, FLX/MCT, TOGA, reversers and engine switches directly, while the stock A321 does not.
Build a clean generic setup for the default A321 first. When an add-on supplies a controller configurator, calibrate there and clear any overlapping FSX axes to prevent two systems from commanding the same control. The underlying FSX control procedure is the same in boxed FSX and FSX: Steam Edition.