NONE of my Airbuses follow NAV , but ALL other ACFT do !?

User Support Hub Aircraft & Systems
, ,
1

Hi guys

My problem relates to both MSFS 2020 / 2024 on my system, so it seems it’s something on my system that’s causing this. NONE of my Airbuses follow NAV mode, BUT all other aircraft ( Boeings etc) do. If I press DIR TO … my airbuses go into the circle around T-P , and never intercept the desired track - even if I “bring” them in HDG mode to cross the NAV line on ND. Boeings and all other ACFT behave correctly - they start tracking and eventually intercept and follow the FPL.
I’m quite familiar with both types and the procedures as well - it seems there’s something weird that has changed on my system and that is causing my problems. so I would like to hear your wildest ideas/solutions to the above mentioned. If any of you had a similar problem - be it some MOD or anything else, I’m open for all your suggestions.
What is it so specific on both SIM versions related to Airbuses that’s causing this weird behaviour??
(I’m on WIN 10 having 64 GB of RAM , 13th Gen Intel(R) Core™ i9-13980HX)

Thanks in advance.

Dc9

2

Most likely you are not in the right mode. Airbus has two ‘AP’ modes, Managed and Selected and they operate rather differently.

3

Falcon, thank you for your reply. I’m in the correct mode … White dot in HDG window. As mentioned I tried with DIR function and “leading” ACFT into the FPL track in HDG mode and few miles before interception engaging MANAGED mode … but the ACFT just flies thru the FPL track … As mentioned earlier , all other ACFT behave normally and as expected …

My first tests gave some positive results - If I remove “pms50-instrument-gtn750” folder (it’s the GTN750 addon I own) airbuses start to behave normally…?? Further testings needed what could be the culprit of it …

Thanx for your input though …

4

Dont ever use the 750 on a commercial airliner it totally messes with the FMC a few years ago i had issues with i think it was the airbus not intercepting and following approaches turned out it was the 750 taking over ( it would actually work if i activated the approach on the 750, so if you need the 750 try “direct to” on that and make sure its in gps mode) once i stopped opening the 750 during a flight it worked correctly

5

Great and thanks for the tip… :grinning: :beers:

6

Your GTN 750 version must be hopelessly outdated. I have the current version installed in 2020 and 2024 and all my Airbuses follow NAV mode perfectly.
Updating your version should solve your problem.

7

Actually I have the latest ver. 2.2.46 installed on both SIMs. Since It works fine on your system, obviously something else (or combination of acft / files) is clashing with my “buses”.
Thanx for your input. :beers:

8

Do your Airbuses behave correctly with a completely empty community folder?

Do the FBW Airbuses behave differently from the inibuild Airbuses?

9

I will start doing these tests with my MSFS2024, because it’s closer to it’s vanilla state and will report back. :+1:

10

My findings:
MSFS2024 It was my fault, because I was starting my MSFS with Beach Baron and then I changed aircraft within “Developer” mode(I know that’s big no-no) - loading aircraft in such manner NONE of my Airbuses (Inibuild, FBW,Asobo…) were able to intercept and follow NAV flight path (in managed mode), although strangely enough all other types e.g. Boeings etc worked normally even when I sometimes even loaded them mid-air :face_with_spiral_eyes::grin:

MSFS2020 : It was as well my fault in how I started my flights, by always starting/loading my Beach Baron which has PMS GTN750 INTEGRATED into it’s cockpit. Then I would load another aircraft (eg. Airbus) and started flying. None of the Airbuses were able to intercept and follow NAV path from the FPL by starting flights this way. (Curious enough though ALL other types worked without such problems. I’m still curious in what way FSim treats airbus types diferently to cause such problems, while ALL other types were unaffected).:thinking:

While making these tests I came across this 2 tips bellow, which I applied to enhance stability of autopilot performance:

  1. Increase/set dead zone on joystick to 7-10% 2. In Windows REGION settings / Administrative Tab - ENABLE : BETA: USE UNICODE UTF-8 FOR WORLD WIDE LANGUAGE SUPPORT ( I guess this might be more relevant for Folks from the non-native English regions, such as myself)

Hope these findings might be useful to some folks… :+1::airplane::clinking_glasses:

Thanks again to all those who tried to help. :beers::+1::innocent:

Dc9