• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

ILS requiring a rather large curve?

S

SpoorObjecten

Messages
18
Country
netherlands
Hey guys,

Does anyone have any insight on the ILS procedure in FS2020?

My approach looks like this:
1600781792223.png


Which is as expected:
1600781828832.png



However the moment I set the approach to ILS, it suddenly changes my arrival (skipping some points) and creating a huge curve:
1600781879202.png


So it's trying to skip 2 waypoints and go south to then make a rather large curve.

Is this something with my code or is this an FS2020 issue?

<Approach type="ILS" runway="03" fixType="TERMINAL_WAYPOINT" fixRegion="EH" fixIdent="EH583" altitude="1330.0F" heading="35" missedAltitude="5000.0F">
<ApproachLegs>
<Leg type="IF" fixType="WAYPOINT" fixRegion="EH" fixIdent="EH573" recommendedType="LOCALIZER" recommendedRegion="EH" recommendedIdent="EHZ" theta="35" rho="6.1N" altitudeDescriptor="I" altitude1="2000.0F" altitude2="2000.0F"/>
<Leg type="CF" fixType="TERMINAL_WAYPOINT" fixRegion="EH" fixIdent="EH583" flyOver="FALSE" recommendedType="LOCALIZER" recommendedRegion="EH" recommendedIdent="EHZ" theta="35" rho="6.0N" magneticCourse="35" distance="4.0N" altitudeDescriptor="A" altitude1="1330.0F"/>
<Leg type="CF" fixType="RUNWAY" fixRegion="EH" fixIdent="RW03" flyOver="TRUE" recommendedType="LOCALIZER" recommendedRegion="EH" recommendedIdent="EHZ" theta="35" rho="1.4000000000000001N" magneticCourse="35" distance="0.2N" altitudeDescriptor="A" altitude1="26.0F"/>
</ApproachLegs>
 
Did you have to hand code the approach and pattern somewhere deep in the files? I assume so as I can't find any option in the SDK. All of the airports I've done are all over the place as I can't figure this out.
 
Try to add a WPT before <Leg type="IF" fixType="WAYPOINT" fixRegion="EH" fixIdent="EH573",
Exampel <Leg type="TF" fixType="WAYPOINT" fixRegion="EH" fixIdent="CRSUL"
Note Waypoint must be exist in sim.
 
I tried that as well but still didn't want to do a straight line up :(
On the arrival I now end up at EH573, but still skips a few points for the ILS and makes this weird curve

<Arrival name="SOPVI">
<EnrouteTransitions>
<EnrouteTransitionLegs>
<Leg type="IF" fixType="WAYPOINT" fixRegion="EH" fixIdent="SOPVI"/>
<Leg type="TF" fixType="WAYPOINT" fixRegion="EH" fixIdent="EH586" flyOver="FALSE" magneticCourse="0.0"/>
<Leg type="TF" fixType="WAYPOINT" fixRegion="EH" fixIdent="EH587" flyOver="FALSE" magneticCourse="0.0"/>
<Leg type="TF" fixType="WAYPOINT" fixRegion="EH" fixIdent="SOMEM" flyOver="FALSE" magneticCourse="0.0"/>
</EnrouteTransitionLegs>
</EnrouteTransitions>
<CommonRouteLegs>
<Leg type="IF" fixType="WAYPOINT" fixRegion="EH" fixIdent="SOMEM" altitudeDescriptor="+" altitude1="6000.0F"/>
<Leg type="TF" fixType="WAYPOINT" fixRegion="EH" fixIdent="EH588" flyOver="FALSE" magneticCourse="0.0" altitudeDescriptor="+" altitude1="4000.0F"/>
<Leg type="TF" fixType="WAYPOINT" fixRegion="EH" fixIdent="MITSA" flyOver="FALSE" magneticCourse="0.0" altitudeDescriptor="+" altitude1="4000.0F"/>
<Leg type="TF" fixType="WAYPOINT" fixRegion="EH" fixIdent="ERSUL" flyOver="FALSE" magneticCourse="0.0" altitudeDescriptor="+" altitude1="4000.0F"/>
</CommonRouteLegs>
<RunwayTransitions>
<RunwayTransitionLegs number="03" designator="NONE">
<Leg type="IF" fixType="WAYPOINT" fixRegion="EH" fixIdent="ERSUL" altitudeDescriptor="+" altitude1="2100.0F"/>
<Leg type="TF" fixType="WAYPOINT" fixRegion="EH" fixIdent="EH573" flyOver="FALSE" magneticCourse="0.0" altitudeDescriptor="+" altitude1="2000.0F"/>
</RunwayTransitionLegs>
</RunwayTransitions>
</Arrival>


<Approach type="ILS" runway="03" fixType="TERMINAL_WAYPOINT" fixRegion="EH" fixIdent="EH583" altitude="1330.0F" heading="35" missedAltitude="5000.0F">
<ApproachLegs>
<Leg type="IF" fixType="WAYPOINT" fixRegion="EH" fixIdent="EH573" recommendedType="LOCALIZER" recommendedRegion="EH" recommendedIdent="EHZ" theta="35" rho="6.1N" altitudeDescriptor="I" altitude1="2000.0F" altitude2="2000.0F"/>
<Leg type="CF" fixType="TERMINAL_WAYPOINT" fixRegion="EH" fixIdent="EH583" flyOver="FALSE" recommendedType="LOCALIZER" recommendedRegion="EH" recommendedIdent="EHZ" theta="35" rho="4.0N" magneticCourse="35" distance="4.0N" altitudeDescriptor="A" altitude1="1330.0F"/>
<Leg type="CF" fixType="RUNWAY" fixRegion="EH" fixIdent="RW03" flyOver="TRUE" recommendedType="LOCALIZER" recommendedRegion="EH" recommendedIdent="EHZ" theta="35" rho="1.4000000000000001N" magneticCourse="35" distance="0.2N" altitudeDescriptor="A" altitude1="100.0F"/>
</ApproachLegs>
 
That 'curve' is reasonably prototypical in terms of what the aircraft will fly. The IF is not a 'fly-over' fix, so the ILS intercept path doesn't have to go over it. The fact that the approach also misses the MITSA waypoint is, I suspect, because MSFS assumes a certain radius of turn to intercept the ILS, and that's the geometry it comes up with. In real life, and assuming approach speeds prior to the FAF of about 180kts, I'd have expected a turn radius of around 2-3 nm, so MSFS is overdoing it somewhat!
 
Then you have to create transition.
Addd missing leg in the approach, is absolutely necessary.
 
You must log in or register to reply here.
Back
Top