![]() I made a quick Excel file with macro functions to do this conversions which I found a great help.Necessary cookies are absolutely essential for the website to function properly. This differs from some other PMDG files where the lat/lons are in the format 'S 44.234098' (degrees with minutes/seconds to 6 decimal points. degrees, and minutes (including seconds) to 5 decimal points. As NZQN has only one 05/23 runway, I took out 05L, 05R, 23L, 23R and replaced them with 05/23 throughout the SID STAR file, and in the airport file too.ĥ) The FIX lat/lons are in the format 'S 44 23.12345' ie. The way to code this is 'AT OR BELOW 10000 AT OR ABOVE 16000'Ĥ) The default PMDG SID/STAR files for NZQN have 2 runways (05L and 05R, 23L and 23R). turn won't occur till this has happened)ģ) For NZQN, the STAR mentions FL ranges eg. Also, note the difference between HDG and TRK, and the use of OVERFLY to ensure a waypoint is actually passed over (next procedure eg. The painful part is inserting all the new fixes (QN775 etc.) - the lat lons needed to be worked out manually.Ī few 'learnings' from editing the PMDG SID/STAR file for NZQN:ġ) You must enter every FIX entered as part of a SID/STAR in the SID STAR file - it's not enough to have them in the waypoints file only.Ģ) In a STAR, it's invalid to put a TRK xxx degrees between waypoints: the FMC knows what the tracks are anyway (not 100% sure of this, but seemed to remove an error). Old topic I know, but was trying to create exactly the same thing: approaches for NZQN. One of the SID's, i forgot to insert FIX before a WPT By writing FIX OVERFLY this has helped align the approach better but is there a command to place a smooth arc between each fix in the approach? ![]() I'm pretty sure the TRK issue was not mentioned.Īlso in the real world approach charts for NZQN (in particular RNAV Y RWY 23) there are smooth arcs required between each fix to navigate safely through the mountainous terrain. Now that I can put in many fixes in the approach (making sure I don't use TRK) this helps me write accurate "real world" approaches for NZQN (and others).Īre there any other traps in writing the syntax for these files? I have read the "PMDG 737NG How to make Terminal Procedures" from the Avsim library as well as the "Tutorial on how to create and adapt data files for PMDG FMC" by Luca T. What I did find was the use of TRK in the APPROACHES section causes an error and the SIDS/STARS for that airport doesn't appear in the FMC. This did not seem to cause an issue either. I was also experimenting with by writing in one extra fix at a time to see if there was a limit to the number of fixes in an APPROACH line. I verified by checking every new additional fix one by one to see if the FMC showed and error and you guessed it, no error appeared. Also adding gates at the airport did not cause an issue either. In my updated SIDS STAR file for NZQN, I have been running through entry by entry for my additional APPROACHES, FIXES and GATES and did come to the conclusion also that ERROR at the "FIXES" line did mean there was an issue with the syntax somewhere in the file. There is a Tutorial how to make Terminal Procedures for PMDG Aircraft this document is made by Terry Yingling, You can find it in the AVSIM File libary search for the following: " PMDG 737NG Terminal Procedures Tutorial 5th Edition ". This is a very slow process but I would like to fly accurate approaches into my airports of choice in the simulator. Rather than starting with the functioning SIDSTAR file for NZQN and updating the file line by line then shutting down FSX then restarting to see if there is an error message in the FMC, is there a program that simulates the PMDG FMC alone so I can check if my newly written files will work in FSX? Is this a known issue when writing your own SIDS stars files?ĭoes anyone know of a tutorial or summary for writing the correct syntax and the possible command options for writing my own data for the 737ngx FMC? It appears like all other files in this folder and is very confusing. I keep getting an error at line 17 which is the word FIXES. ![]() I have searched the net for assistance in writing the correct syntax for these files and have been meticulous in adding all extra fixes to the file as well as the approaches and gates. In particular I have been attempting to write RNAV approaches for Queenstown NZ in the SIDSSTARS folder. ![]() I have been enjoying the amazing functionality and accuracy of the 737 NGX simulation and decided to write accurate approaches not in this months latest Navigraph updates. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |