Autopilot keeps disengaging NAV mode (VOR-to-VOR navigation)
-
@Black-Square
I did another two test flights today to see if I could discover some pattern.-
I took the standard Piper Dakota for a VOR-to-VOR flight at 6500 ft.
Empty Community and Community2024 folders.
No external programs running (no SPAD.neXt, TrackIR5, MSFS AutoFPS, Navigraph Charts, Little NavMap etc.).
All standard MSFS2024 hardware bindings and mouse control.
Observations: Autopilot NAV did NOT disengage during climb-out and cruise (1h30m). -
Second flight was with the Just Flight BAe146-100 on the same VOR-to-VOR route at 7500 ft.
Selected applicable and my usual "standard" Add-ons in Community and
Community2024 folders via Addons Manager.
External programs running: SPAD.neXt, TrackIR5, MSFS AutoFPS.
Observations: Autopilot V/L Mode did NOT disengage during climb-out, cruise and ILS approach (about 50 min).
Conclusion: standard aircraft (only one tested: Dakota) and some but not all third-party aircraft don't show this issue, while several third-party aircraft are affected. It seems to me that a relationship between the Commander 114 (amongst others) and the disengaging NAV mode can not be excluded.
This NOT an accusation that something is wrong with the aircraft. On the contrary, it might be the perfectionist and advanced design of the systems that proof to be too good or sensitive for what MSFS2024 can deliver. But I am convinced Nick has taken that into consideration. It just came up as a thought …...
BTW one advantage of doing so many test flights is that you get to learn and enjoy this wonderful gem of an aircraft. For me this is the best and most enjoyable single engine GA aircraft, though I must say the TBM850 comes very close.
@HansDeVlieger
I did tests some time ago with several aircraft. Here is a copy of what I found from the related MSFS forum entry:
Found the same problem with the following aircraft:BKSQ Caravan PMDG DC-6 NAMS YS-11 Default Beech King Air C90 GTxHowever I did NOT find the problem with the following aircraft:
Beech Baron G58 Beech King Air 350i Beech Bonanza G36 Saab 340 Cessna Citation CJ4 Cessna Caravan EX SWS Kodiak TBM 930I did all tests “Ready for take-off” from KSNA with 115.3 OCN Oceanside VOR, flying to and from the VOR in about 3-5000 ft.
-
-
@HansDeVlieger
I did tests some time ago with several aircraft. Here is a copy of what I found from the related MSFS forum entry:
Found the same problem with the following aircraft:BKSQ Caravan PMDG DC-6 NAMS YS-11 Default Beech King Air C90 GTxHowever I did NOT find the problem with the following aircraft:
Beech Baron G58 Beech King Air 350i Beech Bonanza G36 Saab 340 Cessna Citation CJ4 Cessna Caravan EX SWS Kodiak TBM 930I did all tests “Ready for take-off” from KSNA with 115.3 OCN Oceanside VOR, flying to and from the VOR in about 3-5000 ft.
@George-Curious Do you use FSUIPC, SPAD. neXt, MobiFlight or Axis-and-Ohs, just to try to zoom in? In any case, the issue doesn't seem to be related to any aircraft or developer in particular then.
-
@George-Curious Do you use FSUIPC, SPAD. neXt, MobiFlight or Axis-and-Ohs, just to try to zoom in? In any case, the issue doesn't seem to be related to any aircraft or developer in particular then.
@HansDeVlieger
I don't use any add-ons besides aircraft and sceneries. -
So, also those won't probably cause the issue.