Waypoint at wrong location

[winsome]

Dear all,

I have read many articles about reordering }}}navigraph-nav-jepp and !!!navigraph-nav-base.

That solution in fact solve half of the issue as part of the waypoints are no longer located at N0E0 (like many users mentioned the problem of VHHH). Meanwhile, I still have some mislocated waypoints in STAR transitions. Below is an example:

Any ordering hint or settings I can do to make everything runs correctly? Thank you in advance for your help!

Best regards,
Winsome Wong

[NAVData]

Hi,
That has nothing to do with any package load order. It´s simply a miscalculation or misinterpretation in the FMC of the specific aircraft. I don´t know which sim you use or what aircraft you are using here, so I can´t check it, but it has nothing to do with the loading order.

By the way, the package name with }}} is obsolete and should not be used any longer - not in MSFS2020 nor 2024. The Hub hasn´t installed these folder names for months.

Cheers,
Richard

[winsome]

Dear Richard,

Thank you for your reply and sorry for the missing information.

I am flying from VHHH to RCTP with WFSS VHHH and ACO RCTP with the MSFS2024 default A330.

If I remove the !!! and {{{, I could see a few waypoints located far away from the correct location. That’s the reason why I use the symbols to keep the ordering.

However, after investigations today, if I kept that ordering tool, I would have other scenery waypoint mismatch, like what I showed in the previous post.

I have seen lots of articles about some scenery messing with navgraph waypoints. Is there a final solution to that issue? I only have this messing waypoint problem with default MSFS 2024 planes.

Thank you very much for your help.

Best regards,
Winsome

[NAVData]

Hi,
Two questions:

1. Do you use a 3rd party scenery for these airports
2. Have you tried it with the stock C172 equipped with the G1000

My question is because you wrote that you use only stock aircraft. Not all stock aircraft don’t fully support the new WT framework in the background. The G1000 supports the new internal framework, which should be the reference.

So, I would try it with the G1000 to check it.

Cheers
Richard

[winsome]

Dear Richard,

1. Yes. I am using WFSS VHHH scenery. I know that there is no problem with the default one.
2. Below is a picture of C172 with G1000 which I set up the DALO1D departure. The waypoint is still messing up.
   
   

Cheers,
Winsome

[NAVData]

Hi again,
Thanks for your help. I’m pretty sure now that this is a scenery issue. I will also install the scenery and will analyze it. I assume the scenery contains waypoints, navaids, and procedures. It is rare and uncommon, but I will look deeper into the scenery.

Thanks again for the example and your testing with the G1000.

Cheers
Richard

[winsome]

Hi Richard,

Thank you very much for your help! In fact quite a number of players reported this scenery issue and some of the solutions in the past in fact helps (like adding an “A” in front of the WFSS scenery folder and adding !!! and }}} to nav folders). However, somehow some solutions begin not working after a number of sim updates. I understand that it is actually not a navigraph issue. I just want to see if any experts can help with it.

Cheers,
Winsome

[NAVData]

We will find a solution … Renaming the packages is obsolete and doesn’t work in the same way as in the past. Thats due the sim updates yes …

But anyway, think positive we will find the culprit

Cheers
Richard

[NAVData]

Hi again,
I have tried the WFSS VHHH scenery in MSFS2024 with our data, but I can´t reproduce your issue. Here, what I see with the DOLOL1A:

That is correct. There must be another issue on your system, possibly with another package. Can you please upload your content.xml file here?

I have only done this, which is highly recommended:

FAQ - MSFS2024 Missing terminal procedures in 3rd party sceneries

When you identify any issues with missing or wrong/outdated terminal procedures on an installed 3rd party scenery, try following: Backup your content.xml file first Open your content.xml file via any text editor Look for: communityfs24-navigraph-nav-base Add priority="-999" (minus 999) in this line Look for: communityfs24-navigraph-nav-jepp Add priority="999" (plus 999) in this line save the file - be sure that you save the file as a UTF8 file (NOT! as a UTF8-BOM file) You can also c…

No package renaming, nothing - I have set only the priority according to the instructions in the FAQ posting. I have also tried a few other terminal procedures, but haven´t seen any issues. Please upload your content file so that I can check it. I have checked the scenery settings, and all are okay, so the scenery isn´t the culprit here. Do you have any other issues?

Thank you
Richard