When I calibrated my throttle hardware in the A220, using AXIS+BUTTON, I found that it requires the TOGGLE or HOLD REVERSE THRUST input to be assigned to a button. Every other MSFS aircraft I have (third party or default) allows F2 to enable reverse thrust by moving the lever input into the reverse range. This is a default behaviour in MSFS. F2 will decrease A220 throttle lever position in the forward range, but not in the reverse range. Can this method be enabled for the A220?

I can add the required binding as a specific A220 input and use reverse thrust that way, but I find advancing the throttle to increase reverse thrust is counter intuitive.

Kevin

1 hour ago, kevinh said:

When I calibrated my throttle hardware in the A220, using AXIS+BUTTON, I found that it requires the TOGGLE or HOLD REVERSE THRUST input to be assigned to a button. Every other MSFS aircraft I have (third party or default) allows F2 to enable reverse thrust by moving the lever input into the reverse range. This is a default behaviour in MSFS. F2 will decrease A220 throttle lever position in the forward range, but not in the reverse range. Can this method be enabled for the A220?

I can add the required binding as a specific A220 input and use reverse thrust that way, but I find advancing the throttle to increase reverse thrust is counter intuitive.

Kevin

Hi Kevin,

I’d kindly ask that you post this feature request over on the official Synaptic Discord. The team there will have a better understanding of why the system behaves the way it does and can provide further insight.

Thanks!

Just now, iniKyle said:

Hi Kevin,

I’d kindly ask that you post this feature request over on the official Synaptic Discord. The team there will have a better understanding of why the system behaves the way it does and can provide further insight.

Thanks!

Thanks Kyle, I'll do that. I wondered what the Synaptic support channel was.

Kevin

On 9/1/2026 at 7:04 PM, iniKyle said:

Hi Kevin,

I’d kindly ask that you post this feature request over on the official Synaptic Discord. The team there will have a better understanding of why the system behaves the way it does and can provide further insight.

Thanks!

Another issue that many people on Discord have complained about and that has never been resolved since the first update.

13 hours ago, GustavoAguiar said:

Another issue that many people on Discord have complained about and that has never been resolved since the first update.

Yes, I saw all that. I posted it as a suggestion and after explaining why people want it they said they would look at adding a calibration method for an axis without reverse range. No promises.

Someone on Discord posted a workaround which does do the trick, but you need to make a new axis calibration for it. Essentially so that idle on your throttle input comes at 0, not -1.

Kevin