Glitchy altitude setting

[Administrator]

As always, you can always submit the unit for inspection so our engineer can verify and even though unlikely but make sure there is no issues with the hardware. To arrange the inspection, please contact [email protected]

 

[Uber Deuce]

Hi, after some research on your issue, it looks like there is an issue with Honeycomb Bravo where many users reported this issue. It's also consistent with the original post in the thread where the user was able to resolve this issue with this fix.

Honeycomb Bravo Causing Random Altitude Changes: Causes and Solutions
Overview

Many users of the Honeycomb Bravo Throttle Quadrant have reported issues where adjusting autopilot controls-especially altitude-results in unexpected or random altitude changes in Microsoft Flight Simulator (MSFS). This is a well-documented problem and is typically related to control profile bugs or conflicting key bindings rather than a hardware fault.

Common Causes

• Default Profile Bugs: The default Honeycomb Bravo profile in MSFS has known issues, particularly with the autopilot VS (Vertical Speed) and ALT (Altitude) selector knobs. These bugs can cause the autopilot to disengage or change modes unexpectedly when switching between selector positions or adjusting values14.
• Improper Key Bindings: The VS selector knob is often incorrectly bound to both select and activate the VS mode, which can inadvertently disengage altitude hold or other autopilot modes when the knob is turned4.
• Profile Inheritance: Even if you create a custom profile, if it was forked from the default (buggy) profile without correcting the bindings, the issue can persist1.
• Control Conflicts: Sometimes, using multiple Honeycomb devices (e.g., Alpha Yoke and Bravo Throttle together) or having overlapping assignments can introduce further conflicts, though this is more commonly associated with heading increments than altitude23.

Symptoms

• Adjusting the altitude knob causes the aircraft to start descending or climbing without user input14.
• Switching the selector knob from one mode (e.g., ALT) to another (e.g., VS or HDG) can deactivate altitude hold or change the autopilot mode14.
• The altitude selector only adjusts in large increments (e.g., thousands of feet) or behaves inconsistently3.
• Adjusting airspeed or another value also changes the altitude setting, indicating a binding conflict5.

How to Fix

1. Check and Update Your Control Profile
   
   • Go to the MSFS Controls menu and select the Honeycomb Bravo device.
   • Do not rely on the default profile. Create a new profile or thoroughly review all bindings if you forked from the default14.
   • The VS selector on the left knob should only select the mode, not activate or deactivate it.
   • Remove any binding such as "Set Autopilot VS Hold" from the VS knob position4.
   • The correct approach is: use the knob to select the mode (ALT, VS, HDG, etc.), then use the associated button to activate/deactivate the function4.

Summary Table: Issue and Solution

Symptom​	Likely Cause​	Solution​
Random altitude changes when using Bravo knobs	Default profile bug	Create/fix custom profile, remove bad bindings14
Altitude selector changes mode unexpectedly	Improper VS key binding	Remove "Set Autopilot VS Hold" from VS knob4
Adjusting one value changes another (e.g., airspeed changes altitude)	Binding conflict	Review and separate all bindings5

Conclusion

The random altitude changes with the Honeycomb Bravo in MSFS are almost always due to software configuration issues-specifically, bugs or conflicts in the default or inherited control profiles. Carefully reviewing and correcting the autopilot mode selector bindings, especially for the VS and ALT positions, resolves the problem for most users14.

OP here. Please note that I edited my post about fixing it. I edited the post to say to disregard my post as the problem returned.

 

[Administrator]

OP here. Please note that I edited my post about fixing it. I edited the post to say to disregard my post as the problem returned.

Are you still using it with Honeycomb Bravo? Did you try it in another sim like X-Plane? You can also always send a G1000 to us to test to make sure there is no issues with the hardware (email request to [email protected]) but based on your details it's very unlikely.

 

[Uber Deuce]

As I wrote in another thread, I haven't been able pop out the windows in MSFS 2020 or 2024 so the hardware has been sitting on the floor unused, but the last time they worked the altitude glitch was still present.

I just bought X-plane 12 and I wonder is the G1000 suite plug and play with X-plane 12? I can't find any X-plane instructions on your website. I'd like to try it with that sim.

Yes I'm still using the Bravo.

 

[Administrator]

If you can't pop out windows in MSFS, it's a known MSFS bug and you can try this https://flightsimbuilder.com/pages/flight-simulator-bugs-known-issues-page but given all of the issues you've been having with MSFS, I would do a clean install https://flightsimulator.zendesk.com...6108-How-to-clean-install-the-simulator-on-PC

For instructions, you can find them here https://flightsimbuilder.com/pages/flightsimbuilder-instructions

 

[Uber Deuce]

I've done a full MSFS 2020 re-install already. I'll let you know if it works. Do I need the launcher for x-plane? There are no instructions that I can find for X-plane.

 

[Administrator]

https://flightsimbuilder.com/pages/flightsimbuilder-g1000-instructions It's under IV. X-Plane