TCA Throttle Issue, only 75% of axis recognized (as well as input curve page not showing motion)

User Support Hub Hardware & Peripherals
,
21

This should be bug report imho. Throttle quadrants not working properly is a huge deal in flight simulator.

3 Likes
22

Yesterday my controler configuration worked (the default one on the Flight Stick X), but today the throttle stays halfway and the engine stops when I accelerate.
SOLVED

I reinstalled the drivers and now it works again
I think everything got misconfigured because I had another device connected that created some kind of conflict and changed the mapping

1 Like
23

By default, the TCA throttles are mapped to “Throttle 1/2 Axis (0 - 100%)” - changing the mapping to just “Throttle 1/2 Axis” fixed the problem for me. You then have to configure the detents on the ipad in the plane itself.

2 Likes
24

I found out that the Throttle problem occured on any plane from the basegame. I opened one of my previous purchased planes from 2020 and it worked like intentional. I think its a bug from the new plane models rather than the game itself.

1 Like
25

I’m having a similar issue. I think I’ve given up why couldn’t they import all the setting from msfs2020 into this using same account. I’m literally about to just say f it.

26

Got the solution ironed out in actionable terms. The problem, as mm0070 said earlier, is the axis defaults to only positive axis (+) and not the entire axis (Axis -, Axis +). The Cessna 172 appears to not be affected by it for me. So far, it appears to reset with each new aircraft. My working solution is as follows:

  1. Map the axis as you would normally on the “THROTTLE 1 AXIS”, or whichever axis you are attempting to map.
  2. To the right of this map function will be a gear icon, click on it.
  3. In the left column of the next window will be a list of inputs, which are enumerated according to what your throttle has. Scroll down and look for the axis that is mapped (enabled). This will most likely be something like “JOYSTICK LAXIS Y+”.
  4. The next part is not repeatable after it has been committed for the current aircraft. This in itself shows that it is a BUG we are dealing with. Given the example above, enable “JOYSTICK LAXIS Y”, “JOYSTICK LAXIS Y+”, and “JOYSTICK LAXIS Y-”.
  5. Return to the aircraft and verify full throttle travel according to your hardware input. You may need to invert the axis.
  6. Go back to the settings (gear icon to the right of the map function) of the input and disable the “+” and “-” inputs in the left column. The throttle range should persist to the full actuation on your hardware. Unmapping this and adding it back with none of the steps listed above seems to work as it should have originally–more evidence this is a bug and not some wacky input syntax Asobo created.
2 Likes