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.
Hi all, I am facing the same issue now. Adding the letter A in front doesn’t make a difference. Flying out of VHHH from WFSS seems impossible with a STAR and iniBuilds A321.
Any idea ?
Currently, I have found a solution to this issue. First, install the Navigraph navigation data. Second, use the package reorder tool to sort the files, moving third-party add-on airports above fs-base-nav , as shown in the image. Then restart the game.
Remove the underscores “_” in the folder name WFSS_VHHH located at the path Community\wfscenerystudio-vhhh-ms24\scenery. For example, I renamed it to WFSceneryStudioVHHH. Then use MSFSLayoutGenerator.exe to regenerate the layout.json file.
This should resolve the issue of scrambled navigation data.
Unfortunately this doesn’t work either as I cannot place the airport above fs-base-nav. Base-nav shows as locked, and therefore I cannot place anything above it.
Does anybody know of another VHHH airport scenery that I could use ?
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:
One for aircraft (start typing in your aircraft name in the tag section and pick correct option)
Feel free to delete this quote section after adding your appropriate tags.
ISSUE DESCRIPTION
So far I have noticed that VHHH Hong Kong and ZSPD Shanghai Pudong arrival and departure procedures are completely broken to the point where you can’t use any RNAV or even VOR instrument departure. All the waypoints seem to go to somewhere literally on the other side of the world and are just stacked on top of each other before connecting to your route of flight.
The iniBuilds A300 is the only aircraft that does this. The A350, and even with the TDS GTNXi and all worked flawlessly. So I am not sure what went wrong here. I am on version 1.0.4 and the latest AIRAC cycle. This only happens in 2024 as I tested this in 2020 and the SIDS and STARS work just fine. I contacted iniBuilds and they said it’s most likely a sim issue because of how frequently it happens with other aircraft too. Though, the A350 was fine for me.
If applicable, which aircraft is experiencing this issue:
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
Yes
FREQUENCY OF ISSUE
Every time
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
Spawn in anywhere at VHHH or ZSPD
Select SID or STAR
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:
[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?
DX12
[PC Only] What GPU (Graphics Card) do you use?
4070
[PC Only] What other relevant PC specs can you share?
MEDIA
Please add a screenshot or video of the issue occurring.
Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes,
Provide extra information to complete the original description of the issue:
• I thought it may because that the designers of the airport scenery, WFSS specifically, did not put waypoints near the airport.
If relevant, provide additional screenshots/video:
•
For anyone who wants to contribute on this issue, Click on the button below to use this template: