I have been working since mid-December on a modification to the default scenery for KCLT that adds the new runway. I have been using a combination of EZ-Scenery and ADE9x to accomplish this and, after a few setbacks, actually uploaded a file to the AVSIM Library for download by others. 600+ downloads later I have been trying to "tweak" the scenery and provide a better end product.Using ADE9x, I added the ILS NAVAIDS for the new runways (18R and 36L) using data from AirNav for accuracy. The feathers and glideslopes look "spot on" and AI Aircraft use the new runway for departures and arrivals, but one thing that has been pointed out is that the new approaches (I added the ILS and RNAV approaches for 36L and 18R using ADE9x) do not show up in the aircrafts' GPS as selectable approaches. The approaches that were "established" when I added the ILS NAVAIDs do.The new approaches show up in the list of approaches on the "Approach" page in ADE9x, but not in the GPS list of "procedures"Any ideas?Randy

Could you copy out the xml approach data from one of the approaches that isn't showing and post it?scott s..

Scott,Not really sure where to find or extract or create an XML document of the approaches. When I created the approaches, I was in ADE9x. My save file is called KCLT_ADE_RVT.BGL (after compilation). I used XMLSHELL.EXE to create an XML file of that BGL file, It creates an http:\c:\........xml document, but it lists EVERYTHING that was done in the creation of that compilation, taxi signs, objects, runways, etc. However, nothing resembling an approach, even though the fixes for the approach legs are in that document, but not in any particular order.Maybe I'm in over my head...LOL. I sat on the virtual ramp at Charlotte last night and "observed" the default ATC issuing landing and takeoff clearances. Default ATC was using 36C for departures and 36L and 36R for arrivals, just like I would expect RW, so I was happy with that. I should be happy the AI aircraft use the runways and taxiways I created and quit while I'm ahead, but there's a part of me that wants to give people who download my scenery what they want, i.e., an approach in their aircraft's GPS.Randy

In ADE you can go to settings -- options and on the "general" tab check the box for "save xml after compile" and when you compile it will create an xml file of your airport in the same place as the bgl file. But easier for this is to go into approach mode, and select the approach in the lists -- approaches. On the right side click on to highlight the topmost entry (should be something like "R36L:ILS") and right-click to get the context menu, then in the menu select "Show XML". A popup window will show with all the approach xml code. Select all the text in the window and copy it into a post here (might need to enclose in "code snippets" brackets). It will look like this:

<Approach   type="ILS"   runway="36"   designator="LEFT"   suffix="0"   gpsOverlay="FALSE"   fixType="TERMINAL_WAYPOINT"   fixRegion="K7"   fixIdent="GLASI"   altitude="883.92M"   heading="355.962982"   missedAltitude="1524.0M">   <ApproachLegs>      <Leg         type="IF"         fixType="TERMINAL_WAYPOINT"         fixRegion="K7"         fixIdent="NIVSE"         recommendedType="LOCALIZER"         recommendedIdent="IDQG"         theta="183"         rho="12.0N"         altitudeDescriptor="+"         altitude1="1219.2M"         altitude2="883.92M"         />      <Leg         type="CF"         fixType="TERMINAL_WAYPOINT"         fixRegion="K7"         fixIdent="GLASI"         flyOver="FALSE"         recommendedType="LOCALIZER"         recommendedIdent="IDQG"         theta="183"         rho="8.5N"         magneticCourse="3"         distance="3.5N"         altitudeDescriptor="+"         altitude1="883.92M"         altitude2="883.92M"         />      <Leg         type="CF"         fixType="RUNWAY"         fixRegion="K7"         fixIdent="RW36L"         flyOver="FALSE"         recommendedType="LOCALIZER"         recommendedIdent="IDQG"         theta="183"         rho="1.9N"         magneticCourse="3"         distance="6.6N"         altitudeDescriptor="A"         altitude1="229.514M"         />   </ApproachLegs>   <MissedApproachLegs>      <Leg         type="CA"         magneticCourse="3"         altitudeDescriptor="+"         altitude1="487.68M"/>      <Leg         type="VI"         magneticCourse="314"         />      <Leg         type="CF"         fixType="WAYPOINT"         fixRegion="K7"         fixIdent="STANN"         flyOver="FALSE"         recommendedType="VOR"         recommendedRegion="K7"         recommendedIdent="FML"         theta="347.2"         rho="29.51N"         magneticCourse="347"         distance="11.0N"         altitudeDescriptor="+"         altitude1="1524.0M"         />      <Leg         type="HM"         fixType="WAYPOINT"         fixRegion="K7"         fixIdent="STANN"         turnDirection="R"         magneticCourse="167"         distance="5.0N"         />   </MissedApproachLegs>   <Transition      transitionType="FULL"      fixType="VOR"      fixRegion="K7"      fixIdent="CLT"      altitude="1524.0M">      <TransitionLegs>         <Leg            type="IF"            fixType="VOR"            fixRegion="K7"            fixIdent="CLT"            />         <Leg            type="TF"            fixType="TERMINAL_WAYPOINT"            fixRegion="K7"            fixIdent="MARJO"            magneticCourse="0"            altitudeDescriptor="+"            altitude1="1524.0M"            />         <Leg            type="HF"            fixType="TERMINAL_WAYPOINT"            fixRegion="K7"            fixIdent="MARJO"            turnDirection="L"            magneticCourse="3"            time="1"            altitudeDescriptor="+"            altitude1="1524.0M"            />         <Leg            type="CF"            fixType="TERMINAL_WAYPOINT"            fixRegion="K7"            fixIdent="NIVSE"            flyOver="FALSE"            recommendedType="LOCALIZER"            recommendedIdent="IDQG"            theta="183"            rho="12.0N"            magneticCourse="3"            distance="3.2N"            altitudeDescriptor="+"            altitude1="1219.2M"            />      </TransitionLegs>   </Transition>   <Transition      transitionType="FULL"      fixType="TERMINAL_WAYPOINT"      fixRegion="K7"      fixIdent="MARJO"      altitude="1524.0M">      <TransitionLegs>         <Leg            type="HF"            fixType="TERMINAL_WAYPOINT"            fixRegion="K7"            fixIdent="MARJO"            turnDirection="L"            magneticCourse="3"            time="1"            altitudeDescriptor="+"            altitude1="1524.0M"            />         <Leg            type="CF"            fixType="TERMINAL_WAYPOINT"            fixRegion="K7"            fixIdent="NIVSE"            flyOver="FALSE"            recommendedType="LOCALIZER"            recommendedIdent="IDQG"            theta="183"            rho="12.0N"            magneticCourse="3"            distance="3.2N"            altitudeDescriptor="+"            altitude1="1219.2M"            />      </TransitionLegs>   </Transition></Approach>

scott s..

Scott,I thank you for that setting in ADE and really appreciate your help. I feel silly. Turns out there was an errant .bgl file in my KCLT folder that I was testing for someone that I forgot to remove. It was "overriding" my scenery. Once I removed that, the new approaches I added showed up on my default GPS. Lesson learned...always check file contents. Thanks again,Randy

Yup, that can bite you in the butt.scott s..

Randy, installed your KCLT file in FS9 this morning. One word comes to mind,"Outstanding". Did a short hop from KMCO-KCLT in the LD767 and all Navaid data for the approach was in the FMC's database. Just curious if this scenery file will work in FSX also? Thanks again for your excellent work for this addon scenery.