Autopilot will not intercept the purple line in NAV mode

Bug Reporting Hub Aircraft & Systems
, ,
1

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue:
If I turn on the Autopilot whilst not on the planned track (the purple line) and I then engage NAV mode the autopilot does not attempt to fly to the planned track. If I use HDG mode to steer towards the planned track with NAV mode on, it also does not intercept the planned track. This is something I did regularly in MSFS2020 so I am confident I am operating the autopilot correctly.

If applicable, which aircraft is experiencing this issue:
Bonanza G36, Cessna 172 G1000

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

FREQUENCY OF ISSUE

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

REPRODUCTION STEPS

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

  1. Plan a simple VFR flight
    2.Take off and fly away from the planned track
  2. Enable the Autopilot, setting NAV
  3. Steer the plan towards the planned track using HDG mode
  4. Observe that the plane does not intercept and just flies on at the set heading

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:
X.56 HOTAS

[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?

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

[PC Only] What other relevant PC specs can you share?
i9-10900K, 32GB RAM, 1TB m2 SSD, Windows 11

MEDIA

Please add a screenshot or video of the issue occurring.

[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:
•

2

I have had it work several times with the C172 but then other times it does not. Can’t seem to get it to follow the magenta line consistently. Sometimes it has flown right past the magenta line (Nav1 selected GPS indicated in G1000) and once or twice has changed direction and headed off on its own path to somewhere.

In 2020 it worked well for the most part. In 2024 I don’t think it is fully sending the information to avionics.

3

In your steps to reproduce, it wouldn’t start following the GPS line.

You would still be in heading mode.

You need to hit the NAV button to arm the Navigation mode and continue using HDG until it intercepts. A G1000 doesn’t switch to NAV mode by default.

I’ve used the G1000 in 2024 on about 40 flights now and never once have i experienced an issue with GPS intercepts.

1 Like
4

I think I’m just explaining it badly in the reproduction steps. Pressing NAV to arm then steering towards the line with HDG mode is never capturing the track for me. I’ll retry in 2020 to make sure I have the control sequence right.

5

agree and confirm.
Also i noticed some airbus (A320, 321…) have the NAV button not working.
Maybe i did something wrong but i cant activate them.
For the 337 Max, i can use the NAV but it often stops after a while and go towards like an idiot.

6

OK, my issue was that it had defaulted to LOC1. Cycling through the modes with CDI to enable GPS and it worked fine.

7

Yes, but even with NAV mode armed, the aircraft will blow right through the track and will not capture in some cases. I’m a pilot IRL so I know how to do it correctly, and this is an actual bug.