ATR In-Game Throttle Only Follows IRL Throttle Position

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No.

Have you disabled/removed all your mods and addons?

Yes.

Brief description of the issue:

In-game throttle input is only affected by the IRL throttle position. Calibration, gust lock and flight idle lock has no effect.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

On ground - engines running; engage gust lock and move throttles forward, observe torque.
In flight - idle gate in flight idle; move the throttles to flt idle position (not all the way back) and observe torque. Then reduce IRL throttle all the way backwards and observe torque.
Calibration page;
Add full detent tolerance (idle, notch, ramp), validate and observe effects while moving throttles.
Set idle, notch and ramp detents at wacky places, validate and observe effects while moving throttles.

PC specs and/or peripheral set up if relevant:

VKB Gladiator NXT EVO with OMNI adapter as throttle.

Build Version # when you first started experiencing this issue:

World Update 13 (1.32.7.0).


: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:

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

Similar

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

Thrustmaster TWCS throttle here. EFB calibration seems to have no effect. Throttle will not pull all the way back to idle. Nearly impossible to move to Notch position. When approaching Notch, it jumps past it. Reverser does not work with my normal reverser push button which works for the other turboprop airplanes. And cannot set up throttle in Axis and Ohs. The axis is not recognized as a throttle. Verified no conflicting control assignments on throttle axis.

If relevant, provide additional screenshots/video:

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

YES

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

I have tried setting up controls with both the default controls set up in MSFS and with a paid version of FSUIPC7 and get same results. For throttles, Idle detent always seems to have my throttles stop at the top of the green line. I can only get the throttles to go down into the green arc, to FI or GI with i push and hold F2. As soon as I release F2, the throttles pop back up to the top of the green line. Furthermore, with the condition levers, Prop Axis 2 works perfect, with Prop Axis 1, I am unable to get the lever to go below idle. This aircraft right now has been rendered unable to fly because I cannot control my power management.

If relevant, provide additional screenshots/video:

I was able to fix the issue for me. I had FSUIPC7 running. It seems that it’s calibration system does not play nicely with the ATR. I haven’t had any issues with any other 3rd or 1st person add ons until this one. I disconnected FSUIPC, and then set up my controls for a custom profile in the default control set up and made an ATR profile. Everything works great now. I just wish that the default control systems for MSFS would link the controls the plane you are flying and change the profiles automatically like FSUIPC7 does. I hate having to jump back and forth all the time.

I thought it might be an FSUIPC issue but because I need it for other things, disabling it just for this plane wasn’t acceptable for me.

I don’t even know how anyone thinks it’s appropriate to release an addon that conflicts with FSUIPC, since like 20 years. It’s such a crucial part of MSFS.

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

YES

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

I DONT USE FSUIPC AND STILL HAVE THE SAME ISSUE. Honeycomb bravo here.

If relevant, provide additional screenshots/video:

It could be an issue with how I set up FSUIPC and a conflict between FSUIPC and the key bindings in MSFS2020. With FSX, it had a control option to disable all FSX default controls so that FSUIPC worked alone. With MSFS2020, I always seem to one issue or another configuring a plane with FSUIPC. With the flybywire A320, it was something with the throttles (could have been my mistake calibrating wrong though.) With the PMDG 737, I cannot get the parking breaks to release if I use FSUIPC to set the controls for the brakes.

Well I don’t know about the others, but the PMDG parking brake issue I had too until I realized that I just need to push real hard on the pedals.

Verified fixed in v1.0.9