ILS Not taking appearing in game after airport build with FS2020 developer

Redoing airport using the 2020 SDK developer. After building the whole airport, the ILS will not show up in the game. There are no build errors shown in the console. The correct package has been copied to the community folder. I have used the deleteAllIlss command when adding the new runway, and verified in the XML file that the ILS deletion is set to “TRUE”. The associated XML for the ILS is shown below.

Any help would be so appreciated.

Thanks

I’m not an expert but I am rebuilding airport EGMH, adding a functional ILS with dmearc approach waypoints and transitions that are good enough for my personal use.

When you say it doesn’t show up in the game, do you mean in the flight planner UI or in the sim? If it’s in the sim, and you tune to the ILS frequency, you don’t see the localiser/glideslope on the instrument panel?

This thread proved useful, would recommend reading: MSFS - Coding xml SIDs/STARs/Approaches - A small tutorial | FSDeveloper

It shows in the planner, because no delete command was selected (see screen shot below). When the ILS frequency is tuned, no response in the aircraft. In the frequencies detail in the Garmin, it just shows 0.00 with no description.
Capture

I have tried changing frequencies in the XML, no luck. I have changed coordinates, no luck. I have tried rebuilding before loading in the editor, no luck.
The DME doesn’t read any distance when the ILS frequency is tuned either.

Unsure of the problem, but I remembered another useful resource; try this video about ILS creation in xml [017] Creating An Airport - Working ATC and ILS - Microsoft Flight Simulator 2020 SDK Tutorials - YouTube

One thing you might want to check is that although the compiler didn’t flag it as invalid, the range parameter in both the GlideSlope and Dme elements, at least on my system I believe to be is a value of miles. So for me I set range=“27.0”. alt values are in meters; you have that at around 2000 which after looking it up, seems to be about right for Durango.

Thanks for the reply. That video is what I’ve used in combination with the runway tool to get the above coding. So frustrating that it works just fine in the video with no problems, and not for this project.

Thanks for the reply. Tried converting all ranges to miles just now, no change at all.

One thing to note (sorry if you know this already) After you save the XML, you have to build. If you hit save scenery (in sim) it will overwrite your ILS info in the XML to whatever the default is.

Thanks for the reply. Yes, I’m aware of this also. I have tried this same scenario with another airport with the same result. I put a request in with Zendesk. to see if they can figure it out, It’s obviously a bug.

Just to clarify: range is in meters, not miles, so make sure you have an appropriate value.

I ran into a similar issue where ILS wouldn’t work when tuned. I believe that when they added ILS support to the scenery editor they put the ILS data under a Runway object, whereas most airports in the game define the ILS data under the Airport object. What I did was copy the ILS data and move it directly under the Airport; note that you will need to remove the end=“PRIMARY” attribute. Then my ILS worked as expected. You can also try loading the XML from the stock airport and work off of that.

Here is the XML that worked for me:

1 Like

Thanks for the reply and help.
I tried this, and it did not work.
I also tried this same formatting and location of the ILS code for the second airport I’m redoing, and same result, no go. I did successfully add an ILS at KCEZ, and airport with no existing ILS to delete. Obviously, this must be related to the deletion of the existing ILS causing a problem.

I have no idea how to load the XML data from the stock airport. A little help with that would be great!

I’ve got a request into Zendesk. Hope for a reply soon.

There are two ways to load the stock airport into XML that I know of:

  1. Official Airport to SDK project: here is a small app to help you (draft) | FSDeveloper
  2. MSFS - Alpha 19 Released | FSDeveloper

me too having the same problem, no matter what I do the default ILS cannot be deleted, anyone has a solution so far ?

Hi All,
Just chipping in. I’m having a similar problem. My custom ILS works fine. However, if a flight is made with an ILS approach in the flight planner, the NAV1 frequency isn’t set as it would be when using a stock airport, and has to be entered manually.
Have zendesk opened a ticket for this bug?
I was reading somewhere that this was affecting some other payware products and they were able to rectify the problem somehow.

I did submit to Zendesk weeks ago. Never heard back from them.

Thanks mate.
I kind of figured this out. The ILS frequency gets set just before the approach and not at the start of the flight. I spent a day trying to fix something that wasn’t broken lol.
What I did find is that if you take off and do an ILS approach from and too the same runway, it often goes a bit strange.

I tried this too, placed the code outside of the runway still inside the airport and I still do not have any ILS at the airport I am modifying (the stock KCRP is missing a runway and doesn’t have the correct approach navaid, it has a LOC instead of an ILS… it’s ■■■■■ and subject of a bug report with Zendesk). The most troubling part is that I had an ILS working and then one day, without any changes to versions, it stopped working. It’s a puzzle!

I got a problem, where I added a fictional ILS to an existing airport: it is showing in MSFS and eg. Little Nav Map as ILS, but in the plane I only see it as “VOR” or “NAV” on my instruments… in planes with analog instrumentation I neverless get a correct ILS HDG & GS (but a green text “NAV”)… in G1000 I only get the visualization of horizontal alignement “dot” in PFD, but NOT THE VERTICAL GLIDESLOPE indicator, and a green text as “VOR”.

where is my fault?

here my code:

		<Runway parentGroupID="1" groupIndex="131" lat="46.94212484925496" lon="8.28361345787442" alt="441.88511382602155" heading="11.77499961853027" length="1656.75891113281250" width="40.34870910644531" patternAltitude="304.79998779296875" falloff="40.000000" surface="{2E0DE83F-B79A-4435-905C-DCBBEAC55C59}" transparent="FALSE" number="01" designator="NONE" primaryLanding="TRUE" primaryTakeoff="TRUE" primaryPattern="LEFT" secondaryLanding="TRUE" secondaryTakeoff="TRUE" secondaryPattern="LEFT" primaryMarkingBias="0.00000000000000" secondaryMarkingBias="0.00000000000000" groundMerging="TRUE" excludeVegetationAround="TRUE">
			<RunwayDeformation alt="443.088898" ratio="0.000000"/>
			<RunwayDeformation alt="440.456055" ratio="0.252998"/>
			<RunwayDeformation alt="440.489594" ratio="0.289051"/>
			<RunwayDeformation alt="440.791443" ratio="0.385704"/>
			<RunwayDeformation alt="438.628174" ratio="0.667991"/>
			<RunwayDeformation alt="435.843292" ratio="1.000000"/>
			<Markings edges="TRUE" threshold="TRUE" alternateThreshold="FALSE" fixedDistance="FALSE" alternateFixedDistance="FALSE" touchdown="TRUE" alternateTouchdown="FALSE" dashes="TRUE" ident="TRUE" leadingZeroIdent="TRUE" precision="FALSE" alternatePrecision="FALSE" edgePavement="FALSE" singleEnd="FALSE" primaryClosed="FALSE" secondaryClosed="FALSE" primaryStol="FALSE" secondaryStol="FALSE" noThresholdEndArrows="TRUE"/>
			<Lights center="MEDIUM" edge="MEDIUM"/>
			<OffsetThreshold end="PRIMARY" surface="{00000000-0000-0000-0000-000000000000}" length="160.000000" width="40.000000"/>
			<BlastPad end="SECONDARY" surface="{052FEFB1-11E3-4951-B5C4-D93CE253FD9E}" length="250.000000" width="40.000000"/>
			<ApproachLights end="PRIMARY" system="RAIL" strobes="1" endLights="TRUE" touchdown="TRUE" snapToGround="FALSE" reil="TRUE" offset="157.550003" spacing="0.010000" slope="0.850000"/>
			<ApproachLights end="SECONDARY" system="MALSR" strobes="1" endLights="TRUE" touchdown="FALSE" snapToGround="FALSE" reil="TRUE" offset="120.000000" spacing="30.000000" slope="0.000000"/>
			<Vasi end="PRIMARY" side="RIGHT" type="PAPI4" biasX="33.121906" biasZ="709.902527" spacing="10.000000" pitch="5.000000"/>
			<Vasi end="SECONDARY" side="LEFT" type="PAPI4" biasX="34.306339" biasZ="873.448059" spacing="9.000000" pitch="4.000000"/>
			<Ils lat="46.93713299996048" lon="8.28483299999906" alt="445.01044868491590" end="PRIMARY" range="92631100.69526401162148" ident="IBRU" magvar="357.579987" heading="25.95999908447266" frequency="109.05000000000000" width="5.000000" name="ILS RW01" backCourse="FALSE">
				<Dme lat="46.93746690715382" lon="8.28358532458881" alt="446.50234171561897" range="92631100.69526401162148"/>
				<GlideSlope lat="46.93743649143347" lon="8.28366495940255" alt="446.52000354137272" pitch="5.000000" range="92631100.69526401162148"/>
			</Ils>
			<RunwayStart end="PRIMARY" lat="46.93507270243640" lon="8.28147545698715" alt="441.88705891836435" heading="11.86943817138672"/>
			<RunwayStart end="SECONDARY" lat="46.94912439187265" lon="8.28571870294762" alt="441.98283757921308" heading="191.86933898925781"/>
		</Runway>
  • I also tried to insert a additional -Tag in the main -section, as showed in the SDK sample for NavData… therefore the compiler did not work (Error with Tags)
  • I added later a range = for Glideslope, with same value as sample… but no improvement

thank you for your help!

best wishes,
Francis

PD: maybe some of you have a functional ils with correct HDG, GS and DME, and can put it here as example?

And finally I found the solution for my issue!!!
in another forum they talked about valid ILS Frequency, so not only the Freq. Range but also only some freq. are used for a correct ils(/dme/gs):
https://www.fsdeveloper.com/forum/attachments/4-3-5-vhfuhf-plan-for-aeronautical-radionavigation-pdf.87754/
in
MSFS - MSFS2020 New Airport Glideslope and DME setting problem | FSDeveloper

maybe this info is usefull for others!