Do you have any add-ons in your Community folder? If yes, please remove and retest before posting.
Happens with, or without liveries in the community folder.
Are you using Developer Mode or made changes in it? No
Brief description of the issue:
The FMC distance to destination is calculated incorrectly. When the next waypoint is the same as the destination, its distance is added to the distance to destination.
Provide Screenshot(s)/video(s) of the issue encountered:
Detail steps to reproduce the issue encountered:
- Create an IFR flight from any airport to another, where you have at least 4 waypoints. Example: KSFO to KPDX
- Select the 787-10 aircraft
- Flight the route
As you start the route, the distance to KPDX will be decreasing in the FMC. This will continue until in the FMC the “next” waypoint is KPDX. At this point the distance to KPDX is incorrectly calculated by add the distance to current waypoint + next waypoint (which is KPDX) + distance to destination (KPX). So, if 25nm is left to the next waypoint, and KPDX is 100nm, since KPDX is shown also as the next waypoint, the FMC shows the distance to KPDX as 225nm (25+100+100).
PC specs for those who want to assist (if not entered in your profile)
Asus Strix ROG x299-XE Motherboard with an Intel i9-7900X
32GB DDR4
Asus Strix ROG RX 5700 XT OC 8GB
Did you submit this to Zendesk? If so, what is your ticket #? No
This happened to me on my first and only long-haul flight in the 787. It’s bad enough navigating with the goofy AP and FMC to begin with. Without the DTG, it’s silly. It’s something that was brought up on the Developer Q&A wishlist a couple of days ago, so hopefully we’ll hear something about the future of autopilots and FMCs in a few days.
2 Likes
Same poor FMC performance in the 748, regarding distance and ETA. Been unchanged since the beginning. Mine won’t even keep the time correct. Every instance that I check the clock in the weather (cloud symbol) tab the time is usually off by a few to several minutes. Clicking “live” will fix it but this should not be needed. There is no clock in a 748 dash that I can find… just the time to next waypoint which is usually wrong until I update the time as explained above. I’ve noticed this is a problem more so going east and west rather than north or south. Not to mention all the times are listed in local time not UTC. Just another way of not being very realistic. BTW, I don’t use pause.
1 Like
The 747-8 does the same thing, each waypoint restarts the count. done it since the start, so annoying
When flying the B787 or B747 from CYYC (Calgary) to CYEG (Edmonton), as I am approaching YEG, ATC tells me to proceed direct GOPEV. When I put that in the FMS, The AP then makes a hard left bank to take me away from GOPEV. If I take over control and head direct to GOPEV, the distance to GOPEV Increases as I get closer instead of decreasing. There are other similar bugs but this one is my most recent.
Yes! It’s very annoying. I think it creates a “starting” waypoint, at the moment of entering the one from the ATC. And, when EXEC is pressed, the aircraft is way past the starting point, so the autopilot wants to go back to that starting point, instead of simply going to the one entered. And, the FIX doesn’t seem to work, either, the only other option is to not use LNAV.
Thanks for the reply. I don’t remember having this issue with previous versions. It happened after one of the recent updates. Glad to hear I’m not the only one experiencing this issue. I hope they fix it.
I’ve been experiencing this issue since launch on both 747 and 787: The “PROG” view on the FMC consistently shows incorrect DTG and ETA to final destination. However, it shows correct #s for the next two waypoints. I got used to no relying on this, but it feels like an easy to address bug.
Reported to Zendesk 10 months ago under ticket number 88671, closed 9 months ago as “solved”, but clearly it isn’t solved (I have seen it again on a recent flight from KSEA to KORD and it affects all Boeing jets, including a 3-rd party 737-Max8)
1 Like
It is still (months later) displaying incorrect ETA for the destination regarding time and distance. I agree that this seems like it would be a simple fix that they have neglected to actually fix ever since the launch of the product. The notion that it was pointed out, assigned a ticket number, then closed and listed as solved, is just aggravating but frankly, not at all surprising. How sad a statement this is about the trio; Asobo’s, Zendesk, and MS’s quality and error correction capabilities.
1 Like
I logged a follow-up ticket on Zendesk (referencing my original ticket) to see whether they will look at it again and hopefully really solve the issue this time.
Maybe additional tickets logged by other simmers will raise the priority of the bug.
2 Likes