I updated the firmware and recalibrated and all seems fine, pretty happy with the way it works but no idea if the reverser is what it should be. Just made a bit bumpy landing but that was my fault. 
… I’ll need to check later if I used Neo’s or your settings though.
As long as you’re using the Throttle 1/2 Axis (0 to 100%) and not the regular Throttle 1/2 Axis as shown in @MoparChrgr69 screenshot. You should be able to use the reverser by adjusting the netural and sensitivity - according to my screenshot.
I mean not having a problem with the reverser, just that I dont know what it should be as in real life.
What do you mean? The quadrant has a reverser where you unlock it and pull back to the reverse zone. As is the thrust lever in the cockpit view as well. As soon as you unlatch and pull the lever back to the reverse zone, the lever in the cockpit does the same. Which I think that’s how it is in real life.
MoparChrgr69 said that it took away more from the trust reverser curve. I dont have a problem with the curve and seems to work fine. Only that I dont know how it should be as IRL and I assume it just goes full reverse as it does now… Hope it makes sense now. 
That’s why I reduce the “sensitivity -” curve which manages the reverser zone to make it scale better at the start-medium reverse thrust before it bottoms out in the end.
Start menu -> Thrustmaster -> Firmware Update…
1 Like
I updated mine also for a week ago, works fine
There is a new driver for the TCA quadrant Link
I’ve updated my driver and firmware, and I only feel a slight difference that I just recalibrate my sensitivity by 1%.
So to clarify the issue I had with the reversers…
With Firmware 1.56, If I go into the reverser area, the reversers on screen followed exactly (prior to FS2020 update 6) and would hit 100% reverse thrust when the throttle lever hit the bottom of the axis.
After update 6, the reversers on screen moved “faster”, hitting 100% reverse thrust while the physical throttle was only about halfway down into the reverser area. I still have a good bit of physical throttle travel, but in game it thinks the throttles are already at 100% reverse. No amount of changing the sensitivity- curve would change that. It would change how fast they bottom out, but they still bottom out when the hardware is only halfway down in the reverser area. The thrustmaster driver settings utility showed that the hardware was responding normally and showed movement all the way to the very bottom of the physical hardware.
When I installed firmware 1.60, the throttle response in the driver show it hitting the end before the physical throttles were at the bottom. So inexplicably, the new firmware is reporting that my hardware isn’t travelling as far as it did with 1.56. When I went in game, this loss of overall throttle axis area compounded with the loss of reverser response in FS2020 update 6 to make the throttle hit 100% reverse thrust when the physical throttle axis was only ~25% into the reverser area. In other words, in game showed 100% reverse thrust, but the physical throttle was only where the TOP yellow arrow mark on the physical throttle is between the plastic tabs/indicators on the throttle lever. The physical throttle lever still has a lot of travel to go to get down to where the bottom yellow arrow is between the plastic indicator tabs.
Now, that said, because of the shorter reported axis response in the driver for 1.60, I would need to recalibrate the neutral position and possibly the sensitivity curve in game to compensate which might make the reversers work closer to what they were before firmware 1.60 but would take away another tiny bit from the overall axis response which would likely make the detent problem worse as I explain in the next paragraph…
Side note: I wonder if the overall loss of axis travel in FS2020 update 6 is why we can’t get the detents to line up perfectly anymore. With a shorter overall travel, even slightly, the onscreen throttle has to move “faster” to cover the shorter distance allowed from the hardware. This means a steeper curve in game which makes the second detent not line up right.
1 Like
Hi, could you share your sensitivity settings after update to 1.60 ?
Thanks for all your feedback in this thread! I am going to try and map these to my x56 switches; just to clarify (probably a dumb question) but you’re mapping multiple functions to the same button in this screenshot? I.e. the multiple joystick 3s are all the same joystick 3 from the throttle?
I see what you mean, it is the same here. At half reverse thrust on the quadrant, the throttle handle is at full in sim.
After updating my firmware to 1.60, here’s my new sensitivity settings:
This is where I mapped my throttle axis:
And this is where the in-game detent is located according to my physical TCA quadrant detents:
TCA quadrant detent on IDLE:
TCA quadrant detent on CL (Even though it doesn’t look like it lined up in this image. It actually does in respect to the aircraft systems as you can still hear the “click” and the A/THR mode also register it as a valid CLB thrust mode):
TCA quadrant detent on FLX/MCT:
TCA quadrant detent on TOGA:
TCA quadrant detent on Reverse:
Yeah, sadly it is what it is now. I guess it’s a good thing it’s not common to use half reverse thrust, since on landing everyone will be doing a full reverse thrust anyway. So it’s not that big of a deal.
2 Likes
Yes, button 3 on the TCA throttle quadrant is the engine 1 switch. Button 4 is the engine 2 switch. They are physical switches on the hardware quadrant and not momentary buttons.
The multiple functions are what is needed to get the engines running, and keep them running, in the vanilla a320, as well as various other aircraft. In the A32Nx mod, I think the only function needed is “set engine 1 fuel valve” (or 2, respectively) since that mod has logic to handle the other functions slightly differently from the vanilla a320. If you ever fly other aircraft, the magneto and starter functions are needed too, for example, so it’s easier just to have all the mappings relating to engines on those switches so I can jump to different aircraft type in game.
1 Like
Ah ok, unfortunately it won’t work on the x56 since they are toggle switches and won’t stay in place 
What about the engine mode? Does it work now with FW 1.60?
No, that’s something Asobo has to fix.