ILS flags offset at Zurich airport

[earnorbust]

Like your Vancouver and Basel airports (which you fixed), the ILS frequency flags pointing to the runways with ILS are offset at the Zurich airport too. You are still using the true heading (as in FSX) instead of the magnetic heading, needed in MSFS. I don't understand, why such a fine airport developer like Virtuali allows the same mistakes on later and newer products. 

Please fix this.

best regards
Robert

[lonewulf47]

Like your Vancouver and Basel airports (which you fixed), the ILS frequency flags pointing to the runways with ILS are offset at the Zurich airport too. You are still using the true heading (as in FSX) instead of the magnetic heading, needed in MSFS. I don't understand, why such a fine airport developer like Virtuali allows the same mistakes on later and newer products.  

Please fix this.

best regards
Robert

Agree! Please use the correct figures as per AIP Switzerland. They even publish the figures as magnetic bearing, just to help you... (although only in full degrees)

LOC14: 135° MAG
LOC16: 153° MAG
LOC28: 274° MAG
LOC34: 333° MAG

Edit: In addition to the beforementioned I found that the coordinates used for LOC28 (47.45747, 8.56658) are wrong. Those are identical to the coordinates for GS28. The coordinates used for GS28 however are the ones for DME28 (GP and DME are identical in your record, in reality they differ slightly)

Find below the decoded RWY record for ILS/DME 28:
LSZH, ILS/DME [BC] MagVar 3.0,  Localizer: 109.75 / IZW / CRS 277° / RW28 / RNG 27.0NM / 47.45747, 8.56658    Glideslope: 3.30° / RNG 27.0NM / 47.45736, 8.56650    DME: RNG 27NM / 47.45736, 8.56650   Name='ILS/DME 28'

Regards
Oskar

[virtuali]

All ILS at Zurich we used the Magnetic heading and, with if you run the FSDT Live Update now, you'll get a fix for the LOC28 in the wrong position, which was in fact a problem in the scenery. We also adjusted a bit the headings too, since the correct Magvar for 2020 is 2.90 degrees East, not 3.00.

About headings, you cannot expect to have the heading perfectly matching the published magnetic heading.

Let's take RWY 16 for example, the published magnetic heading of the approach is 153° degrees. However, if you take Google Earth pro and MEASURE the actual heading from the ENUSO fix to the Localizer, it will give you a True heading of about 155.02, and adding -2.90 for variation, results in a magnetic course of 152.02, so it's not exactly 153° but, if we wanted to show 153, we would have ended up with an ILS not aligned to its real course which, as the approach plate says, runs from ENUSO to the localizer.

And for those wondering, a "perfectly matching the chart" heading of 153° ( 155.9 True, with 2.90 of magvar ) from the localizer to ENUSO, would project to a point about 250 meters East of ENUSO, yes, I just checked that now...

[xsjojo]

Thanks for fixing! Has this update made it to the internal MSFS store as well? I bought the scenery there.

[virtuali]

I'm not sure but, we sent Microsoft all latest versions of all our sceneries during the holidays, so they will surely appear the next time the Marketplace is updated.