The default MSFS ILS data for EDDS (Stuttgart) is incorrect and gives an offset ILS approach.
To get around this issue I am using the navigraph ILS data, by setting the “navigraph-navdata” as the last entry in my content.xml file
The (Cat III) ILS is now perfectly aligned. However, there is an issue with the glide slope as it is setting the touchdown zone before the 25 rwy threshold (rendering autoland impossible for the FBW A320)
The screenshot below shows the default Asobo A320 (not FBW) just before touchdown, according to the ILS GS, illustrating where it thinks the touch down zone should be, in the middle of the approach lights prior to the threshold:
Hi,
it looks that this is a scenery issue - I have checked the localizer- and glideslope antenna position from us and the stock data and both are identically. Also the elevation of the antennas - completely equal.
I have also flown this approach with the stock data and it´s the same behavior without our data installed. So, I assume that this must be any other issue but it doesn´t look, that this has something todo with the navdata (stock nor our data). I´m not a scenery designer so I can´t really help here more, sorry.
Yes, I assume also that this has something todo with the runway elevation but as I wrote, I have not enough knowledge to understand what is the exact reason now. I can only check the correct positions and the elevations and all these values are ok so far, but nit only in our data also in the stock data (exclusing the course and the magnetic variation but that has nothing todo with the GS or the touchdown zone).
The Navigraph data is indeed very accurate. However, the threshold elevation at some (add-on) airports is not correct. This problem was much less pronounced in older simulators and seems to go along with the sloping runways in MSFS. I understand that it is impossible for Navigraph to fix all mistakes made by other developers, especially in cases where there are different add-ons for the same airport.
However, this is a BIG PROBLEM in MSFS and should be adressed. On many approaches, I ended up this crutial few feet high or low, wich makes the difference between a pleasent flight and a frustrating one.
The cleanest solution would be to fix the threshold elevation. However, I doubt that this will be addressed by all developers in the near future. Another acceptable solution would be to manipulate the nav data to at least match the glide slope to the wong elevation (none ILS approaches would still end up high/low). Of course this is not ideal, but in most cases it is only a few feet. Not so relevant during the intercept, but crucial on short final.
For FSX and P3D there is a third party navdata editor available which can be used to to fix issues like this. However, I haven’t found anything similar for MSFS. Are you aware of such a tool for MSFS, or could you Richard @NAVData think of providing us with somthing like this? It could be realy basic, but would help to solve one of the biggest problems with MSFS.
