Asobo 737 MAX Autopilot Altitude Control Binding

ISSUE DESCRIPTION

Description of the issue:

The control key bind for “[INCREASE/DECREASE] AUTOPILOT REFERENCE ALTITUDE” does not affect the autopilot reference altitude on the Asobo 737 MAX 8 Mode Control Panel (MCP) or the magenta value on the Primary Flight Display (PFD).

If applicable, which aircraft is experiencing this issue:

Asobo 737 MAX 8 (both VIP and Passenger variants)

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?

Yes and yes.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

Every flight with the Asobo 737 MAX 8.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Start a flight in Free Flight with the Asobo 737 MAX 8
  2. Bind any two (2) keys to “INCREASE AUTOPILOT REFERENCE ALTITUDE” and “DECREASE AUTOPILOT REFERENCE ALTITUDE” respectively
  3. Use those keys
  4. Observe no change to the autopilot reference altitude on either the MCP nor the PFD.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

Standard USB keyboard

[PC Only] Are you using Developer Mode or have you made any changes to it?

No

[PC Only] What GPU (Graphics Card) do you use?

Radeon RX 7900 GRE

[PC Only] What other relevant PC specs can you share?

n/a

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

1 Like

So it appears that some controls for the Asobo 737 MAX 8 MCP are specific controls for the aircraft, even if they are universal functions (like altitude selection) - I was able to bind my usual controls for altitude selection increase/decrease to the following and it does work.

image

4 Likes

Moved to USH since a solution has been marked

2 Likes

Thanks for posting this binding, very helpful. Added it just now.

1 Like

Boeing 737 Max.

Bravo Honeycomb cannot change the altitude in cockpit although it can change all other variables (i.e.Speed, etc). I can only change the altitude with the mouse hovering on the Alt button in the dash.

MSFS 2024 version 1.4.12.0
i9-14900K, RTX4090. No Mods/add-ons.

Hi @guerbou ,

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

i @guerbou ,

Asobo 737 MAX Autopilot Altitude Control Binding - User Support Hub / Aircraft & Systems - Microsoft Flight Simulator Forums

ISSUE DESCRIPTION

Description of the issue:
Bravo Honeycomb Quadrant Altitude change is not working

If applicable, which aircraft is experiencing this issue: Boeing 737 Max.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue? No Mods/add-ons.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
All the time.

REPRODUCTION STEPS

Bravo Honeycomb Quadrant is correctly map to SELECT ‘ALTITUDE’ BUG but does not respond to the INCR DECR selector that is mapped to MINUS and PLUS and cannot change the altitude.

Note that all the SELECT ‘HEADING’, ‘VSI’, ‘AIRSPEED’, ‘VOR’ BUGs are working with MINUS and PLUS selector.

The altitude can be change with the ‘mouse’ over the Alt button in the dash or with ‘keys’ of the KEYBOARD mapped to ALT SEL DECREASE and ALT SEL INCREASE.

YOUR SETTINGS

What peripherals are you using, if relevant: Honeycomb Bravo Quadrant
[PC Only] Are you using Developer Mode or have you made any changes to it? No.
[PC, MSFS 2020 Only] Are you using DX11 or DX12? DX12
[PC Only] What GPU (Graphics Card) do you use? RTX4090
[PC Only] What other relevant PC specs can you share? i9-14900K, RAM 64

2 Likes

The solution has already been linked above.

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:
• After engaging the autopilot on the 737Max, the autopilot disconnects and the plane roll to the left and goes nose down . This has happened a few times now. Or after taking off an airport after engaging the autopilot, the plane fails to follow the route .
Thank you.
Pedro

If relevant, provide additional screenshots/video:

I don’t think this is related to the altitude hold value control binding.

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:
• I have exactly the same issue. I am using the AXAIR MIAP Pro 24. Reference Altitude works perfectly for all other aircraft (that I have tried) except the 737 Max.

The issue has been resolved - please scroll back through the post to find the correct binding that will work.

(MSFS 2024) Honeycomb Bravo

737 max and 787 have aircraft specific altitude adjustment settings.
USE: Alt Sel Decrease and Alt Sel Increase are the two to bind. It’s WORK.

The posted fix is not correct it has nothing to do with the actual problem of the Bravo not working. All the other options work… vs, hdg, crs, ias. Its only the alt that does not work

2 Likes

The altitude keybind does work if you use the correct one - the standard one under the “Aircraft” controls category does not work for the Asobo 737 MAX whether you’re using a Honeycomb Bravo or a standard USB keyboard (or any other input device). You must use the ALT SEL INCREASE/DECREASE keybinds found under the “Specific” category of controls, as shown here:

image

Appreciate you taking the time to reply… YES, working now. Thanks.

1 Like

While this solution fixes keyboard bindings, it does not apply to the Honeycomb Bravo throttle.

By default, the adjustment knob on the right of the Bravo sends the PLUS and MINUS commands to the item selected on the selector knob to the left of the Bravo.

In the case of the Altitude setting, it fires off the SELECT ALTITUDE BUG setting when ALT is chosen, and then PLUS/MINUS will adjust the bug. Same with SELECT HEADING BUG when HDG is selected, etc, etc.

The 737 Max does not appear to have a corresponding setting to SELECT ALTITUDE BUG, and you cannot simply change what commands the adjustment knob sends because that would break it for VS, HDG, CRS, and IAS, which all still rely on PLUS/MINUS. You also can’t just double map the new altitude increase/decrease command because they would just change your set altitude every time you changed anything else.

So for anyone looking for a solution to the altitude selector being broken for the 737 on the Bravo, this is not it.

1 Like

Can confirm that this is still a bug with the Asobo 737 Max and the Honeycomb Bravo. This is the only plane in the default lineup which cannot have the altitude selected with a Honeycomb Bravo. Its lovely that some people can work around it, but this can be fixed and it should be fixed. This has NOT been solved.

DarthFinibilis above has the exact reason why…