The starting position is the same as before: MSFS2024 SU2 (and also with SU3 beta), AIRAC 2508 rev. 2, stock scenery, correct sequence, no 7000 nm waypoint, nothing—it looks absolutely normal.
I assume you have installed any bad packages/or incompatible scenery on your system, but I can´t identify any navdata issue here.
It is highly recommended that you make your tests with the stock C172 equipped with the G1000 instead of any other aircraft/add-on to have a reference for whether it is working or not. And/or via the EFB …
I have tried once again and as you can see form the attached pictures, when you enter a star the FPS drops, the way points end up being +30000 miles away and some are not found , this is after a fresh install of Navdata.
Hi Owen,
As I mentioned before, it is very unlikely that this is a navdata issue. I don´t know anything about your system, what exactly you have installed, which version you use, and so on. So, it is hard to analyze it, but as you see in my screenshot, the data is included and selectable. All scenes are 100% compatible when the system is up-to-date and the correct configuration is used.
Have you tried it in the EFB and with the C172 and the G1000?
I´m pretty sure you have a misconfiguration on your system. Sorry!
I have used Navigraph for years and had no issues there is no problem with the set up and simbrief correctly shows the waypoints.
The issue is when the Stars inserted if you look at the pic with JTN waypoint it’s something like over 6000 miles, remove this star and it goes back to the correct NM’s.
You can also see that the PD waypoints are unknown hence the 0 nm for each one?.
Please could you try to replicate using the INI A330.
Hi again, Owen,
No, it´s not an INI issue; it is any issue with one package or the package loading order on your system. Sorry to say that again.
PMDG and Fenix use external databases completely independent of the MSFS data; therefore, such add-ons work correctly in every situation and after every update. Those aircraft that use the in-game MSFS data are more critical for incompatible packages, loading orders, etc.
Here the SAS9A arrival into ZSPD ILS34L from the Inibuild A330 ND:
You see, there is no missing waypoint or 7000 nm waypoint. Everything is in the correct sequence with the proper distances, again using the stock Inibuild A330 FMC here, too.
Your information indicates any configuration issue (loading order) or bad packages issue, but it´s not a navdata or aircraft issue. Sorry.