Just tried this again in the sim… figured why not, since the mooney is screwed up… Updated to latest firmware, but most indents dont line up at all with the ones in the sim. Man oh man oh man… frustration overload.
yes thanks, but it still doesnt fit the FLEX right. its too early.
Yea, the detents dont work properly even with those settings.
1 Like
The game had another small patch after I posted that setting. I’ll do another reconfiguration on the sensitivity and share it here again once I got all the detents right.
1 Like
So… Just played around a bit with the A320 mod and the Flightstick & Quadrant.
Everything feels good, but Engine 2 doesnt actually respond to the throttle input. The proper thrust lever moves, but no engine response.
Thrust lever for engine 1 will control thrust on both engines. The heck is that all about?
And the Autopilot constantly banks left, right, left right… In the Flight controls page you can see the control surfaces always moving. Bleh…
And selecting heading and speed, its jumps in increments of 10s instead of 1s. No idea what happened there now.
Uhh, that’s weird… Can you check your settings again?
- Flight model needs to be set to Modern.
- Assist settings all need to be Hard/True to Life.
- Copilot assist set to off.
If you’re on the A320NX mod, delete it, and install the latest development version. They’ve fixed the autopilot and swaying issues.
Heading and Speed increments always jumps on 10 increments when using the mouse wheel. Clicking on them will turn at 1 increment.
I’ve also double checked my thrust lever using my sensitivity setup that I shared in my previous post. I have no issues. All my detents work properly.
So, quick question since you seem to have done the most testing thus far. Does the version of A32NX (stable vs dev) affect the sensitivity/zone setting one should use? I ask because the only thing different I can tell between you and me at this point is that I’m using the A32NX stable while you appear to be recommending the dev version.
I’ve tried your settings from above and it’s way off for me. I used your recommended actions and sort of worked out my profile which is the level best I can do. The idle to 50% is WAY sensitive but I seem to have no choice on that without sacrificing something else. The back end of reverse flips back to 30% forward if I don’t hold short of fully back but works fine if I ease back and stop short. I think I’ve figured out the general effect of each change and I flat cannot get it working better any other way. It’s doable for now. I’ve updated firmware as you did, etc.
Also, I notice the buttons so work in dev mode A32NX but not stable (I’m assuming they’ll that to stable soon). But, I did not try the settings you recommended exactly in dev mode after the firmware update thus my question. Thx!
I don’t think that they should affect the sensitivity.
I think what’s missing from my screenshot is the Throttle binding. I’m using Throttle 1 Axis (0 to 100%). Don’t use the default Throttle 1 Axis. There’s two of them. Make sure you use the one with (0 to 100%) in the name and use Reverse Axis. That should interpret the neutral setting of -50% for me to be at the right place as Idle in the cockpit.
When I reconfigure my setup after the firmware update. I reset my sensitivity curve to 0, 0, 0, 0. Then I deleted all my existing profile so it will revert back to Default profile that the sim gives. The sensitivity will be set to what the default profile gives for the TCA quadrant. Then I start a new blank profile and rebind all my keys appropriately. And when I adjust my sensitivity to have the correct detents, that’s what I end up.
Well, I know I’m using the right axes. I’ll try that procedure (deleting/re-setting up the profile from 0). that’s the only thing I didn’t do. I simply edited the settings from the existing profile previously. Thanks again! 
Never mind, chief. The settings work.
The thing with the increments, that must be new. It didnt do it before.
Hey guys. For those without 3D printers, check out my Joystick Gremlin configuration which get’s the quadrant into a reasonable working state: Thrustmaster TCA quadrant still not completely working
1 Like
gotta make one of those for T.A.R.G.E.T.
2 Likes
For those people frustrated by the lack of Knob return to “Norm” it’s easy to fix.
In MSFS define a keyboard shortcut for “set Norm” (I set mine as CTRL+i)
Run the Thrustmaster TARGET software. Define a profile for the quadrant and set a button “Release” action for buttons 7 & 8 to “Pulse” the keyboard CTRL+i.
Start TARGET and run the profile before starting MSFS.
This means every time the knob returns to “Norm” on the quadrant it does so in the plane 
Works a treat for me.
Now after the latest, really small update today to mfs2020, my quadrant has been detected as Touch Pointer. I tried unplugging the cable and all that but didnt help.
I made a topic about it but does anybody know how I can use the tca quadrant for a 747 ? How do I bind the engines all together if possible? Since I’m long awaiting my honeycomb throttle ? Much appreciated
I did set my thrust for the lever 1 also for 3, and leveler 2 for also 4.
Thanks for the reply . In the settings where do I go about it ? Kinda hard without visuals. Much appreciated.
Thanks I tried it and it’s all reversed the throttles