Hi! One question: i've downloaded the sid/star database, but sometimes, even with the bigger airports like EHAM, the sid and stars don't appear in the fmc dep page. I have to manually download them from the site and put them in the sid star folder, often overwriting the other one!!?? After this it works fine, but it is very annoying to manually download the sids and stars each time!Anyone suggestions or having the same problem?Regards, Ruben

same problem, yes

This thread may help?http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchSimon

ok, let me clear this: the sid and stars ARE installed in the correct folder, but do NOT show up in the fmc. What causes this problem? I read the "SID/STAR/IAPs updates explained. New 737NG owners should read this" thread, but my problem is not mentioned.Regards Ruben

Hi Ruben,Let's try to get to the bottom of it.Assuming indeed that you have roughly 2055 TXT files in your My Drive:Program FilesMicrosoft GamesFlight Simulator 9PMDGSIDSTARS folder (this is approximately the number of procedures installed with Terry's monthly cycle) and assuming that the FMC does not give any warning / message when you try to open an airport then it looks to me as if the monthly cycle you downloaded is corrupted. Maybe you should try the following:1. manually delete all files in the ....PMDGSIDSTARS folder,2. download again the terminal procedures from Terry's site,3. install and verify that the PMDGSIDSTARS folder contains more than 2000 TXT files,4. if you wish download from Navdata the "all in one" package of custom-made procedures and install them in the same folder as above,5. Before starting FS9 check in the PMDGSIDSTARS folder that your departure and destination airports are listed. Now, should the FMC give you a warning / message when you input the departure or destination airport or when you pick up a procedure at those airport plese report the message(s) here and we shall see from there.Michael

Ok, I downloaded the sid stars all in one file from navdata, but i can't find the sidstar file from terry. Maybe someone can give me a link to his site? (and why is the sidstar file from www.precisionmanuals.com not ok?)Regards Ruben

Ruben,Of course the sidstar file from www.precisionmanuals.com is OK. Sorry I did not mention it before. In fact it should be exactly the same file.Michael

well, i donwloaded the new sidstar cycle, deleted the complete content of the old sidstar folder, installed the newones, but only the runways popup in the fmc, no single star or sid, very anoying...suggestions?Regards Ruben

Hi Ruben>Ok, I downloaded the sid stars all in one file from navdata,>but i can't find the sidstar file from terry. Maybe someone>can give me a link to his site?http://home.sw.rr.com/filesherenow/index.html>(and why is the sidstar file from www.precisionmanuals.com >not ok?)It depends on timing. At the same time I release the newest cycle on my site I also send it to PMDG but it usually takes some time before it gets posted. So there is some time period where the cycle numbers don't agree. Having a different cycle than the AIRAC one can cause problems with runways not being found due to runway number changes in the real world. You should always verify that the AIRAC cycle and my terminal procedures cycle are the same cycle number. Open any of the files, AIRAC or mine, and the cycle number is in the header.RegardsTerry

Hello RubenYou didn't mention if you did step 5 of Michael's suggestions, "Before starting FS9 check in the PMDGSIDSTARS folder that your departure and destination airports are listed." It sounds silly but I've answered more than one message having your problem only to find out that airport XYZ was not in the PMDGSidstars folder afterall. If the FMC does not find the departure or destination airport it only lists the runways available, just like you are seeing.You also didn't mention if you got a warning message when you input the departure or destination airport. Was there any warning message? This can also cause the same symptoms.These questions provide clues in the troubleshooting process.I might also add that I have seen your problem caused by two other situations. One, a bad 737NG install and one that went bad and, two, by flying a 737NG that had not been upgraded or patched.RegardsTerry

"You also didn't mention if you got a warning message when you input the departure or destination airport. Was there any warning message? This can also cause the same symptoms".No warnings, and the dep/arr. file IS listed in the sidstar folder, I'm also flying the upgraded 737NG. The only thing that might caus this prob may be a bad install...right?...