Hi Terry;Im starting here with this question because I don't know where else to start.Two of my freinds have the Level-D 767. I don't, I fly the PMDG 737NG. We tried to all do a flight from KBWI to KBOS. When my LDS freinds select the SWANN3 departure in their FMC they can no longer select any runway for depature. If they select runway first, then the FMC says that there are now SIDs available.So, we looked at the 602 .xml file for KBWI and noted that the word 'all' is used to define what runways are available for the SWANN3. So we tried another airport that had 'all' specified for available runways for a SID, namely KSTL, CARDS7 dep. Same thing occured.It appears that the Level-D FMC interprets the world 'all' to mean 'none' instead. So we edited the KBWI .xml file to list all of the runways and that works. But that's impractical to do for all airports that have SIDs serving all runways. Any ideas on how to solve this?BTW the route was KBWI SWANN3 OOD J42 RBV J222 JFK ORW3 KBOSThanks.

Hi Dave.This is a known problem that has a note about it in the LDS procedures readme file. I don't have a cure at this time but I have written to LDS about it. They told me that it is a bug that they will fix, when I don't know. I have been told by one user who wrote me that if you change the word "ALL" to lowercase "all" it will fix the problem if you want to give that a try. I'll contact LDS again and see what's up as the problem apparently was not fixed by SP3.Thanks for reminding me about this.RegardsTerry

Thanks so much Terry;I thought as much, and I'll pass this along. We'll try the "all" trick and hope for a fix from LDS. Thanks again for your response and for your work on making these files for all of us.

Just an update Terry;Changing "ALL" to "all" makes no difference. Oh well.

Well, nuts. Ok then, thanks for testing that.RegardsTerry