Can you give a specific example, then I can investigate? Thanks.

Asobo are very prone to changing file formats and specifications from version to version, without any notification of what they've done. So we have to rely on people spotting things and telling us...

I recently tried to enter a flight plan created with Plan-G in MSFS2020 and it assigns me disparate points in the flight plan, I have wanted to enter some other flight plan and the same thing happens to me, all this has happened since the last update of the MSFS2020, while if I make the flight plan with Simbrief, which also has a .pln format, it accepts it well for me. is there any solution to that? since due to that problem I cannot create any flight plan with the Plan-G for said simulator.

Thank you very much for your attention.
Best regards
Jesus Garcia

Good afternoon to everybody.
for some reason in the new version of the MSFS the Plan-G flight plans are not imported well, specifically it generates some points totally far from the plan and unlikely to fly, it is one or two reference points or waypoints located in the North Pole for instance. Everything was working fine in the previous version of MSFS 2020

The build is not showing any errors, and the number of VORS is at least approximately correct - you actually get a few more than I do (8990 vs 8963). Comparing the two screenshots, most of the missing VORs are actually TACANs, and the corresponding DMEs are actually shown (TACANs can't be received by regular VOR receivers). Now it may be that Asobo changed their TACAN data and Plan-G no longer sees it - I'll have to check on that: they do have a habit of just changing file formats on a whim. The second screenshot is not of MSFS data, since Plan-Gv3 did not support MSFS, so it must have been either P3D or X-Plane. I'd guess P3Dv3/4, which shows TACANs as VORs.

"ATC" should work (it shouldn't be case sensitive, although the answers are stored as lower case in the database). But beware of autocorrect - my reply here just got changed to "etc"

Hello Tim,

thanks for your reply.
I have rebuild the Database again, please find the new Log (392Kb) attached.

Btw: I answer the security question "what is the abbreviation for Air Traffic Control" with ATC and the System tells me the answer is wrong. What would have been the correct answer?

Many thanks & greetings
Claus

You may have left it too long before copying the log file - it's only kept for a day, and there's no database build in the one you posted.Please rebuild the database (again, sorry!) and immediately post the log file here. It'll be between 400k and 500k, for reference.

At the moment we can just see there are not many VORs, but not why.

Also, please check that you have MSFS set as the active database (data tab).

I'll look into it. If a fix is needed it'll be part of the X-Plane 12 update.

Hello, my name is Claus and I am a new user of MSFS 2020 and Plan-G v4.

I would like to learn to fly using VOR navigation and have already watched some YT videos. In a video, that explains how to create a flight plan using VORs, there are many more VORs than in my installed version.
I have already recreated the database (MSFS 2020) twice and attached the log to this post. I have also added 2 screenshots to show how the map looks in the video and how it is displayed in my installation - namely with far fewer VORs.

It would be great if someone could tell me what I'm doing wrong and how I can correct the error.

Thanks and greetings
Claus

I used V3 but mainly for X-plane 11 UK flight planning and have recently installed V4 to try. However I can no longer see lower airways at any zoom level. If I revert back to V3 they are visible. I have tried rebuilding the Navigation Database. Any suggestions as to get them showing in V4

Please try the dropbox link from the other thread: https://www.dropbox.com/s/0hppmgl7rj63rjo/Plan-Gv4.0.1.262.zip?dl=0