It’s an Asobo bug caused by any hardware that has switches that stay permenatly on.
The bug has been in MS flight sims for years.
You can avoid the bug by using various 3rd party software solutions
I recognise that if it was any easy problem to fix they would have done it by now! Remeber this has been around for years so I decided instead of complaining I’ll just start fixing (or more to the point avoiding) the problem.
So I decided to use the free vJoy/Gremlin soution with my Alpha and Bravo. It takes some time to set up but once done you won’t look back. I’ve been succefully using it for 3 months now
Here’s my Solution to Avoid the Bug
This just shows the basic solution to get you started flying a Complex engine GA aircraft with Throttle, Prop and Mixture controls. Once you have this successfully working you will be able to see what I’ve done to setup Bravo profile and you will then be able to configer the throttles for other types of GA engines.
If the bug is still there it means you still have an “always on” switch maped on your alpha or bravo profile. Use these instructions to find that offending switch
If you still have the bug than it’s likely you incorrectly created a Gremlin macro ; usually it’s forgetting to assign a “released” action
By using gremlims input viewer you can find the incorretly created macro by switching/rotating every switch and dial one at a time on your Alpha and Bravo to see if any of the vJoy buttons permenantly stay on (red)
So spend a few hours implimenting one of the many workarounds people found and then you can 100% enjoy the full functionality of the Alpa and Bravo with FS2020
To be honest even if Asbo do fix the problem I’ll still continue to use my vJoy/Gremlin solution because I have made some quite complex macros using Gremlins Condition function (“if this than do that”) to further extend the functionality of my Alpha & Bravo