Thrustmaster TCA Captain Pack X Airbus Edition

I would not split the throttle range in the gc-map.mcf, so that the throttle-lever universal remains operational for all aircraft types.

Instead, I would create a subfolder for the affected aircraft in my own user directory and enter the deviating data between the external controller and the aircraft TMD there. I'm doing this for the C130.

What kind of splitting would you like to have on which plane?

Quote from cristianodesa

I'm not sure, but it seems to me the Airbus throttle positions are related to the TCA virtual buttons.
I would love to have the option to config the positions as well, as I have customized detents on my TCA.

Which axles should be adapted for which aircraft?

Mine worked out of the box.

Quote from vhild

Mine worked out of the box.

same

Quote from ApfelFlieger

What kind of splitting would you like to have on which plane?

A320

But does anyone know if the split can be done, does the config support such thing? I do not mind doing it globally, in fact, I prefer that as I only fly Airbuses.

I noticed you have MacBook Pro with Thursmaster, is there any driver you installed? For some reason, my stick does not work, AeroFly does not see anything. I even tried a 3rd party app and the OS does not see anything.

Hello,

I recently purchased Thrustmaster TCA Captain Pack X Airbus Edition set and it appears it is completely ignored by AeroFly FS 4 on both PC and Mac. Since it has the very same functionality as the other products plus an extra switch that can flip between PC setting and Xbox I thought I would share the USB Vendor/Product ID and maybe IPACS could add support. Or if anyone knows how to edit the schema, I could not find any text file containing Thrustmaster in the game folder.

Here is how it reports on MacOS with the switch set to PC (sorry for the Czech language, USB IDs are there):

TCA Sidestick X Pilot:

  ID umístění:	0x00100000
  Typ připojení:	Removable
  Výrobce:	Thrustmaster
  Sériové číslo:	XXXXXXXXXXXXXXX
  Rychlost připojení:	12 Mb/s
  ID dodavatele USB:	0x044f
  ID USB produktu:	0x040e
  Verze USB produktu:	0x0200
  Přidělený výkon:	2.5 W (500 mA)

here is info from the quadrant when connected directly:

TCA Q-Eng 1&2:

  ID umístění:	0x00100000
  Typ připojení:	Removable
  Výrobce:	Thrustmaster
  Sériové číslo:	XXXXXXXXXXXXXXX
  Rychlost připojení:	12 Mb/s
  ID dodavatele USB:	0x044f
  ID USB produktu:	0x0407
  Verze USB produktu:	0x0200

it seems the quadrant is not detected when connected via the internal USB HUB which is something that many users have problems with. Probably wrong USB-C cable and power issues. Anyways, here is how the sidestick reports when set to XBOX mode:

TCA Sidestick X:

  ID umístění:	0x00100000
  Typ připojení:	Removable
  Výrobce:	Thrustmaster
  Sériové číslo:	XXXXXXXXXXXXXXXXX
  Rychlost připojení:	12 Mb/s
  ID dodavatele USB:	0x044f
  ID USB produktu:	0x0410
  Verze USB produktu:	0x0100

So all and all, it looks like the USB product IDs are:

• 0x040e for the stick in PC mode (acts also as USB HUB)
• 0x0410 for the stick in XBOX mode (no USB HUB functionality)
• 0x0407 for the quadrant

Hello,

I am trying to configure TCA Sidestick X Airbus Edition as it is not properly detected by the game and I am almost done, but I need to split the range of the throttle axis between thrust (0-50000) and reversers (50100-65535). There is no documentation on how to do that, any ideas?

            <[tmchannelmap][element][83]
                <[string8u][FunctionID][TwinJetThrustReverse1]>
                <[string8u][InputID][X]>
                <[uint64][DeviceUniqueID][9983255117548841988]>
                <[string8u][DeviceIDString][TCA  Quadrant Airbus Pilot]>
                <[bool][IsDigital][false]>
                <[bool][IsValue][false]>
                <[float64][Sign][1]>
                <[float64][Direction][0]>
            >
            <[tmchannelmap][element][84]
                <[string8u][FunctionID][TwinJetThrustReverse2]>
                <[string8u][InputID][Y]>
                <[uint64][DeviceUniqueID][9983255117548841988]>
                <[string8u][DeviceIDString][TCA  Quadrant Airbus Pilot]>
                <[bool][IsDigital][false]>
                <[bool][IsValue][false]>
                <[float64][Sign][1]>
                <[float64][Direction][0]>
            >

Quote from FrankLFRS

It works, but I think that Aerofly should include a way to record the positions min/max, iDLE, CL and FLEX (because an update of the device could change something and make it fail with Aerofly).

Pretty please, or at least let us know how to set this by editing the mapping file.

I have now taken a closer look at the data on the A320 in the controls.tmd and in the subdirectory "base" in the system.tmd. With a closer look at your wish, I don't think it makes sense to change anything about these two files.

Therefore, I also looked at my gc-map.mcf on my Mac:

(1) SECTION [list_tmchannelmap][Channels][]

For me, the ThrustLevers are already separated by the menu Settings in the FS 4 into the two axes "X" and "Reverse 1" or "y" and "Reverse 2":

            <[tmchannelmap][element][225]
                <[string8u][FunctionID][TwinJetThrottle1]>
                <[string8u][InputID][X]>
                <[uint64][DeviceUniqueID][1234567890]>
                <[string8u][DeviceIDString][TCA Q-Eng 1&2]>
                <[bool][IsDigital][false]>
                <[bool][IsValue][false]>
                <[float64][Sign][1]>
                <[float64][Direction][0]>
            >
            <[tmchannelmap][element][227]
                <[string8u][FunctionID][TwinJetThrustReverse1]>
                <[string8u][InputID][Reverse 1]>
                <[uint64][DeviceUniqueID][1234567890]>
                <[string8u][DeviceIDString][TCA Q-Eng 1&2]>
                <[bool][IsDigital][false]>
                <[bool][IsValue][false]>
                <[float64][Sign][1]>
                <[float64][Direction][0]>
            >

So nothing can be changed here.

(2) SECTION [list_tmdevicesetting][Settings][]

A possible change could take place here:

            <[tmdevicesetting][element][4]
                <[uint64][DeviceID][67568719]>
                <[string8u][DeviceName][TCA Q-Eng 1&2]>
                <[string8u][DeviceType][Throttle]>
                <[string8u][DeviceMode][]>
                <[bool][Enabled][true]>
                <[bool][GamePad][false]>
                <[float64][Sensitivity][0.5]>
                <[float64][DeadZone][0]>
                <[int32][Priority][0]>
                <[list_tmdevicecalibration][Calibration][]
                >
            >

I use the controller PFT-PUMA to fly helicopters and it has a fine adjustment in the Calibration line:

            <[tmdevicesetting][element][2]
                <[uint64][DeviceID][0987654321]>
                <[string8u][DeviceName][PFT-PUMA]>
                <[string8u][DeviceType][Joystick]>
                <[string8u][DeviceMode][]>
                <[bool][Enabled][true]>
                <[bool][GamePad][false]>
                <[float64][Sensitivity][0.5]>
                <[float64][DeadZone][0]>
                <[int32][Priority][0]>
                <[list_tmdevicecalibration][Calibration][]
                    <[tmdevicecalibration][element][0]
                        <[string8][InputID][X]>
                        <[float64][Zero][-0.015]>
                        <[float64][Min][-0.1]>
                        <[float64][Max][0.045]>
                    >
                    <[tmdevicecalibration][element][1]
                        <[string8][InputID][Y]>
                        <[float64][Zero][0.002]>
                        <[float64][Min][-0.062]>
                        <[float64][Max][0.066]>
                    >
                    <[tmdevicecalibration][element][2]
                        <[string8][InputID][Z]>
                        <[float64][Zero][-0.129]>
                        <[float64][Min][-0.25]>
                        <[float64][Max][-0.08]>
                    >
                    <[tmdevicecalibration][element][3]
                        <[string8][InputID][Rx]>
                        <[float64][Zero][-0.215]>
                        <[float64][Min][-0.32]>
                        <[float64][Max][-0.11]>
                    >
                    <[tmdevicecalibration][element][4]
                        <[string8][InputID][Ry]>
                        <[float64][Zero][-0.248]>
                        <[float64][Min][-0.45]>
                        <[float64][Max][-0.046]>
                    >
                    <[tmdevicecalibration][element][5]
                        <[string8][InputID][Rz]>
                        <[float64][Zero][-0.08]>
                        <[float64][Min][-0.28]>
                        <[float64][Max][0.12]>
                    >
                    <[tmdevicecalibration][element][6]
                        <[string8][InputID][Slider 0]>
                        <[float64][Zero][-0.0425]>
                        <[float64][Min][-0.12]>
                        <[float64][Max][0.035]>
                    >
                    <[tmdevicecalibration][element][7]
                        <[string8][InputID][Dial]>
                        <[float64][Zero][-0.0575]>
                        <[float64][Min][-0.14]>
                        <[float64][Max][0.025]>
                    >
                >
            >

I think a comparable calibration is possible with the TCA quadrant.

With the PFT-PUMA I proceeded in such a way that I always looked at the individual movements in the SETTINGS/CONTROLS menu and changed them until it fit me.

Quote from lzap

I noticed you have MacBook Pro with Thursmaster, is there any driver you installed? For some reason, my stick does not work, AeroFly does not see anything. I even tried a 3rd party app and the OS does not see anything.

No, I don't have a driver, to my knowledge there is no driver for the Mac either. I just plug in all my controllers and they work.

I've been using Thrustmaster's various TCA products on my Macs since they've been around. And regardless of the product and the Mac, it always works plug%Play.

I just remembered that I initially had a Mac with a USC A-port. When switching to my Mac with USB C port, the controllers did not work with a USB C-USB-C cable, but only with the USB C-USB A cable plus USB A to USB C adaptor. Try it out if it's because of it.

Oh thanks, that worked! I used USB-C HUB that has 2 USB-A and it worked! In fact, the game detected the hardware and it works out of box on MacOS. I could not get it working on PC, probably because the profile already had some mappings or something, not sure how this works.

The only thing that does not work is reverse thrust, I remember in Windows I unchecked the Virtual Buttons option in the driver options app which presses buttons automatically for thrust and flaps. I guess the firmware remembers it, going to uncheck it on PC to see if it makes any difference on Mac.

Great that it already works.

I remember that at first I also had difficulty assigning reverse appropriately. I then reset the TCA quadrant and assigned reverse first and then throttle. However, the assignment can also be made in the gc-main.mcf via the keyboard.

Quote from Jet-Pack (IPACS)

... Avoid using USB hubs as well...

Moin Jan,

on my MacBook, external controllers with USB C connecter only work if I connect them via a USB-C to USB-A hub.

Thank you it works now. The key thing to get it running for me was to delete gc-map.mcf there were some old bindings in the way so the game would not automatically assign. Also, it is worth mentioning that the integrated USB hub did not work for me as you noted and only after directly connecting both devices, it worked flawlessly. Also, make sure to uncheck the Use Virtual Buttons in the Windows Control Setup, it appears to store this setting in the hardware firmware. This is checked when it comes from factory so you should be good to go.

Still, I would be interested in documentation of the format.

Quote from Jet-Pack (IPACS)

Please also try resetting the device to default

For the record, tried this tree times, did not work at all. The only thing that worked was deleting the file completely. Not sure what was going on. I could see both devices and buttons working, it was just simply not mapped. An explicit button "create default mapping" would be nice here.