Do you have any add-ons in your Community folder? If yes, please remove and retest before posting.
No
Are you using Developer Mode or made changes in it?
No
Brief description of the issue:
A few updates ago, one of the notes in the Release Notes was “Localizer offset for runways where ILS Localizer Heading is significantly different than the runway heading.”
This was not aggressive enough:
- Nice (LFMN) has an offset ILS approach for runway 04R. This offset heading isn’t shown in the sim when the ILS is tuned and flown. However, the ILS will line you up in between both runways.
- Detroit Metro (KDTW) has two ILS approaches to 22R (111.95 is aligned with the runway for normal operations, 111.75 is offset by 2.5 degrees when parallel operations to runway 22L are also active). In the sim, however, both localizers share the same heading. However, 111.75 will line you up to the left of the runway.
- Salt Lake City (KSLC) also has a similar issue for the LDA runway 35; the localizer is supposed to be offset 5.04 degrees for terrain and airspace avoidance. However, the localizer is perfectly aligned with the runway, yet transposed a few dozen feet to the left (i.e., where the actual Localizer antenna is).
It is clear in this instance that the localizers are positioned correctly geographically relative to their real world counterparts. However, their headings are not polled from nav data, but from the runway they’re associated with. This is simply incorrect.
Provide Screenshot(s)/video(s) of the issue encountered:
Just one picture; it’s an ordeal documenting these situations in pictures
Detail steps to reproduce the issue encountered:
Fly to an airport with an offset ILS approach of 1-2 degrees
Set up the approach in the GPS/FMS/etc.
Fly it using the localizer signal (NAV instead of FMS)
Note the following issues:
- Aircraft isn’t where it should be
- GPS shows a different position for the localizer
PC specs for those who want to assist (if not entered in your profile)
- Ryzen 7 3800X
- RTX 2080 SUPER
- Windows 10
Build Version # when you first started experiencing this issue:
1.7.12.0; this was never resolved since day 1 for small offsets like this; just the major ones like KDCA.
Are you on the Steam or Microsoft Store version?
Steam
Did you submit this to Zendesk? If so, what is your ticket #?
#109576