Help configuring Thrustmaster TCA Captain Pack X Airbus Edition in FSX Acceleration (FSUIPC4)

Hi Konstantinos,

FSX + FSUIPC can definitely work with the Thrustmaster TCA set, but the main “gotchas” are:

1) Windows sees the controllers but FSX/FSUIPC isn’t actually receiving inputs
2) FSX controls are conflicting with FSUIPC assignments
3) You’re testing in an “Airbus” cockpit/add-on that doesn’t use the default FSX flap/throttle events

Below is a clean, step-by-step way to get you to a known-good baseline.

1) Confirm Windows is seeing the TCA properly
Before touching FSX:

1. Unplug/replug the TCA devices (sidestick + throttle quadrant, and any add-on quadrant modules).
2. Open Windows “Game Controllers” and verify each device shows up and responds to movement.
3. Calibrate in Windows if anything looks dead/jittery.

If Windows doesn’t see movement here, FSX/FSUIPC won’t either.

2) In FSX: temporarily remove FSX’s own control assignments
This avoids the classic “FSX fights FSUIPC” problem.

1. Start FSX.
2. Go to Settings > Controls.
3. On the Control Axes tab, make sure the correct controller is selected in the device drop-down.
4. Either:
   • Uncheck Enable Controllers (quickest test), OR
   • Manually delete assignments for the axes you plan to set in FSUIPC (aileron/elevator/rudder/throttle/flaps etc).

Why do this? If FSX is already mapped to the axis and you also map it in FSUIPC, you can get “nothing happens”, jittering, or odd behavior.

3) Verify FSUIPC is actually receiving your inputs
Now check whether FSUIPC can “see” the hardware.

1. In FSX, go to Add-ons > FSUIPC...
2. Go to the Axis Assignment tab.
3. Move ONE axis (for example: move the flap lever or move the sidestick left/right).
4. You should see changing numbers in the input boxes when you move it.

If nothing changes in FSUIPC when you move the lever/stick, that’s the key clue—either the wrong device is selected, Windows/driver issue, or the axis isn’t presenting the way you expect.

4) Assign primary flight axes first (sidestick)
Do this with a default aircraft first (important).

1. Load a default FSX aircraft (example: the default Cessna) at a runway.
2. Open FSUIPC > Axis Assignment.
3. Move aileron axis → check Send direct to FSUIPC Calibration (recommended if you’re going to calibrate in FSUIPC).
4. Pick the correct control (Aileron).
5. Repeat for Elevator, Rudder (if applicable), Throttle(s) as needed.
6. Then go to the Joystick Calibration tab and calibrate each axis you assigned.

5) About the flaps lever (why it “does nothing” in the Airbus cockpit)
Two common realities here in FSX:

1. Some Airbus add-ons do not use the default FSX flap axis/events. If you test in that Airbus first, your lever may appear “dead” even though it’s working.
2. FSX default aircraft will always respond to standard flap commands, so they’re a good testbed.

So first, test the flaps lever in the default Cessna. If the flaps work there, your TCA/FSUIPC side is basically fine and we then tailor the mapping to the Airbus add-on.

6) If your flap lever is an AXIS, not buttons
In FSX, flaps are often easiest as buttons (increment/decrement), but you can attempt an axis if the hardware provides one.

In FSUIPC:

1. Go to Axis Assignment
2. Move the flap lever and see if FSUIPC detects it.
3. If it detects it, try assigning it to the Flaps axis (if available in the drop-down).
4. If the aircraft still won’t respond, switch strategy: assign flap lever positions to button presses (see next step).

7) If your flap lever behaves like “detents” (buttons/switches)
A lot of quadrant levers/detents end up presenting as buttons. In that case:

1. In FSUIPC go to Buttons + Switches.
2. Move the flap lever through detents and watch if button numbers light up.
3. Assign:
   • One detent/button to “Flaps Decr”
   • Another detent/button to “Flaps Incr”

That will at least prove the lever is being seen and can control flaps in a default aircraft.

A couple of targeted questions so I don’t send you down the wrong path

1. When you move the flap lever in FSUIPC’s Axis Assignment tab, do you see any numbers changing? (Yes/No)
2. In FSUIPC’s Buttons + Switches tab, do any button lights/numbers trigger when you move through flap detents? (Yes/No)
3. Which “Airbus cockpit” are you testing in—default FSX Airbus, or a specific add-on Airbus?
4. Are you running Steam Edition or boxed FSX Acceleration, and are you launching FSX “as Administrator”?

Answer those and I’ll tell you exactly which mapping method to use (axis vs detent buttons) and how to avoid conflicts so everything (sidestick, throttles, flaps, spoilers, reversers) behaves predictably.