OK, I give up. What's the secret to getting addon runways like those in Aerosoft's Antarctica X to appear in

the PMDG FMC? I've tried modeling my attempts after the VHHX "manual" installation but "no joy". Is it required

to add (at least) one SID or STAR to the appropriate data file to get runways to be recognized by the FMC.

I've been using the T7 as a test bed for my experiments. Also, the FMC will not load a saved flight plan

via the CO Route method that has (Antarctica X) NZPG as departure or arrival airport. The FMC WILL accept

NZPG as an entry in the departure or destination block; and then of course it's possible to manually enter

all the route waypoints, airways, etc. so this can be used as a satisfactory workaround. The FMC will also

still allow normal entry of other routes via the CO Route method and shows the runways of the respective

airports. I seen to be only having the FMC data setup / organization problems with the addon airports.

Ken

Thank you Kevin.  I will keep this ideas in mind as I press on with my Antarctica (McMurdo) project.

I presently have succeeded in getting the PMDG FMC to accept NZPG (McMurdo Pegasas) on the

initialization page.  But unfortunately have had no success so far having the NZPG runways appear

on the DEP page.  I'm sure that I've added the rwy lines to the wpnavapt.txt file in the correct format;

but I've obviously missed something.  I've inserted some of my custom wpnavapt.txt NZPG lines below with

a known good line for comparison. Let me know if anything looks "strange"  ~

 

"BASE MARAMBIO SAWB24 04134240-64.236667 -56.618611000.0024000740 " ;; Example of known good line (ignore quotes)

 

MCMURDO PEGASUS NZPG15 11023015-77.952156 166.489482000.0001500000 ;; My custom added NZPG lines

MCMURDO PEGASUS NZPG33 11023195-77.980339 166.538582000.0019500000

MCMURDO PEGASUS NZPG08 10000309-77.957195 166.552157000.0030900000

MCMURDO PEGASUS NZPG26 10000129-77.958887 166.682206000.0012900000

 

My NZPG runway headings are referenced to "True" North since I understand that in the real world "True North"

headings are used in most of Canada and near the poles due to the large magnetic variations in those areas.

I believe that many (if not all) runway headings in the database are referenced to True north.

I'm open to any / all suggestions.

Ken

Firstly if the airports aren't showing up at all I don't think the program can find them. It won't be a heading issue. So therefore the order you put them in the file is probably crucial. The order of airports in wpnavapt.txt is the same as the order of airports in airports.dat. Note that the order in airport.dat is of increasing latitude. So the furthest south airport is first. Your new airports will probably be at the top of the list. Also the runways for each airport are in numerical order in wpnavapt.txt, not as you have put them (in pair order). So your new runways should probably be in the order:

 

NZPG08

NZPG15

NZPG26

NZPG33

 

It may not matter but it's safest to stick to the order the others are in, in case some programmer has assumed that order is always going to be stuck to.

 

Secondly the data has to be consistent. FSX won't know that some have mag headings and some have true. So I would put mag headings in throughout, even though the mag heading wouldn't be used for navigation in practice.

 

I'm guessing as much as you are, but two heads are better than one.

Thanks again Kevin. I have reordered the entries as you have prescribed and all seems to be working
correctly except for the NZPG runways not showing on the Departure (or Destination) pages, and FMC still not
accepting the flight plan when the route is entered via the FMC's "co route" block. Seems strange that
the FMC WILL accept NZPG in the Departure and Destination blocks, but not the "co route" block.
Do you know what FSX or (or other) scenery files that the PMDG nav data files get their runway specifications

from? Or, if I'm doing a custom addon airport modification to the FMC data files exactly where should I be

getting the runway specs (Lat / Lon, altitude, headings, etc)? I'm thinking perhaps I can load the appropriate

AF2 or bgl file into ADE and use it to obtain the specs; but I'm also thinking that the FMC database reads and
compares what is present in the database to what exists in an AF2 or bgl file somewhere.
Best regards,
Ken

That's progress at least.

 

Have you added a file for the new airfield (and the runways) in the SIDSTARS folder? That might be the issue for selecting them for departure and arrival menu. Not being able to do that might also prevent COROUTES working. Again just a wild guess. Other than that you'll need to ask Ryan for help with specific PMDG functionality.

I'll try to create a simple SID and STAR and add them to the appropriate file (in the appropriate format~  tonight, and see what happens.

Ken

Why is there another thread on this? I posted a huge reply into a different one that's still sitting right here on the front page just yesterday explaining everything. Cmon people, look at what's sitting there on the very first page before going and necroposting in a year old thread...

 

http://forum.avsim.net/topic/442498-adding-airports-to-fmc-database/

Why is there another thread on this? I posted a huge reply into a different one that's still sitting right here on the front page just yesterday explaining everything. Cmon people, look at what's sitting there on the very first page before going and necroposting in a year old thread...

 

http://forum.avsim.net/topic/442498-adding-airports-to-fmc-database/

Steady on Ryan. Yes this is an old thread but both threads have current replies. When I first replied to this thread the other thread wasn't on the front page. Multiple threads on the same topic happen sometimes and of course they leapfrog each other as replies are added.

I'll take the heat on this Kevin and Ryan. I've meandered my concerns on this matter over to the other topic >>

 

http://forum.avsim.net/topic/442498-adding-airports-to-fmc-database/

 

Best to all,

Ken