MSFS Sydney erroneous ILS bearings

[george[flytampa]]

Ok, I must stand corrrect. After reading the discussion I had with the other competitor, I see that the issue there was exactly the other way round. He used TRUE courses for the LOCs and thought it would be adjusted by the Variation.

So in the case of YSSY there are onyl two main errors: the wrong course of ILS34L (355° iso 335°) and the GS being zero. Then main problem with localizer bearings however is that obviously noone at Asobo has the faintest clue about Aerial Navigation. I have no idea why they changed the LOC courses to be MAGNETIC. This will cause a few more problems in the future if they are not IMMEDIATELY reverting to the usual method of using TRUE BEARINGS for LOCs (as they do for RWYs anyway). One of the fantastic outcomes of Asobos missing knowledge is the fact that their ARINC parser (whatever Gremlin told them to do so) alignes all LOC bearings strictly to the RWY thus eliminating all OFFSET LOCs worldwide...

I do hope that we get an update for YSSY in reasonable time and I thank you in advance.

Regards
Oskar

So you think the MagVar should be zero again?

[OmniAtlas]

Hi George,

I'm not too sure what needs to be done on the programming side of things, but here is how the ILS is depicted and read with ProSim (Instructor Station) -

ILS_2.PNG (64.17 KiB) Viewed 8732 times

ILS_1.PNG (81.27 KiB) Viewed 8732 times

[lonewulf47]

So you think the MagVar should be zero again?

No, please leave it to the official 13° value. To be honest I only see that all LOCs definitions in RWY records show the correct magnetic variation and show up properly in the A/C's OBS. Just make the corrections on the LOC bearing for RWY 34L (335° iso 355°) and set the GP angle to 3.00° and that's it. I still need to investigate a bit deeper as to what the actual influence of the Magnetic Variation in the RWY record is.

Regards
Oskar

[lonewulf47]

Ok, after doing a few more tests it definitely looks as if the magnetic variation entered in the RWY record is of no importance. It is however a good addition to complete all information of the respective ILS-LOC.

Find below screenshots for all ILs-LOC autotune bearings at YSSY:

YSSY 34R

YSSY_34R.png (143.87 KiB) Viewed 8725 times

YSSY 34L

YSSY_34L.png (137.92 KiB) Viewed 8725 times

YSSY 25

YSSY_25.png (166.13 KiB) Viewed 8725 times

YSSY16R

YSSY_16R.png (150.64 KiB) Viewed 8725 times

YSSY 16L

YSSY_16L.png (99.64 KiB) Viewed 8725 times

YSSY 07

YSSY_07.png (113.51 KiB) Viewed 8725 times

All bearings are correct except for RWY 34L, where it shows the wrong value of 355° iso 335°.

As for the ProSim Instructor Station I strongly presume that ProSim is still calculating the bearing according to the FSX/P3D method, where the bearing should be TRUE and corrected by local variation. So any changes for correct display is ProSim's task.

Regards
Oskar

[george[flytampa]]

Version 1.1 is available for download. Please let me know if it helps out with the ILS.

[XCLTM3]

Version 1.1 is available for download. Please let me know if it helps out with the ILS.

Many thanks George!

I'll do some testing

[John Burgess]

Thanks George,

Just did a very quick check on all the ILS's in the Daher and they now all seem to work as intended in the sim (including 34L).

A word of warning, though, they do look misaligned in programs like Little Navmap (presumably magvar still set to 0).
I am, however, confident that in sim I'm seeing the ILS's from the scenery and that they are working.

All the best,

John

[george[flytampa]]

Hey John. Thanks for the feedback.

The magvar is set to 13 in the update. Something funny is going on :}

[John Burgess]

Hi George.

A nights sleep works wonders!
Just got out my protractor - in Little Navmap the ILS's are displayed at 26 degrees to the runways.
Could it be the magvar is set to 13 degrees in the wrong direction?

Edit. Just Googled it. Magvar for Sydney is apparently 13 degrees East.
Little Navmap is reporting the magvar for the ils as 13 degrees West.

All the best,

John

[george[flytampa]]

Thats possible. Problem still remains I get the stock ILS taking over. Removed content.xml, asobo yssy, and that Utah scenery too.

[John Burgess]

Very strange.

Did you check in the rebuilt content.xml file the point I mentioned that, for me at least,
<Package name="asobo-airport-c53-lowerloon" active="true"/>
needs to be above
<Package name="fs-base-nav" active="true"/>

If it isn't I see the default ILS's.

All the best,

John

[george[flytampa]]

Very strange.

Did you check in the rebuilt content.xml file the point I mentioned that, for me at least,
<Package name="asobo-airport-c53-lowerloon" active="true"/>
needs to be above
<Package name="fs-base-nav" active="true"/>

If it isn't I see the default ILS's.

All the best,

John

Hey John,

Do you know if the LOC is meant to move in realtime if I edit the position in the MSFS project editor? Or does it need a recompile to reflect a change in position.

[John Burgess]

Hi George,

I don't know I'm afraid.

All the best,

John

[OmniAtlas]

Seems to still affect ProSim and the aircraft is unable to capture the glideslope or localiser.

Anyone have a solution?

Screenshot 2021-11-21 201437.jpg (15.17 KiB) Viewed 6880 times