Depends on what issue you’re getting. My TCA quadrant is all working as it suppose to for all the switches and buttons. I don’t have the addons yet, but just the quadrant, everything is working.
I’m using just the quadrant too. But if compared to x-plane configuration(screenshot), lets say for engine start lever, it has (button 5) to set as On, (button 21) as off(shutoff). Even eng norm mode(button 23) selector is also a virtual button in x-plane. It makes configuring this quadrant for other planes so much easier.
In MSFS 2020, engine on is only button 3(and somehow with some custom configuration either from asobo or a32nx, once I push it to off, it recognizes it as engine shutdown, but not on other planes.)
I’m trying to configure this to work with WT CJ4, but with the lack of virtual buttons, it is almost impossible to setup.
I suppose it’s not designed for non A320. Just remember that there are 3 different terminology in the controls. SET, TOGGLE, and SET ON/OFF. Each of this behaves differently depending on what the type of buttons and switches you use.
You might also need to double bind different commands into the same engine switches to make sure it covers all things needed for engine starts at the same time.
I’ll try on the CJ4 and see how it goes.
Thanks. Hopefully can make it more functional. Screened through almost the whole thread, seeing issues from landing gear only can set as up but not down, eng ing can set crank and ign/start but not norm really surprises me in terms of customization that i’m being allowed to do to this quadrant. Seems like a lot of workload for developer if this issue always need a developer to create a code for it. This is one part they should learn from x-plane perhaps.
The landing gear is an issue that I haven’t got around to test it yet. Since I don’t have the addons yet. But the Norm switch issue is already working and solved for a while. So if you’re still having issue with it. You need to delete all your profile you’re using for the TCA quadrant reset the to the default bindings.
Yeah, the norm switches is already working for me too. Not complaining for A320 cause maybe asobo or a32nx did some coding for it but not for other airplanes. There’s no way I can set anything to bind to the norm button cause its not a “button” in MSFS2020 whereas it is registered as a button in X-plane.
Like I said too, this should be something easier for us to amend rather than depending on the developer, or future 3rd party aircraft to solve.
Hopefully posting this here can get some attention from the developers. Let us map the entire quadrant and not just follow blindly the button assignments provided by thrustmasters only.
Yeah, they probably do it on the software side that “in an absence of button 9 and 10 being active, always apply button X”. It could also be done the same way on the landing gear “In an absence of button 20, always apply button Y” where both X and Y buttons are coming from the sim itself and not from the quadrant.
1 Like
The landing gear is working fine, both up and down. Got my addon two days ago and almost all buttons worked right out of the box. The remaining buttons i mapped myself in the sim.
I’m getting mine next week. Anything I should prepair for or etc?
Read this topic, all the info is there… 
Calibrate it before using.
You will have to map the spoiler and flaps axis in the sim. And the autobrake is not mapped correctly. Otherwise everything works. (All infos are referring to the addon)
1 Like
Hin everybody! have the following problem:
At first, the thrustlever on the thrustmaster was in the idle position but on the simulator at around 40%. With the help of the numerous tips, this problem is (almost) solved. Thank you!
Now the thrust lever in the MSFS no longer moves slowly forward, but „jumps“ in one big step as soon as you have reached the CLB position on the TCA.
Thanks for your tips!
Which steps have you done for the following?
- Download and install the Driver and Firmware TFHT 5, and Upgrade your firmware to version 1.61.
- Do a factory calibration process of your quadrant. And make sure you have pressed the red buttons for all 5x detents, including the full reverse.
- Download and install the Experimental Custom FBW version of the A32NX mod using the installer.
- Follow this steps to configure the throttle level a32nx/docs at fbw · flybywiresim/a32nx (github.com)
- Change your sensitivity level in the sim controls settings to 0,0,0 fully linear.
1 Like
Many thanks for your help!
I habe done all the points, but I was quite overwhelmed with the throttleconfiguration.ini file, which version is required. I finally realized that I had a problem with the Mod experimental Version, because the „jumps“ during the thrust also happened when the thrustmaster was not plugged in, but instead I controlled the keyboard with F3. With the development version everything works perfectly! Is the problem only with me?
Yes, it’s the experimental version that has the throttleconfig.ini file. You have to use your thrustmaster. If you use the keyboard, the scaling is going to be different.
What the throttle config ini file does is to change the power scaling being applied to the throttle from your physical hardware. Note that there’s a lot of power travel between IDLE to CLB (roughly 85% of thrust) but only 10% thrust between CLB to FLX/MCT, and 5% from FLX/MCT to TOGA. But the Thrustmaster TCA quadrant, has all the detents at equal distance with each other (20% each).
This means, from IDLE to CLB, the sim has to cover 85% of thrust with only 20% of physical thrust coming from the hardware. While above that, it needs to scale down to cover 10% in the sim with 20% physical thrust. And then scales down even more to cover only 5% using the same 20% physical thrust.
And what the Throttleconfig.ini file does is to do just that. To interpret the power scale coming from your hardware and apply the appropriate scaling in the sim, so that both physical throttle detents matches the detents in the sim. When you switch this control to keyboard, the scaling still applies, but because the keyboard has a completely different scaling involved, you would experience the jump around.
So if you use the experimental version of the mod to use the TCA Quadrant, you have to commit to keep using it. Don’t switch hardware.
All right, good to know! But why doesn’t the development version actually need the throttleconfig.ini file? By the way, MCDU no longer shows the remaining refusing distance to the destination airport during the flight under flight plan (in DEV-Version), no idea why. Which configuration would you recommend for the experimental version? Thank you again!
That’s because Dev version does not have a custom flybywire being modeled. The throttlleconfig file is a direct manipulation of the flybywire system. Since it’s tied to the throttle controls. So only the experimental version, which has a custom flybywire system is the only version that can utilise the throttleconfig file. The dev version, without a custom flybywire system, means it cannot utilise the throttleconfig since it can’t manipulate the throttle control directly.
You can start by using the guideline specified here. a32nx/docs at fbw · flybywiresim/a32nx (github.com) Test them. If they still not match up slightly, then adjust the values accordingly until you find that sweetspot. Everyone’s hardware is different and setup differently, so you can use this as a base, but eventually you have to find that config sweetspot yourself.
Followed this post with interest, i have the AB throttle quadrant and now have it working to the throttle dents all lined up and tying in with the throttle position. I now have a reverse thrust issue this does not move past idle and will not travel the assigned distance and only shoes 26% power and the aircraft will not move. I have tried changing the ini file to various settings with no success it still won’t link reverse thrust. Any ideas please, if this is not successful I will have to go back to the development version
Make sure your binding is set to Throttle Engine Axis (0-100%) not the usual Throttle Engine Axis without the 0-100.