ADE ILS Help

[lingyuan.he]

Hi,

Sorry for the one-after-one threads, but I am really frustrated with the first airport of mine. The ILS simply won't work. It is shown on the map, the identification code IXU can be interpreted by the ILS on board, but the localizer and glideslope won't appear. Note that I have tried to change the frequency. Also note that the airport is brand new (not stock) and over 50NM away from the nearest airport.

In the game:

The XML:

<Approach
type="ILS"
runway="35"
designator="NONE"
suffix="0"
gpsOverlay="FALSE"
fixType="TERMINAL_WAYPOINT"
fixRegion="ZY"
fixIdent="FF35"
altitude="750.0M"
heading="337.76"
missedAltitude="750.0M">
<ApproachLegs>
<Leg
type="IF"
fixType="TERMINAL_WAYPOINT"
fixRegion="ZY"
fixIdent="FF35"
altitudeDescriptor="+"
altitude1="792.48M"
/>
<Leg
type="CF"
fixType="TERMINAL_WAYPOINT"
fixRegion="ZY"
fixIdent="FD35"
flyOver="FALSE"
theta="0"
rho="0.0M"
magneticCourse="347.76"
distance="7408.0M"
altitudeDescriptor="+"
altitude1="792.48M"
/>
<Leg
type="CF"
fixType="RUNWAY"
fixRegion="ZY"
fixIdent="RW35"
flyOver="FALSE"
theta="0"
rho="0.0M"
magneticCourse="347.76"
distance="11112.0M"
altitudeDescriptor="A"
altitude1="168.44M"
/>
</ApproachLegs>
<MissedApproachLegs>
<Leg
type="CF"
fixType="TERMINAL_WAYPOINT"
fixRegion="ZY"
fixIdent="FD17"
flyOver="FALSE"
theta="0"
rho="0.0M"
magneticCourse="0"
distance="0.0M"
/>
<Leg
type="DF"
fixType="VOR"
fixRegion="ZY"
fixIdent="SRT"
flyOver="FALSE"
/>
</MissedApproachLegs>
</Approach>

The Approach Design:

The Airport:

ILS Settings:

Approaches:

Another wired problem at the northern part of the ramp:

I attach the ade here, any other comments are welcomed, too.

Thanks a lot!

 

[AFTRS]

For some reasons FSX wants the fix ident in the approach def to be the FAF.
So may be that one might work:
Set the initial Fix ident in the approach to FD35.
IAF = FF35
FAF= FD35
In the FAA handbook it is defined as You did it )
Christian

 

[glottis]

I also notice you have no heading and distance for the missed approach on the CF leg,
probably why you have a red dashed line

 

[jvile]

I checked your attached project file and the ILS works fine. The localizer is off the center line of the runway a small amount but the radio is receiving it. Do you have any other airports in the area that could have the same ILS frequency?

As stated in AFTRS post your IAF and FAF are backwards. This does not have any affect on the ILS but ATC will see it as a small problem.

 

[Orange]

Just a minor note. I see you have set the ILS range to 30nm. FS will ignore this as the max range is 27nm, hard-coded into FS. I am told that this reflects real life.
Jon, rather than let people think this value can be set to whatever they wish, might it be an idea to "cap" this box to 27nm?

 

[scruffyduck]

Just a minor note. I see you have set the ILS range to 30nm. FS will ignore this as the max range is 27nm, hard-coded into FS. I am told that this reflects real life.
Jon, rather than let people think this value can be set to whatever they wish, might it be an idea to "cap" this box to 27nm?

I've made a note Dave.

PS - I see you are settled in Newtown. As you can probably work out we moved from Llangurig a couple of month ago. We are near Denbigh but may well be back in the NT area

 

[jvile]

Just a minor note. I see you have set the ILS range to 30nm. FS will ignore this as the max range is 27nm, hard-coded into FS. I am told that this reflects real life.
Jon, rather than let people think this value can be set to whatever they wish, might it be an idea to "cap" this box to 27nm?

Dave

For information the following is a little code reading, a whole lot of testing over the yrs. since FS2004 was released and why ADE uses 30 NM's.

Many values in the XML are not carved in stone.

The default LOC is 27 nautical miles if not specified as per the SDK. MS elected to use this value in the decompiled XML as far as we can tell but that does not mean we cannot set it to a higher value.

Many Localizers are not the same when it comes to the range set. In all our testing during the development days of Add-a-Gate, AFCAD and the last 5 yrs with ADE it was decided to use 30NM's since many localizers (in FS) around the world may work at that value. But, there is more to it then that.

I randomly pick a airport with ILS /DME and my picture shows the Localizer coming alive at 30.4 NM's from the far end of the runway (DME is co-located with LOC antenna not the GS).



Even if the range is left at the default of 27NM then at many airports the LOC does not come alive until a much lesser range. It all boils down to what happens in post .dll instead of pre .dll (compiled bgl after it is passed to a FS Engine).

Don't confuse any of what the LOC range does when looking at the GS range. GS range is a percentage of LOC range but then again what we see at one ILS DME runway we may not see at another.

In this picture the same LOC that comes alive at 30.4 NM causes the GS to come alive at 21.9 NM. The GS always lags behind so many NM's when the Localizer comes active. You can find many ILS DME's where the GS lags and then comes alive from 15-25 NM.



In all the code reading and testing since the early days of Add-a-Gate, AFCAD and now ADE the 30 NM is based on what FS will do. The actual range in FS for many localizers is 30 - 31 NM so I ask Jon to code ADE with a cap of 30 NM in the early development stages.