Navigation: loading custom waypoints from .pln files is broken on some systems

Not sure if this is helpful, but I had this issue after I recently uninstalled everything in Content Manager in order to save space on an underpowered laptop I was using to just import flight plans from Little Nav Maps, and then upload them to the cloud for use on my XBox.
As soon as I reinstalled all the World Updates, and airports, the problem was resolved

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Folks - status is now “bug-logged” meaning Dev Team confirms defect through repro, and now it moves through to remediation and determination when to deploy the fix. Thanks to everyone for contributing to this report!

1 Like

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:

any flight plan with a custom waypoint totally breaks and routes me to the north pole for each WP once loaded into the sim. I have navigraph (2212 Rev1).

If relevant, provide additional screenshots/video:

The first screenshot is how the route looks in LNM before loading in to the sim.

-The second screenshot is after I have loaded the flight plan in the sim.
9f4380df5c7c88dcf2f2619fc7ebfdab

-The third screenshot is after I save that flight plan in the sim and then re-load it in LNM a second time.

Does someone found a workaround until this is fixed by Asobo?

Ok, I’ve read some forum threads here and in the navigraph forum.

I was not aware, that navigraph caused this issue. After updating the MSFS database to Navigraph AIRAC Cycle 2302 revision 4 it is working again.

This is now back after World Update 13 today. Any idea of what the final fix was?

1 Like

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:

Using .pln files with custom waypoints triggers the same issue with points relocating to the North Pole. However, if using an associated .flt file to load the same flightplan, the problem does not occur. This has only happened for me since WU13. I am using Navigraph 2304 Rev.3.

If relevant, provide additional screenshots/video:


Flight plan loaded from .pln file


Same plan loaded using the .flt file

1 Like

I’m having this same issue again also.

1 Like

I had the same when loading a simple pln, the route loaded into the world map and all the waypoints pointed to the north pole, I uninstalled Navigraph ( I had all the latest updates being a sub to navi ) after the pln loaded into the world map correctly, so a bug somewhere with Navigraph, very surprised as Navigraph being quite an expensive sub…

Hopefully someone from Navigraph can let us know why this is happening?.. thx

Using plans generated by Little NavMap v2.8.10 64-bit.
I had this issue intermittently, but all day on 6/6/2023. I followed the advice above and removed all Navigraph files from Community to a hold directory and the issue went away.

Hi there! Been having this issue recently and installing the latest world update (XIII) fixed it. It seems like Navigraph build its last AIRAC with some dependencies with the world update.
With this fix you can put Navigraph’s files back :slight_smile:

Cheers

Now it is back again, and ATC voices are gone again, and and and. We must have had another MSFS 2020 update. :face_with_raised_eyebrow:

Now ATC voices are gone again. :grimacing:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Seems this bug is back. Running Navigraph AIRAC 2306 in Little Nav Map and MSFS2020. If I save a plan in Little Nav Map OR MSFS2020 that has custom waypooints. Then when I load it back in the custom waypoints are actually in the North pole. 2023-07-07T04:00:00Z
Provide extra information to complete the original desc ription of the issue:

Custom way points loaded into MSFS from a .pln file always show up in the north pole. Whether they are created in MSFS or a 3rd party application.
If relevant, provide additional screenshots/video:

I have been having this issue ever since I purchased and installed Navigraph into the sim & LNM. I have all latest updates to Navigraph, MSFS & LNM.
I can NOT USE ANY CUSTOM WP AT ALL !!

Does anyone know how to fix this issue?

Thanks, David.

Having the same problem. I installed ALL World Updates to try and fix this, but user waypoints are still borked with airac 2306.

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:

Installed all World Updates to try and fix but issue persists

If relevant, provide additional screenshots/video:

Have you contacted Navigraph about this? If custom waypoints worked before you installed Navigraph and now they don’t, I suspect the problem is caused by Navigraph.

My understanding is that Navigraph have stated this is a MSFS bug and needs to be resolved by Asobo.

Sorry, this doesn’t make sense to me. The general software troubleshooting paradigm is that if something breaks after a change is made, then remove the change.

Navigraph should communicate all the details of this problem. Who are they working with at MSFS? When was the last time they talked with Asobo? When is a fix available? Who is going to test this fix to make sure it works? What is the current status?

I assume that MSFS does not have Navigraph or any 3rd party vendor app for testing. Whenever an update is published by either MSFS or Navigraph, who is responsible for testing Navigraph?

I do not like it when any vendor throws a problem over the wall to another vendor to fix! Who owns the problem? Has Asobo taken ownership? If not, why not? Basically problems between vendors frustrates users because money has been spent on broken software that should work.

I’ve had problems in the distant past using the Navigraph add-on with MSFS so I removed it. I have no desire to reinstall it because of the waypoint issue. Unfortunately, not having it messes up a different 3rd party app.