Problems with showing approaches

[FlyingAxx]

Hello Tim,

Probably you can help me to understand what is going on. Triggert by the tread regarding the airport Comiso (LICB) I build it in ADEX. Now I'm in trouble to add the proper approaches. They are looking well in ADEX but crippled in Plan-G. The problem is that I do have no idea what I can do to bring both in line.

The attached picture shows ILS to Rwy 05 with missed approach. The XML looks like this:

Code Select Expand


<Approach
   type="ILS"
   runway="05"
   designator="NONE"
   suffix="0"
   gpsOverlay="FALSE"
   fixType="VOR"
   fixRegion="LI"
   fixIdent="COM"
   altitude="706.0F"
   heading="50.1"
   missedAltitude="5000.0F">
   <ApproachLegs>
      <Leg
         type="IF"
         fixType="VOR"
         fixRegion="LI"
         fixIdent="COM"
         altitudeDescriptor="+"
         altitude1="5000.0F"
         altitude2="5000.0F"
         />
      <Leg
         type="HF"
         fixType="VOR"
         fixRegion="LI"
         fixIdent="COM"
         turnDirection="R"
         magneticCourse="257"
         time="1"
         altitudeDescriptor="A"
         altitude1="5000.0F"
         />
      <Leg
         type="FD"
         fixType="VOR"
         fixRegion="LI"
         fixIdent="COM"
         turnDirection="L"
         recommendedType="VOR"
         recommendedRegion="LI"
         recommendedIdent="COM"
         theta="0"
         rho="0.0N"
         magneticCourse="249"
         distance="9.0N"
         altitudeDescriptor="+"
         altitude1="3000.0F"
         />
      <Leg
         type="DF"
         fixType="TERMINAL_WAYPOINT"
         fixRegion="LI"
         fixIdent="IF"
         flyOver="FALSE"
         turnDirection="L"
         altitudeDescriptor="A"
         altitude1="3000.0F"
         />
      <Leg
         type="TF"
         fixType="TERMINAL_WAYPOINT"
         fixRegion="LI"
         fixIdent="FAP"
         turnDirection="L"
         recommendedType="TERMINAL_WAYPOINT"
         magneticCourse="48"
         distance="9.0N"
         altitudeDescriptor="A"
         altitude1="3000.0F"
         />
      <Leg
         type="CF"
         fixType="TERMINAL_WAYPOINT"
         fixRegion="LI"
         fixIdent="MAPT1"
         flyOver="FALSE"
         theta="0"
         rho="0.0N"
         magneticCourse="48"
         distance="6.0N"
         altitudeDescriptor="+"
         altitude1="1145.0F"
         />
   </ApproachLegs>
   <MissedApproachLegs>
      <Leg
         type="CR"
         turnDirection="L"
         recommendedType="VOR"
         recommendedRegion="LI"
         recommendedIdent="COM"
         theta="270"
         magneticCourse="240"
         distance="0.0N"
         altitude1="4000.0F"
         />
      <Leg
         type="CA"
         magneticCourse="270"
         altitudeDescriptor="+"
         altitude1="4000.0F"/>
      <Leg
         type="DF"
         fixType="VOR"
         fixRegion="LI"
         fixIdent="COM"
         flyOver="FALSE"
         turnDirection="L"
         altitudeDescriptor="A"
         altitude1="5000.0F"
         />
      <Leg
         type="HF"
         fixType="VOR"
         fixRegion="LI"
         fixIdent="COM"
         turnDirection="R"
         magneticCourse="257"
         time="1"
         altitudeDescriptor="A"
         altitude1="5000.0F"
         />
   </MissedApproachLegs>


I did not copy the Transitions.

The second attachment shows the result in Plan-G. To say it clear, I've build more than 200 airports with ADE but never tried to include the approaches. Therefore it's quite a beginner's question. Probably you can help me finding what to do that Plan-G shows what is intended.

Regards,
Axel

P.S.: Due to the reported problems I'm still (back) on version 3.0.3.56

[tim arnot]

Yes it looks like it's doing something wrong - on the face of it the initial track out of the hold appears to be wrong and the turn onto missed looks like it's 90 degrees out of phase. I'll look into it, but it's a long time since I delved into the Approach code, so I'll have to re-orient myself, and it's not something I can do in a quick half-hour. (i.e., it won't be this weekend)

[FlyingAxx]

Hi Tim,

Please let me know if you would like to have the airport code (or the BGL'S) for testing. I publish almost nothing as most stuff I'm doing is just the better adoption of usually elevated runways to FS' flat limitations and that's done as freeware. In this case others already published something on AVSIM (even if I don't know if they included approaches).

Regards,
Axel

[tim arnot]

The bgls would certainly be useful, thanks.

[FlyingAxx]

Hi Tim,

You've got the package (as I would put it on AVSIM).

Regards,
Axel

[tim arnot]

Thanks Axel.

[FlyingAxx]

Hi Tim,

Next chapter. ???

I posted the same problem in the FS Developer Forum and got some valuable hints. Even if I still believe that there might be something with your software I'll rewrite the approaches by following the directions I got there. They told me to start any approach routine straight and simple at FAF, followed by the missed approach section and assigning the first hold and turn at COM after coming from the initial STAR legs to the TRANSITION section.

If there are new findings I'll come back to you.

Regards,
Axel

[tim arnot]

I'm always ready to accept there may be problems rendering approaches - that code was always experimental, and never really polished (it isn't an IFR planner after all... ;))