Hello, during the previous p3d and pmdg737,I was able to create a custom fix by adding values to the wpNavFIX file, but from this msfs pmdg777, I can’t create a custom fix because the wpNavFIX file doesn’t exist anymore, is there any other way?
Hi,
Thanks for the question - unfortunately there are no ways at the moment. Possible, that PMDG offers a solution in the future but currently, you should not change anything in the database.
Cheers
Richard
There is a way; I’ve built one of my company’s custom RNP (AR) approaches into JNU in the new navdata in the 777 for MSFS (in preparation for this navdata format being moved to the 737) and I’ve almost got it fully debugged and working, and this is a full procedure with RF legs etc. It involved adding several waypoints that weren’t already in the data. Adding a waypoint is very simple, especially if you’ve done any previous database work.
-
Dowload DB Browser - this is a free, open-source editor for SQL Lite databases.
https://sqlitebrowser.org/ -
Locate the file e_dfd_PMDG.s3db in your 777 installation location. BACK UP THE ORGINAL VERSION OF THIS FILE BEFORE ANY EDITS.
-
Open that file in DB Browswer.
-
Select “Browse Data” from the tabs near the top.
-
Select the correct table to add your waypoint to - either tbl_enroute_waypoints, or tbl_terminal_waypoints.
-
I would just highlight and duplicate a record for a waypoint in the same region as the one you’re trying to add, and then change the data as necessary for your waypoint.
-
When done, click “write changes” and then close DB Browser.
-
When you next load the 777, your waypoint should be available.
1 Like
Just to clarify, this is not supported and also not recommended from us - also it is not allowed to share the database or upload the database somewhere.
Thank you for your understanding
Richard
Thank you!, it works well
Why would you not do this as either a gps waypoint or a fix/rad/distance waypoint in the FMC. I can see all the data base doctors doing this stuff and then complaining that either Navigraph or PMDG broke something.
1 Like
Excellent answer @mwcrabtree … Thank you very much for this!
Cheers
Richard
It would depend on what you wanted the waypoint for, and the level of accuracy required. The FMC will not accept pilot-entered waypoints to a very high level of precision (that’s intended for enroute navigation), you may not know the course or bearing from another point (for instance, the ref waypoints for P-56 near DCA), and obviously you then could not use the waypoint as part of an arrival, departure, or approach procedure.
There are many good reasons to need to edit the navdata - mostly, the same reasons that airlines edit their own navdata in reality, vs only making do with what they buy 
.
I’m surprised at the expressed level of reticence from Navigraph on this; frankly the new PMDG stuff is both far more powerful AND easier to edit without screwing up than the old text-based hodgepodge format. That was frankly kind of a mess. The new stuff makes much more sense. Of course not sharing the database is a given, as the vast majority of work in there is not yours. I imagine if a person wanted to share a procedure, the way to do it would be to share only the records for that procedure / those fixes, and other users would need to append it to their data - which is very easy.
Worst case if something gets screwed up, a user could just run the navdata update again and get a clean version of the file and be right back where they started, pretty easily.
Don’t you see their complaints every day? 
And if there’s a problem, I can delete - reinstall it. I don’t think there’s any reason to get these ignorant comments from you
Offense cannot be given, only taken. When someone takes offense it says more about them. Good luck to you.
Crabby, it IS ok to admit you’re wrong, sometimes. Really, it is.
1 Like
This thread has degenerated into personal attacks/comments which are not tolerated.
Thread closed
Ian