Looks like that strange error of a Flight Plan with Custom Waypoints generating huge legs North is back. It started showing up for me when the New Zealand World Update hit and some of us started using the extracted Bush Trips and tonight’s MS Community Fly-In Plan (both attached to this post).
Confirmed I am on 2302 Rev. 1 for both Navdata and Little Nav Map:
Seems we created two posts on same problem at the same time. This happened before, it’s some problem with navdata. Happens only with plans with custom waypoints. Not related to WU I would say. Last time it was fixed with new AIRAC revision.
Can confirm this happens to me as well, even when updated via Navdata Center. When I temporarily remove the navdata and navdata-base folders from the MSFS Community folder, custom PLN files prior to WU12 work again.
ok, we have tried to analyze this issue again and it looks again an issue with the sim-update but we have no idea what ASOBO had changed here. I have tested all AIRAC cycle now since the fix of this “north-pole” issue to eliminate an issue with the latest AIRAC cycle and this happens now with all previous AIRAC cycles too.
The strange thing is, that we haven´t seen any reports since the fix and now, after this update it happens again. Again and this happened with all previous/old cycles too now. We have reported this to ASOBO in the past but we haven´t gotten any answer to this. I will ask again but at the moment, we have no possibility to see what happens behind.
It´s a shame, that all 3rd party developer has the same issue with this updates and it´s impossible to spend 40-50 hours (at least every 2 months) after an update to look for a fix after the “try & error” principle because support is zero to us.
Sorry, we will see what happened with the upcoming updates - at the moment, we can´t do anything because we don´t know what they have changed! Again, it´s not a data issue because all previous cycles are also not working anymore …
Yes, last AIRAC was working properly for sure few days ago. Then it is really tied to WU. I’m suprised Asobo is not communicating with Navigraph as many users are using your navdata.
Any bug report on their forum will probably ends with “Please contact Navigraph to fix, as without their navdata, everything is working well.”
Because only in this version, you see which airports are real and existing in the data. When you only use the MSFS 2020 data you can select a none existing airport but this airport only exists in MSFS not in the AIRAC data → the result is a pseudo waypoint somewhere in the north pole region.
To be clear here a screenshot from LNM (using only MSFS data for flightplaning). You see that you will find the airport:
So the main issue is, that ASOBO offers airports which are not existing and when you plan a flight with a none existing airport in real + real-world data this is the result.
@bravetoss, @marekkye1 it would be great, when you both also can upload your PLN file here that I can verify/analyze it too but it looks that this is the issue. So no navdata issue, more an MSFS issue due not existing airports.
It is completely unclear for me, how ASOBO create the AIRAC updates because as I posted the screenshot from the AIP New Zealand. This airport isn´t existing (at least in the AIP) and therefore it can´t be included in the NavBlue data too - we know that they are mixing different source (FAA + NavBlue data) due the lack of information in the NavBlue data. But now, it looks also that they are mix the MSFS satellite data too
is it possible to set “custom waypoints” in the WorldMap since the latest WU12?
I can load an external created flightplan yes, but I can´t create an flightplan in the WorldMap which contains “custom waypoints”?
When I press somewhere, I get the custom waypoint “Navaid” and when I press “Add” nothing happens … I have tested this with and without our data, means with the stock data. Same behavior, can someone confirm this?
I think they changed the way the behavior works in the World Map, at least if you’re in SU12 Beta. It used to be that you’d put your cursor on the point you want, then right click to get a context sensitive menu. Now, you point at it, but left-click, pause left-click again to get the same menu:
Does not work here too. Using known (I hope) Apts LSZH, LSGG with user Wyp RW28 it creates those Northpole diversions. Attached the input and MSFS outputs from today, worked yesterday before the MS Update. Also the Airport name changed and messes up the FMS in the A320 neo (MS own one). Instead of LSZH it has Zurich in the FMS… and does not find in the the database though…
Seem really an MS/Asobo rather than NG issue ?!
Thank you - yep, they have changed anything with the latest update but it´s impossible without there help to understand what.
As I have described before, I have tried older cycles to eliminate that this is a current cycle issue but here too, every imported flightplan goes thru the north-pole. We have a set of “test-flightplans” which we use during the AIRAC tests before the release and we use test-protocols and here we have a “tested ok”.
It´s very frustrating not only for you as user but this update-policy and the none-communication is hard to understand, at least for me …