Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]MSFS2020 FBW A32NX autopilot/FCU gets stuck in "managed mode" #292

Open
Samh189 opened this issue Jan 14, 2025 · 1 comment
Open

[BUG]MSFS2020 FBW A32NX autopilot/FCU gets stuck in "managed mode" #292

Samh189 opened this issue Jan 14, 2025 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@Samh189
Copy link

Samh189 commented Jan 14, 2025

When using the FBW A32NX the FCU panel in shared cockpit seems to have a complete breakdown. Most important and prominently seems to be that the FCU locks in managed mode, it's near impossible to get the autopilot function back to normal; most consistently this appears to happen after the initial climb is completed.

Currently using the DEV version 007db04.

To Reproduce

  1. Load up MSFS2020, load the FBW A32NX cold & dark at an airport stand or apron of choice.
  2. start server; being host or client doesn't seem to change anything.
  3. verify connection by performing startup tasks, prepare the airplane for flight. Ensure a flightplan of choice including departure and arrival procedure are programmed in the FMGC. Make sure all INIT data is also set.
  4. start performing flight of choice, when at cruise altitude try getting the AP speed or heading out of managed mode.

Expected behavior
FCU (SPEED, HDG, ALTITUDE) should be able to be switched between managed and unmanaged as required.

Additional context
From log snippet below, it does seem to sync the correct data, but for some reason it creates a conflict I suppose. Unfortunately I don't have the log from the other side available right now. Potentially the status isn't communicated, i.e. the "pull" or "push" function.

edit: I have a vague suspicion that these changes are the root of the issue. I think A32NX_AUTOPILOT_HEADING_SELECTED has some issue and the push/pull will have to be changed as per A32NX Flight Deck API below.
I suspect the same steps will have to be taken for the altitude and speed part.
image

PLEASE ATTACH EVERYONE'S LOGS
21:59:35 [INFO] [PACKET] AllNeedSync { avars: {}, lvars: {"L:A32NX_AUTOPILOT_HEADING_SELECTED": F64(270.0), "L:A32NX_FCU_HDG_MANAGED_DASHES": F64(0.0)}, events: [] } Dellhound false true true -snip- 21:59:39 [INFO] [PACKET] AllNeedSync { avars: {}, lvars: {"L:A32NX_AUTOPILOT_HEADING_SELECTED": F64(251.0)}, events: [] } Dellhound false true true 21:59:40 [INFO] [PACKET] AllNeedSync { avars: {}, lvars: {"L:A32NX_AUTOPILOT_HEADING_SELECTED": F64(250.0)}, events: [] } Dellhound false true true 21:59:56 [INFO] [PACKET] AllNeedSync { avars: {}, lvars: {"L:A32NX_AUTOPILOT_1_ACTIVE": F64(1.0)}, events: [] } Dellhound false true true

Discord
N/A

@Samh189 Samh189 added the bug Something isn't working label Jan 14, 2025
@Samh189 Samh189 changed the title [BUG]MSFS2020 FBW A32NX autopilot/FCU gets stuck in " [BUG]MSFS2020 FBW A32NX autopilot/FCU gets stuck in "managed mode" Jan 14, 2025
@rthom91
Copy link
Collaborator

rthom91 commented Jan 16, 2025

Dev version is not supported. Please verify this same behavior with 12.3 stable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants