Montreal CYUL ILS data downloaded with TerraSync

[TheEagle]

Okay. Actually, someone should run that script on the TerraSync server's Objects folder …

[MariuszXC]

That is what I am saying. It apparently is a runway-by-runway priority.

Sorry to bring the topic back, but I am actually surprised that you confirmed everything as working correctly.
What happens for me with my example modification is that a new ILS for RWY11 appears on a map, can be tuned to and flown, but... instead of leading to threshold of RWY11 it leads to threshold of RWY29, just from the other direction.

So my question is, what I did wrong in my test example?

Could someone with the required knowledge please have a look and explain, what is missing and why?
(just to recap, the example test lives here: https://github.com/MariuszXC/GDN-ILS )

[TheEagle]

Remove the NavData folder - all you need is the Airports/E/G/P/EGPD.ils.xml which must (I think) contain the ID of the already existing ILS. The Terrain folder isn't needed either, I think.

[polly]

They both look OK to me after symlinking both the nav and airport folders to my local scenery folder. The ILS for R11 is, as you say, where it should be: close to R29 threshold, at the far end of R11 upon landing.

[MariuszXC]

But the 'stock' ILS for RWY29 leads an approaching plane to the RWY29 touchdown zone (as expected), while my 'addon' ILS for RWY11 does not lead to the RWY11 touchdown zone, but to the opposite end of the runway. So I obviously did something wrong.
Tested with C172p and C182s.

[SurferTim]

Sounds like you have the GS in the wrong location.
The localizer is on one end of the runway, and the GS and DME should be on the other.

[polly]

That's right, in the additions to nav.dat the GS for ILS 11 is located at the same placw as ILS 11.

[SurferTim]

From my experience, I place the GS location on the runway just as I approach the VASI lights. That way they will show 2 red & 2 white on final approach.

[MariuszXC]

Ahh.. yes, for some reason I misinterpreted the antenna layout. Fixed (although not perfect yet - GS seems to be too high). Will experiment more.

[SurferTim]

The GS elevation makes a difference. Sometimes I cheat and adjust the elevation to get the GS angle & position correct. Plus or minus 10' usually does it.

Edit: The elevation is the number following the lat/lon in your nav.dat file.
Landing too long with VASI white, subtract 10'
Landing too short with VASI red, add 10'

That is why I recommended setting the GS position as you approach the VASI lights. You want them synched all the way down. On the GS, two white, two red.

BTW, before you jump me, I use VASI and PAPI interchangeably.

[MariuszXC]

Thanks Gentlemen, I tweaked elevation values a little and it seems to be about right.
Also added OM and MM.

Re EPGD being underdeveloped I agree. Some time ago I have built a new layout from current XPlane gateway files and it is _much_ better, however I did not have elevation data used by WS2.0, so the AP is at level zero. Still, a nice preview of what it will be some day..