Are you using Developer Mode or made changes in it?
No
Brief description of the issue:
With Navigraph loaded, the ILS 31 signal at KSNS only has a range of 20 nm, and the glideslope has a range of 15 nm. Those are insufficient to fly the approach. Richard from Navigraph and Matt from Working Title have both spent a fair amount of time looking into this issue but the root cause is not yet clear. Navigraph believes they’re providing the correct localizer and glideslope ranges. Matt confirmed that the simulator currently computes the glideslope range as around 75% of the localizer range. Richard thinks the sim is using the smaller of the two provided values as the localizer range.
With Navigraph disabled, the LOC range is 27 nm, making the GS range about 20 nm which works fine to fly the approach.
Is it possible the simulator is not correctly loading the range values provided by Navigraph?
Provide Screenshot(s)/video(s) of the issue encountered:
The Navigraph discussion is here: KSNS RW31 ILS range too low - ILS - Navigraph
It has several images and other documentation.
Detailed steps to reproduce the issue encountered:
Enable Navigraph, fly the KSNS ILS31 approach using VOR and ILS only. The ILS will not be correct until hitting 20nm from the airport, and the glideslope until 15 nm. Both of those are less than required for the approach.
PC specs and/or peripheral set up if relevant:
High-end PC.
Build Version # when you first started experiencing this issue:
All
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video: