I noticed I was having a problem where my Heading bug was jumping roughly 10 degrees with each push and couldn't figure it out. I also noticed something odd about the default bindings that the game shipped with. It included four bindings for Magnetos that were setup for buttons above 30 when the yoke only has 30 buttons. 

Then a poster in another thread mentioned that, during the beta, they had this issue and the fix, he thought, was to unbind those plus all the lights/beacons/strobes/taxi switches. Since I like using the latter I decided to just unbind (via Controls) just the odd magneto assignments. Once done the heading resolution bug was gone. 

i unbind-ed all the magneto assignments on the honeycomb yoke and it made no difference, I have logged this with Zendesk as a bug

Go out of the game and back in.

Delete assignments 31 - 34, this was posted in another thread.

Martin

20 minutes ago, MartinRex007 said:

Delete assignments 31 - 34, this was posted in another thread.

Martin

Didn't work tried that

Same thing here, I checked and only have until button 30 (strobe down) assigned and it is still bugged. Opened a ticked with Honeycomb.

deleting them assigments did not work for me either

hope this gets fixed soon

Same. Tried the remove magnetos thing. Didn't work for me either.

Removing the magneto bindings doesn't fix the problem in my case. I also find that the elevator trim repeat quickly becomes dangerously fast when the Honeycomb yoke is connected, whereas it's fine when I connect my Sidewinder joystick instead. Trimming and heading bug setting are also OK with the CH Eclipse yoke, though the yoke's trim wheel doesn't work, so I had to assign trim to two other buttons. Much as I love the visuals, I'm not prepared to accept the poor controller handling, and I also find the user interface unnecessarily obtrusive, so I'm giving up on FS2020 until they get it sorted out.

12 hours ago, Muklum said:

Removing the magneto bindings doesn't fix the problem in my case. I also find that the elevator trim repeat quickly becomes dangerously fast when the Honeycomb yoke is connected, whereas it's fine when I connect my Sidewinder joystick instead. Trimming and heading bug setting are also OK with the CH Eclipse yoke, though the yoke's trim wheel doesn't work, so I had to assign trim to two other buttons. Much as I love the visuals, I'm not prepared to accept the poor controller handling, and I also find the user interface unnecessarily obtrusive, so I'm giving up on FS2020 until they get it sorted out.

Don’t forget to ask for a refund. Im very happy I did. You can always use $1 gamepass until it comes out of the current alpha status.

12 hours ago, Muklum said:

Trimming and heading bug setting are also OK with the CH Eclipse yoke, though the yoke's trim wheel doesn't work, so I had to assign trim to two other buttons.

The trim wheel on the yoke is a mechanical control that simply moves the zero point of the elevator pitch. It is a crude and rather useless attempt from back in the days when the sim(s) didn't have separate elevator trim tab command events.

6 minutes ago, shadow133 said:

Don’t forget to ask for a refund. Im very happy I did. You can always use $1 gamepass until it comes out of the current alpha status.

That does not warrant a refund

This is a bug with any controller that uses an “on-on” toggle switch that has a command bound to that switch. It also happens if you just hold a controller button (again it has to be mapped to a command) down for the “on” state. 

Edited August 25, 20205 yr by snglecoil

1 minute ago, snglecoil said:

This is a bug with any controller that uses an “on-on” toggle switch that has a command bound to that switch. It also happens if you just hold a controller button (again it has to be mapped to a command) down for the “on” state. 

Command bound to what switch, I don't have anything bound on my honeycomb and still does it

4 minutes ago, Jetman67 said:

Command bound to what switch, I don't have anything bound on my honeycomb and still does it

On the Honeycomb specifically, it would be any of the toggle switches or any position on the magneto switch. If you are 100% sure that you don’t have any commands bound to any position of those switches (each toggle switch = 2 buttons, magneto has 4) then I don’t know what else would may be causing it for you specifically. Any other controller connected that may have a toggle type switch or a button the defaults to the “on” state when you look in the Windows 10 game controller setup utility?