I was trying to fly the De Havilland Canada DHC-7 yesterday with my Thrustmaster TCA and couldn’t get the throttles to move the in-plane throttles back to zero or rather, full reverse thrust.
I really don’t want to go out and buy more peripherals!
I’m getting a bit concerned as I don’t see anything on YouTube about binding our Thrustmaster TCA stuff. It’s all Honeycomb Brave, etc.
And in Steam, this doesn’t work.
I saw that video and I have replied back to the guy. THIS is the only path for me:
AppData > Roaming > Microsoft Flight Simulator 2024 > WASM > MSFS2024 then the only directory in there is ‘fcr-embedded’.
There are no planes in that directory he has stated, only a file called, ‘fcr-embedded’.
One of these days I will find someone on YouTube that has the same set-up as me:
FS2024
Desktop PC
Steam
Thrustmaster TCA Captains Pack
My Thrustmaster Thrust Quadrant doesn’t work either; it does work with other in-house aircraft but doesn’t move the A320 Thrust levers at all.
Even in A320 calibration in the MCDU, shows at 0% even when moved.
I’ve actioned recommendations in the thread. They have improved functionality. However the TCA Captain X doesn’t work as perfect and flawlessly as it does in 2020. As a result I don’t have confidence in flying the planes.
I’ll wait for MS to hopefully issue a fix very soon.
As mentioned earlier,
I have the TCA X Captains pack,
fs2024 from game pass for PC (standard edition).
I did what Ripply6718 suggested 3 days ago in this thread and got them to work. I now have correct throttle axis.
I then tried what LH4284 said in their post and used the EFB to calibrate the detents and I now have reverse thrust as well as proper detent calibration.
I have yet to take flight with this issue resolved, because of work/life stuff, but can’t wait to give it a go!!
I can confirm this worked for me too! And any adjustments to the sensitivity curves work too (although you still can’t see the throttle move in the Control screen…)
Doesn’t work anymore;
the mapping for throttles axis in the TCA eng has been changed to a button ( 11 and 15)
so it does not move correctly; it’s moving on and off . Some fix is needed with Thrustmaster / Asobo …
Same here, but it depends what detent I am at. When scanning, sometimes i get 11 and 15, sometimes 10 and 14, sometimes x and y axis. For example, from flex to toga gives x and y axis. But from climb to flex gives buttons 10 and 14. This is in the Fenix btw. The inibuilds shows x and y axis no matter what detent. But here I have the issue that I can’t select reverse (allthough calibration shows the correct reverse setting).
It worked fine two days ago.
I have a Thrustmaster TCA Caption Airbus addition and the throttles are working correctly in msfs 2024
My reverse thrust is not working in all planes. I have it set to “toggle throttle reverse thrust” but its not working.
any help.
I am going to have to discipline myself and dedicate my next flying session to sorting out the nightmare that are my Thrustmaster TCA Captain Pack control bindings for the aircraft types I fly. I find the interface to be not really user friendly at all. What I really need is a step by step tutorial of how to create a set of bindings. I have tried many times and each attempt has been a failure and nothing but frustrating.
Finally, why is it that if you modify an axis curve you have create a binding profile, the axis curves are part of the binding set I am attempting to create.
Should this topic really be marked as solved?
I hope that this all gets resolved before Christmas. Until then I play the game properly because my TCA Captain X is my main interface for playing the game. I don’t want to have spend 20 hours in a week tinkering with files and settings for 5-10 aircraft’s to try to make things somewhat work.
In the meantime, I’m mainly just roaming the game with a control but not starting any missions.
Gamers have £2-4 gaming setups or rigs built around the TCA Captains X. It’s baffling that it doesn’t work as it should with the game at launch. Many of us are loyal FS gamers who spent big money on 2020 premium deluxe and on marketplace add-ons. Not only did MS not invite all of us to participate the alpha but our pheriperals aren’t even working properly at launch.
In the efb in the A320 (A330 and Beluga crashes the sim) I selected no reverse on axis configured the detents then selected yes to reverse on axis and got it to work
I marked it solved for the issue that I had started this thread with.
I have been a huge MSFS fan since the 80’s and I too have invested funds HEAVILY into my enjoyment of every iteration of the sim since I can remember.
Of course there are more issues that need addressing, ALOT more, however, those issues are posted in other threads on this forum and hopefully they get resolved in a timely manner…HOPEFULLY!
It is beyond infuriating at how the ball got dropped since fs2020 and we find ourselves dealing with the issues all over again in the here and now and no telling when any of them will get fixed.
I have since been able to get into free flight mode, file a flight plan, use beyond atc throughout the flight and had very minor graphic glitches, even at 36000 ft, all the way down to final and landing.
My sim rig is an absolute beast of a machine and handles fs2020 and fs2024 beautifully, so I know it’s not a pc issue.
My controls are now working as desired, thanks in large part to the input on this thread from other dedicated flight simmers.
I want to thank everyone for the info and help.
We have a very long way to go before this sim is fixed, polished, and working flawlessly.
It sucks, but, it is what we have to deal with for now.
As unacceptable as that is and believe me, it is absolutely unacceptable.
My only alternative is X-Plane, but I’ve spent enough time and money on the Microsoft title up to this point.
Happy flying!!!
They do work, you just need to bind the controls yourself. It’s not really something that should come as a suprise, how would you expect every aircraft to be configured against one set of controls?
It’s a normal part of any flight simulator experience and it always surprises me that these same complaints seem to come up so often.
T.A.R.G.E.T (Thrustmaster Advanced Programming Graphical Editor) ist ein Softwarepaket, mit dem man Thrustmaster-Regler testen, Thrustmaster Steuerungen testen, konfigurieren und programmieren kann. Download verfügbar auf der Thrustmaster Webseite unter TCA Sidestick Airbus Edition, Software. Hat jemand Erfahrungen damit?
A lot of problem for me too, for example if I try to assign park brakes switch with “scan” it doesn’t react like the switch doesn’t exist.
And it looks like the UI was done by a dev more than an UI expert, a big mess.
The funny thing is that TCA Captains is sponsored in the official MSFS2024 website, so I suppose Thrustmaster is like main partner, how is possible they rolled out with all these bugs??
Guys, sorry if it’s known already, I didn’t read the full 55 pages.
If someone still has issues with the TCA do the following 2 things.
To prevent the buttons show in search, instead of the axis, install current driver and go to the control panel of it. I mean the TM tool, not the sim.
There you have a checkbox for virtual buttons. They cause the buttons in the detents…uncheck it. Now the buttons for detents in axis will be gone.
Delete the double bindings. If you search for engine starters switch (search for Input and move engine starter) for example. You see there is fuel valve and all kinds of things set to.
Leave it with engine start only.
Do this with all other switches too.
This fixed all my issues with it. Especially planes not moving after pushback.
Here is a better solution that works for me. This video offers a step by step process within the sim:
Although it makes the TCA throttle quadrants more usable, I still don’t have the same precise control as in 2020.
My airbus throttle does not working correctly my first detent is reverse thrust when using throttle axis 0-100% and max reverse thrust on my throttle quadrant is idle when using throttle axis only aircraft it works properly on is the inibuilds aircraft
Everything worked in MS2020 so stupid of me to expect it to work in MS2024…