Using NAV 3.1 for flight planning, some waypoints were missing particularly for the high altitude charts. For those using NAV 3.1, here's the procedure I used.First back up with renaming the extension of the precompiled .c files. Then back up the copy of World.wpt using another extension name on the copy. This is the waypoint file.In the RC folder, open with a text editor your latest fixes.txt file as obtained from the navdata AIRAC site. Select and place all the waypoint text lines into the clipboard. Close the file. (Make a copy first just so in case you inadvertently change something you will have a secure version.)In the NAV folder, open World.wpt in your text editor. Select and delete (not cut) just the waypoint data lines. Paste in the same location from the clipboard the waypoint text you got from Fixes.txt. Save and close.Besure there are no files ending any longer in .c. This I found is necessary to insure that NAV will correctly recompile and recreate its database index which appears to be cached.Start NAV and it should start disk crunching away for quite some time recompiling all of its data files and updating its index. Now close and reopen it just to be sure all is OK. Open the flight planning window, select ADD, and enter KMSP, in the dialog. Highlight and Send Minneapolis-St. Paul International to the plan. Punch ADD again and enter HARPI in the dialog. It should have come up with waypoint HARPI which did not show in FS or was in the NAV database when the last version was released but is on the current high altitude chart. Highlight and send it to the plan.The plan should not show a leg of about 40 nm to the SSW from the airport. Congrat's. You have made NAV freeware use a matched database. If all is OK, you can delete the former .c files that you changed the extension of as a backup.When you update the RC database by exporting AIRAC cycles in the RC format (not adventure format) from the navdata.at site, follow this procedure to update NAV. See the RC manual on getting AIRAC updates.Why don't I use FSNAV he asks? I want a flight planner, nothing more. No moving maps, etc. I use the GPS gauges from Reality-XP - that is the simpler Apollo line, not the Garmin 530. NAV saves in both its internal format and exports in .pln format to FS. NAV can also do GC routes as well. This allows me to manipulate as gauges using FS Panel Studio any panel configuration avoiding pop-up windows which I find a royal pain when I fly. I also think the operation of NAV would be quite realistic (not using autorouting) for commuter type avionics and GA as opposed to super airliner avionics gymnastics. I also use the printed plan out of NAV.Anyway, in various forums, posters were complaining about not being able to update NAV so for those interested this was my hack. I should mention that since the exported plan to FS contains coordinates and I believe altitudes, you need not worry about intersection waypoint data being in FS. There are other data files in source text format such as airports and NAVAID frequencies that may need updating. I have not looked a them but I suspect a similar procedure would work.If it were not for legalistic gymnastics and possible political wars, perhaps JD would code this as a nice little utility for NAV users.

Thanks for the info and the time and effort you put in (I happen to use Nav 3.1).Keep 'em flying!Brad