[Solved] X56 input suddenly activates reverse thrust causing throttle suddenly refuses to be increased - plane stalls

SOLVED

ISSUE DESCRIPTION

Description of the issue:
Problem with the reverse thrust toogle: it fired without being pressed!

Sometimes the thottle suddenly refused to be increased. it doesn’t change at all. See video. Either there are invalid conditions in thrust mangement coded or it is an input problem.

if this caused by the player failing to respect the conditions of the aircraft over time, it would be important to get a response to that at the crash, or at least at mission fail screen.

If applicable, which aircraft is experiencing this issue:
Cessna C408 Skycourier, PC12, PC24, and other. (see 1st video)
Cessna 208B: detected sudden increase of thrust causing engine failure (see 2nd video at 1:30)

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
have none

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Very often with medium to large aircraft, like PC-12, PC-24.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Pick a mission and fly
  2. Use Autopilot and AT
  3. Skip to Landing, and turn off AT before
  4. Make a landing aproach. Try to use some flaps, low speed, low landing angle.
  5. Sometimes the problem occurs.

YOUR SETTINGS

What peripherals are you using, if relevant:
Thrustmaster X56 Stick and Thrust

[PC Only] Are you using Developer Mode or have you made any changes to it?
no

MEDIA

C408: (Bug - Invalid Conditions in Thrust Mangement Coded)
208B: (Cesna 208B sudden engine failure)

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Same Problem here. How did you solve the problem

Hello Heinz,
i have plugged it directly into an USB port of my computer, instead using an USB Hub between. As workaround I also removed all settings from throttle buttons that influence engine and brakes.

I even use two active USB hubs because I run a large rig. I use a P6R from DOF-Reality and depend on the USB hubs. Everything works fine in MSFS 2020. Great work Asobo, thanks for the expensive beta test

It is hardware problem of the throttle regarding stability of USB signals. No chance for Asobo to really fix that. A solution might be to code a threshold to ignore fluctuations, but at the current state of the game i see no chance for this to happen.

Another solution might be to try to use active USB hubs instead of passive.


(Source: Pixabay)

I already mentioned that these are active USB hubs. I’m not an IT expert, but it doesn’t make sense to me that it works with the 2020 and not the 2024. As a layman, I would conclude that it’s a problem with the program code. Apparently, many users have the problem. It is often described differently, but always occurs in connection with the 208b and the autopilot.