I found that a lot of navigation data and many coordinates are offset by thousands of nautical miles. This problem has existed in msfs2020 before, but if the unicode program language is adjusted to American English, this bug will not exist. The problem of MSFS2024 actually exists again.
Just give an example:
The flight plan is as follows:
ZSSS/36L NXD71D NXD W131 AKDIM A470 DUBGO W134 ELNEX A599 PLT W19 MABAG W44 OLPAB OLPA3A ZGGG/GG424.I02LZ
These waypoints I circled are all thousands of nautical miles away. And, if the first navigation data is at the end of the runway, that waypoint is 100% thousands of nautical miles away.
I’ve actually seen something similar to this in medium cargo flights with a Caravan across Australia. The flight path looks normal in-game but when I load the flight plan into Navigraph Charts sometimes there are 1 or 2 waypoints on another continent.
This suggests to me there may be problems with the base game’s navigation data.
I’ve seen the same thing and posted it here, but then found that my custom VHHH scenery might cause the issue. Once removed, the distances are fine and the waypoints are back in the nav database. Maybe a scenery can bring it’s own (tiny) nav DB?
I also found that this happens if you use a third-party airport. But why a third-party airport would cause this is worth investigating by asobo. In addition, I also found a solution to install navigraph and then adjust the priority. Ensure that navigraph-navdate has the highest priority, and airports with navigation bugs have a smaller priority than it.
Before msfs2024 was updated to 1.2.7.0, this method was available. But after the update, the format of content.xml changed, so I don’t know if the method of adjusting the priority still works. But now it seems that the method has failed.
