Glitchy altitude setting

[Uber Deuce]

Disregard. As soon as I posted this it started doing it again. Crazy. I had flown for hours without a glitch. Sigh.



Brand new G1000 Suite owner here. Love it. I had a glitch when I would select an altitude on the AP. It would capture and hold the selected altitude no problem, but the altitude select filed would constantly change to a lower altitude.

I fixed it by creating a new (MSFS 2020), Bravo throttle quadrant) control profile specifically for the G1000 hardware. I then deleted all the Bravo autopilot bindings. Problem solved.

 

[Administrator]

Disregard. As soon as I posted this it started doing it again. Crazy. I had flown for hours without a glitch. Sigh.



Brand new G1000 Suite owner here. Love it. I had a glitch when I would select an altitude on the AP. It would capture and hold the selected altitude no problem, but the altitude select filed would constantly change to a lower altitude.

I fixed it by creating a new (MSFS 2020), Bravo throttle quadrant) control profile specifically for the G1000 hardware. I then deleted all the Bravo autopilot bindings. Problem solved.

Thank you for sharing!

 

[JimhCT]

Disregard. As soon as I posted this it started doing it again. Crazy. I had flown for hours without a glitch. Sigh.



Brand new G1000 Suite owner here. Love it. I had a glitch when I would select an altitude on the AP. It would capture and hold the selected altitude no problem, but the altitude select filed would constantly change to a lower altitude.

I fixed it by creating a new (MSFS 2020), Bravo throttle quadrant) control profile specifically for the G1000 hardware. I then deleted all the Bravo autopilot bindings. Problem solved.

I’ve had this same problem and at first it just happened a little and went away, but now the Altitude setting is all over the place and making it impossible to hold altitude. It slowly and then quickly increases or decreases the altitude by 1000s in different planes, and never happened before the hardware. This really needs investigation by Flightsimbuilder as it is almost unusable for me if this keeps happening. I’d even be happy with a workaround.

 

[JimhCT]

I’ve had this same problem and at first it just happened a little and went away, but now the Altitude setting is all over the place and making it impossible to hold altitude. It slowly and then quickly increases or decreases the altitude by 1000s in different planes, and never happened before the hardware. This really needs investigation by Flightsimbuilder as it is almost unusable for me if this keeps happening. I’d even be happy with a workaround.

Updated…Disconnected both G1000 units mid flight during problem and the problem has gone away. Noise from the hardware?

 

[JimhCT]

Updated…Disconnected both G1000 units mid flight during problem and the problem has gone away. Noise from the hardware?

Updated again: further troubleshooting. Connected, altitude change occurred. Disconnected usb for right…still happened. Disconnected left, still happened. Powered off right, still happened. Powered off left, stopped. It’s not coming from the input cables either.

 

[Administrator]

The problem is we can not replicate the issue and it's only a couple customers experiencing it and it looks like it's going away with MSFS update but then coming back. Do you have your ATC turned off in MSFS? Also to test the hardware, can you open windows joystick controller and check ALT is showing there and then while you are in flight make sure the hardware is not sending any signals to eliminate any unlikely hardware issues?

 

[JimhCT]

The problem is we can not replicate the issue and it's only a couple customers experiencing it and it looks like it's going away with MSFS update but then coming back. Do you have your ATC turned off in MSFS? Also to test the hardware, can you open windows joystick controller and check ALT is showing there and then while you are in flight make sure the hardware is not sending any signals to eliminate any unlikely hardware issues?

I’ll check those tomorrow. Possibly tied to Say intentions? I’m using that as well (though disconnected it and it didn’t help).

 

[Administrator]

It's most likely either due to either ATC (it would be great if you can try without Say Intensions and see if it fixes it), autopilot bug (try turning it off and see if the ALT keep changing or not), or launcher/hardware issue (we tried to recreate it and sine it's only a couple users affected, it's unlikely but still possible, you can check it with the joystick input monitoring).

 

[JimhCT]

The problem is we can not replicate the issue and it's only a couple customers experiencing it and it looks like it's going away with MSFS update but then coming back. Do you have your ATC turned off in MSFS? Also to test the hardware, can you open windows joystick controller and check ALT is showing there and then while you are in flight make sure the hardware is not sending any signals to eliminate any unlikely hardware issues?

Check photo. What I did notice is that while turning the alt 1000 knob the lights for the highlighted three buttons lightly lit up

 

[JimhCT]

Check photo. What I did notice is that while turning the alt 1000 knob the lights for the highlighted three buttons lightly lit up

It’s not SI and I checked all autopilot settings in the honeycombs and turned them off.

 

[Administrator]

What about when the altitude changes by itself? Do you see any input in windows joystick controller?

 

[JimhCT]

What about when the altitude changes by itself? Do you see any input in windows joystick controller?

If you want me to troubleshoot for you you’ve got to give me detailed directions.

 

[Administrator]

To rule out any hardware issues, open the Windows joystick controller and check if any buttons light up without being pressed when you're experiencing the altitude fluctuation issue. It's an unlikely possibility, but once we eliminate it, we can focus on other add-ons or potential MSFS bugs.

 

[Administrator]

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.
2. Remove Incorrect VS Key Bindings
   
   • 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.
3. Validate and Test
   
   • After updating bindings, test the Bravo in a flight. Switching between selector positions should not change the autopilot mode unless you press the corresponding button4.
   • Adjusting altitude should only change the preselected value, not trigger a climb or descent unless commanded.
4. Check for Conflicts
   
   • If you use multiple Honeycomb devices, check for overlapping assignments or conflicts, especially if you see other strange behaviors (like heading increments changing by 10 instead of 1)2.

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.

 

[JimhCT]

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.

So I’m sorry to report this didn’t fix it. I created a new profile from blank, assigned only the throttles and flaps, and the problem recurred, though I will admit less than previous, but I’m also using a different plane (SR22 vs C700). I searched literally every control for VS and ALT and took off any bindings. It seemed to happen more when I used the PFD vs the MFD, but that could be coincidence. Using the MFD to change ALT it crept up only 1 or 2K but did settle and I was able to land without incident, but bottom line still happened. Also checked and no other buttons lit up in properties.

 

[Administrator]

Did you try disconnecting the Bravo to see if it fixes the issue?

 

[JimhCT]

Update: flying the Longitude it started again so I pulled the power from both pfd and mfd and the interesting thing is it stopped, but the knobs and buttons still worked, so it’s related to video for some reason. Changed alt/hdg using main screen video and no problems. Will retest today.

It never happens with the bravo alone. Only the g1000 connected.

 

[Administrator]

Disconnecting the power can not impact this issue, as the power is only used for the LCD display.

The reason you may not have noticed this before connecting the G1000 is likely because you weren't using or monitoring the ALT function previously.

All available sources indicate that this is a known issue with the Bravo profiles. It would be helpful to test with a different controller or without a throttle to help isolate the problem and focus on finding a solution.

Let me know how it goes!

 

[JimhCT]

Disconnecting the power can not impact this issue, as the power is only used for the LCD display.

The reason you may not have noticed this before connecting the G1000 is likely because you weren't using or monitoring the ALT function previously.

All available sources indicate that this is a known issue with the Bravo profiles. It would be helpful to test with a different controller or without a throttle to help isolate the problem and focus on finding a solution.

Let me know how it goes!

Look, I get you don’t want it to be true, but saying it cannot be is not going to get you to a solution. You are selling an expensive product that has to interface with an MS product, so while I get it’s a challenge, I am not and will not be the only person having this problem with my vanilla build on a Alienware PC dedicated to MSFS. I just finished my second long flight.
1. This does not happen without the g1000’s on
2. In both long flights the altitude starting resetting after takeoff
3. Unplugging the power to both g1000s IMMEDIATELY stopped the altitude drift
4. I was able to continue to use both to change altitude, HDG, etc with zero repeat of the issue for 3 hours.

While it may be an incompatibility with the honeycomb, the fact remains I have followed the honeycomb fix, there are only 5 bindings on it in these last two flights, and the problem only occurred when the g1000s were powered on.

I would suggest you think about why having those extra screens on would cause the problem. I’m traveling for a week and will not be able to fly for a bit, but do not offload this problem onto me…it is your product, for which I spent a lot of money, and while I’m sympathetic I could go with a return of the product route and file a complaint with Chase Sapphire, who will absolutely take my side. I am instead trying to work WITH you and doing your troubleshooting. If you work against me, that position will change.

 

[Administrator]

Thanks for sharing all those details and for sticking with the troubleshooting process. From the product design, the power LCD can not impact anything in the simulator as it's only powering LCD and LCD and buttons / knobs are not connected.

Also all of the folks we know with this issue (only a few) have fixed it using the Bravo solution.

We’re happy to keep helping out, but based on what you’ve described, it looks like the problem is probably with the Bravo unit or MSFS-both of which are a bit outside what we can directly support. Still, we’re doing our best to help with what we know and what other users have shared.

If you notice anything new or have more questions, just let us know. We appreciate your patience and want to help you get this sorted!