Please tag your post with #pc and/or #xbox.
Are you on Steam or Microsoft Store version?
Are you using Developer Mode or made changes in it?
Brief description of the issue:
Localizers do not have enough coverage in certain cases.
Provide Screenshot(s)/video(s) of the issue encountered:
One example. KORD ILS RWY 10C. Doesn’t become active until just outside PEPAW (~16.6 DME). The localizer in real life extends at least out to BAIRY (25.8 DME). There are numerous other examples at major airports with extended localizers.
Detail steps to reproduce the issue encountered:
Go to virtually any major airport and compare the ILS chart to where the localizer becomes displayed in the cockpit.
PC specs and/or peripheral set up of relevant:
Build Version # when you first started experiencing this issue:
Please note that for most of the localizers in the world, a standard volume is fine, but larger airports (class B and C in the US) usually have numerous localizer courses with what’s known as an “Extended Service Volume”, flight checked to be accurate out to a potentially great distance.
Certain exceptions should be allowed for specific localizer courses to better display localizer course (and associated DME) information accurately.