FRUSTRATION! 787 LNAV tracking issues

Team,

This issue is becoming a real problem. I will be in mid-flight following a course (LNAV) and the plane will just start to circle. When I tried using the heading bug, it doesn’t track either. On take-off, after 2500ft I engage the LNAV and it doesn’t track. When I tried using the Approach it didn’t track either.

I set the Dead Zone 5%; I removed NXTi. Still an issue. This happened after the December release.

Anyone else having this issue. I had some of the same issues with the twin engine props as well.

Thanks!
-joe-

1 Like

Moved to #self-service:instruments

Did you try with the Community Folder empty to confirm it isn’t an addon conflict?
If you have proved it isn’t, did you try deleting the folder for the 787 from the Official, One Store folder and then starting the sim to download a new one?

How do you delete the 787 from the folder? I did not see it in content manager, only liveries. I have the same problem, no add ons in community folder, still does the circle and plummet to earth…

I have the same question. Do we just delete the aircraft from the content manager? There are 5 787 files if I filter on the 787

Are you using MSStore or a Steam installation.
The file you want is “Asobo-aircraft-b787-10”
Delete that file.

MSSTORE. Where do I find that? Remove it from the fs2020 content manager? If it is in the MSSTORE not sure where to look. Thanks

If you are MS Store version, the folder is located here:
C:\Users\USERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore

I found the directory and deleted the files. I re-ran FS and it performed an update on it’s own. I am currently flying from KORD to KEWR. On takeoff I manually flew to align with the first waypoint. The FMC found it and started tracking. about 5 mins into that, it began to bank a hard right. I tried using the heading bug to bring back on course and nothing happened. I manually flew back on coarse and rest the LNAV. It’s now been keeping to the plan for the past 20 mins. I will monitor and let you know if it does it again.

AN observation I have based on the past issues, it seems the autopilot get’s confused as it tries to track. When I switch to STARS pattern entry, the autopilot wants to take the plane to the beginning of the change. SO it doubles back and then realigns. It would lockin from the point I intercept the change. This constantly happens. Just an additional note. I will get a screen grab if it happens on this flight.

Thanks

1 Like

I remember this happening to me a long time ago but never in the last year. I have been using the Heavy mod though. I don’t know if it changes the autopilot behavior

Team, I load the latest version of B78XH addon hoping this would help. What I am seeing that it banks right as it approaches the first and last Nav Aid. Not sure why this is doing it. If anyone has any suggestions I would be up for hearing it. I am afraid to leave the simulator for long flights because I am not sure what would happen.

Any help is greatly appreciated.

Thanks

Since the conversation has now moved to the B787 Heavy Mod, this thread is now in #third-party-addon-discussion:tools-utilities

It’s also probably your deadzones are high enough on your stick. Have you checked the sensitivity settings and deadzones? I have mine increased to 16%

I occasionally fly very long haul routes (KJFK - WSSS, KJFK - RPLL, KJFK - NZAA) in the 787 with the Salty mod. I haven’t had any issues with the FMS/AP.

I have noticed in all aircraft I use that if there is a “discontinuity” in the flight plan, the FMS does not know how to process it and would send the aircraft flying somewhere randomly or flying in circles.

The Salty mod is for the 747. The Heavy mod is for the 787. Also OP didn’t mention anything about problem happening after a discontinuity.

Thx for the correction. Too many mods to keep track of…

This affects the standard plan with no modifications as well. I am not running the Mod, and it won’t follow the magenta line, or keep altitude…

Honestly, if this is a problem with the default 787 and it’s not the deadzone of your controller, there is no workaround. This is an Asobo problem.

To make sure, once you takeoff, unplug all your hardware except your mouse. Fly completely on autopilot and verify that the problem still occurs.

Thanks all. I will disconnect the pedals and yoke once I am in the air. I will let you folks know.

Thanks again

FYI. I am using Heavy Mod.