PMDG 737NGX released!

[cowpatz]

Unfortunately the original NZQN Terminal procedures file that I constructed has become a little corrupted over time. The PMDG aircraft have never supported the AF (arc to fix) leg type. The only way to construct a DME arc is to use a series of waypoints approximating the arc.
I was hoping that the release of the NGX would fix that but from my reading I take it that the AF and RF leg types will be released with an upcoming SP update.
I have yet to purchase this model (as I don't really think my current system will do it justice) so I cannot update the procedure.

[nalbers]

QUOTE (cowpatz @ Sep 1 2011,10:56 PM) <{POST_SNAPBACK}>

Unfortunately the original NZQN Terminal procedures file that I constructed has become a little corrupted over time. The PMDG aircraft have never supported the AF (arc to fix) leg type. The only way to construct a DME arc is to use a series of waypoints approximating the arc.
I was hoping that the release of the NGX would fix that but from my reading I take it that the AF and RF leg types will be released with an upcoming SP update.
I have yet to purchase this model (as I don't really think my current system will do it justice) so I cannot update the procedure.

There may be more going on. I'm experimenting with your terminal procedures file by removing blocks until it works. At the moment it only has the runway info and the Fixes block and still isn't showing up properly in the FMC. Now to see what happens if the only thing in there is the runways... If that doesn't work I'll start with a working file from another airport and strip it down and slowly start adding fixes/procedures etc. Crude method, I know, but it should show me what the limitations of the format are. I hope the problem isn't in the Fixes.. That's the information that's the hardest to get a hold of.
I hope you don't mind me using your file as a base to get a working version for FSX?

[nalbers]

QUOTE (nalbers @ Sep 1 2011,11:09 PM) <{POST_SNAPBACK}>

There may be more going on. I'm experimenting with your terminal procedures file by removing blocks until it works. At the moment it only has the runway info and the Fixes block and still isn't showing up properly in the FMC. Now to see what happens if the only thing in there is the runways... If that doesn't work I'll start with a working file from another airport and strip it down and slowly start adding fixes/procedures etc. Crude method, I know, but it should show me what the limitations of the format are. I hope the problem isn't in the Fixes.. That's the information that's the hardest to get a hold of.
I hope you don't mind me using your file as a base to get a working version for FSX?

And I've managed to track down a few of the problems. Any of these problems and the DEP/ARR page doesn't have any entries.
1. All the runway entries have to match the runways known in FSX in the scenery. Which means 05R and 23L for NZQN
2. No COLOCATED fixes. This is a game breaker for me, since I have no idea how to convert these into LATLON fixes.

[cowpatz]

I wonder why they removed the co-located fix feature? It sure made things easier. It might be to do with the navigraph data updates.