Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
2 tags are required: One for platform, and one for aircraft.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons? 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 Community Support section.
Yes
Which aircraft are you reporting an issue about? (Please also add the proper tag for it)
787 built-in
Brief description of the issue:
2 issues:
The aileron/rudder controls 787 will not center with keyboard assigned key. The controls for other aircraft center using the same computer and assigned keyboard key.
787 will not follow the flight plan with Autopilot with VNAV enabled. 787 was working fine before the latest update. 747 works just fine with the same configuration.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
PC specs and/or peripheral set up if relevant:
Not relevant. 787 was working fine before the update.
Build Version # when you first started experiencing this issue:
Latest update.
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:
Can you provide more details like flight plan specifics?
Did you configure the VNAV in the FMC?
Does the 787 fly the LNAV correctly?
What is displayed in the FMC when the Altitude button is pressed?
If you use the World Map for flight planning, check your Route in the FMC. I frequently find legs that show Vectors rather than Direct to. The FMC interprets those as Heading Holds and expects your to manually fly those legs. When you get to a leg that Is Direct To the LNAV will take over again. You can see this happen in the PFD.
Correction to the original issue statement. I observed this issue when LNAV (not VNAV) is engaged.
I configured the route using the world map. It worked reliably previously before the latest update. Now, it no longer works.
before the update, both planes 787 and the 747 worked normal. Now after the update i have a green arrow instead of the purple one inthe compass left up onscreen.. and no waypoints that my flightpath normally gives to follow… please get that update deleted. the 787 was one of y main planes to fly with. now they are unflyable for me…
Can you save your flight plan (PLN file) before you start FLY and send it to me via a message and I’ll take a look at it. Unfortunately, saying “it worked before and now it doesn’t” isn’t very helpful to figure out the issue. Thx!
Any chance you can illustrate how “Vectors”, “Heading holds”, and “Direct tos” show up in the FMC? If a leg is shown as a “Vector” or “Heading hold”, how do you change that to a “Direct to”?
With the recent update, it appears that the AP in the 787 and 747 have become more strict in the way that it expects and interprets SIDs and STARs.
AlchiD, sorry I don’t know how to do that. To simplify what I was saying–in the FMC most of the flight plan legs will have Dirrect followed by a Waypoint. Occasionally instead of Direct it will say Vectors followed by a Waypoint. That means the system expects you to manually fly to that waypoint, hence Heading mode instead of LNAV.
Hope this helps.
So I’m having the same issue with the 747,787,ATR,CRJ. I’m assuming they use the same avionics in the game. If I setup a simple flight plan via the world map as Direct GPS the plane spawns with VOR rather than GPS as default navigation. On most general aviation aircraft you would adjust the CDI to change but this option does not exist on this type of aircraft.
I dabbled into using the FMC, and setting the flight without a destination I’m able to key in the flight info, and was able to set the route. The route shows up on VFR map ,available on the Quick Menu in flight, but the Autopilot will not follow the route.
Now if I use the MS A320 Neo with the same exact flight it spawns as GPS navigation default and functions as it should. As someone mentioned before this occurred after the last update.
To set up a basic route that the LNAV will follow:
[RTE], enter departure ICAO code into the ORIGIN field.
Enter runway number into RUNWAY field.
Enter destination ICAO code into the DEST field.
Click Activate, then [EXEC]
[DEP/ARR] x2 then select the ARR for the destination airport. Select an Approach, then [EXEC]
[LEGS] page shows the current flightplan. At this point you likely won’t have a magenta line on the nav display yet, as the LEGS page will have a discontinuity. To clear this, select the line below the disc to copy it, then paste it into the line above. Then [EXEC] again.
The Nav Display should now draw a magenta line.
(In the screenshot below I would click the button next to REBLI to copy it, then click the button on the line above to paste it).
I never had this issue with the new avionics until now. 787 follows the FLP line then starts banking back and forth trying to reach the magenta line which never centers anymore just bangs far left then banks far right. Is this an AAUU2 issue?
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:
I have the same problem. The 787-10 is actually unflyable right now. AP does not work. FD LNAV VNAV none of these control the aircraft.
I have put the flight plan in each time.
Before the update I could fly long range with no issues. Now, it’s a challenge to take off and the plane doe snot follow the flight plan.
I had added the Asobo 787-10 Realism mod which really slowed the games load time considerably. When I had this mod installed, I could not take off in the plane without crashing into the ground. When I removed the mod, I can now take off and use AI to fly to fly the plane but anything else AP etc does not work.
Your tone is a bit condescending. That being said, I have flown this plane and followed the instructions to the letter. I am telling you, it does not work. I am well versed in the YouTube videos which is where I learned how to fly this thing in the first place.
The Asobo B787-10 Realism Mod is from Flightsim.to It has been updated to work with SU13
Well… I have also flown the 787, and aside from the flight plan not being followed in external view, and the discos found in some flight plans that periodically need to be corrected in the FMS/FMC, it flies very well. I am not using any “realism mod”. One thing I have noticed with the 787 is that it won’t ascend above 38000 ft. Don’t know why, but I’m sure that will be fixed. That is all.
The short answer is that we are diametrically different people with different knowledge, instruction, and even perceptions. Not everyone is at your level (whatever it is) and not everyone learns the same way. You should develop some patience, and kindness and try to understand an issue instead of assuming the person posting is an idiot. -end-
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Nice Post!