A32NX engine mode selector TCA quadrant bug

Discussion Hub Aircraft
, ,
1

After SU9 I noticed bugs in Thrustmaster TCA quadrant engine mode selector ign position ( A32NX latest dev build)
Anyone else with the same issue?

3 Likes
2

This is an SU9 issue and happens also with the default one. It’s due to how MSFS processes the binding.

2 Likes
3

Oh god, thanks mate.
Honestly I don’t Know what Asobo have been fixed in SU9.

4

Mouse goes all laggy until you return the mode selector back to the middle postion. Then mouse works as normal.

5

Yep, same here. Seems we can’t use the TCA engine mode selector until they fix the binding process.

6

I noticed the same issue and it happens both in A320 and A32NX for me.
Strangely it does not happen for CRANK mode as this is stable flicking to crank and then back to norm.

As I never use crank, I removed the button 7 as it seems to be a conflict when using both button 8 and button 7. So these settings works as a workaround for me:
Norm: button 8 on release
Ign/start: button 8 on press.
Crank: unassigned

If I’m ever going to use crank, I can always flick it with the mouse.

But it would of course be nice if it was fixed so it worked as before SU9.

6 Likes
7

Thanks mate, I’m gonna try your workaround.

8

Thia workaround works, thx mate… :+1:

9

Working for me as well. Thanks mate!!!

10

Same workaround applied by me, it does work now! (sort of, I have to pull the selector to “crank” to make it go to the “norm” position, but it is not a game breaker…

11

Thanks for this workaround!

12

This worked, yes i never use crank either. thank you!

13

My workaround was to flip the bindings on the columns.
By default on the Norm selector is that Button 7 on Release is on the left column, and Button 8 on release is on the right column. I just flipped them with each other.

So Button 8 on release on the left column, and Button 7 on release on the right column. That solves the IGN/Start and moving it back to NORM. But the same flicking issue now lies on the Crank.

I think the binding issue is coming from the right side of the column, or the secondary binding. Not necessarily “both”.

3 Likes
14

Hi. I adopted the same solution yesterday. That’s the only one.

15

Does it like flicker from ign/start and norm?

16

why can’t microsoft/Asobo keep their hands off things that work?

3 Likes
17

Also here:

18

I agree. Another update another series of bugs from Asobo. I keep trying to cut them slack because they are dealing with a complicated system, but I’m at the end of my rope with them. Do they actually have a head of test? It is looks unlikely, but if they do, they should be be asked to leave as they clearly seem to be struggling with the job.

2 Likes
19

Good workaround thanks! Works for me (crank fails as you say but that’s OK with me… for now). What on earth have Asobo done to the input system to get this so wrong - I have other issues which I wonder if they are related, hmmm.

20

Just to add a little more - as you probably knew - the entire “right column” of options seems broken in SU9. I had added ’ for my ATC in the right column way back and in SU9 it worked 1 time in 20, if you were lucky (I had forgotten that SclLk was the “new” default for ATC). Put ’ in the left hand column for controls and now it works perfectly. I am not a troll (before everybody jumps down my throat) but come off it Asobo, aren’t you testing ANYTHING when you put this software out. Having things set in the right column of control options is hardly “edge case” testing… now I just need to figure out why the A32NX engines cut working on takeoff power then never work again, apart from in reverse!!!.. could be a FBW bug, but it started (well, stopped) on SU9 release, so I wonder who might have broken that???