Hi,
Can you try the same approach with the stock EDDS scenery? I ask because we use the elevation of the stock mesh; possibly, the 3rd party scenery uses other elevation data here.
Thank you
Richard
I can give it a try. But did something change with the latest AIRAC?
There has always been an issue with the ILS being too low when using the default MSFS scenery because the runway elevation in the default Asobo scenery is incorrect.
Aerosoft has since released their version of the airport using the real-world elevation. RWY 25 is now slightly lower, which is correct, and until the latest AIRAC the ILS worked perfectly with that scenery.
However, after updating to the latest AIRAC, I now end up too high on the ILS approach when using the Aerosoft scenery.
If you’re using the default Asobo mesh, the airport elevation is higher, so the updated ILS will now appear to be correct (even though the default EDDS elevation has actually been wrong for the past six years).
The problem is that any scenery using the correct real-world elevation (like Aerosoft) now has an incorrect ILS glide path.
Hi again,
The partially incorrect stock data forced us to set them to default (sim) values, which is now problematic in some 3rd-party scenaries. However, we can’t manage two different elevations, so we had to stick to the default/sim values. Since not every user uses 3rd-party scenaries everywhere, it was obvious to use the stock values.
In simpler words:
The references behind are the stock/sim elevation, comparing the more accurate real-world elevation, which we also have in our database. It is a compromise, sorry for that.
Cheers,
Richard
PS: we have seen that ASOBO/MS won´t/can´t change the elevation globaly, so we must look for a globaly solution.
Hi Richard,
Thanks for the explanation. I understand why you decided to align the data with the stock MSFS airport, since that’s what most users are flying with.
However, it is a bit unfortunate because airports like Aerosoft EDDS, which use the correct real-world runway elevation, worked perfectly with the previous AIRAC. After the latest update, the ILS glide path is now noticeably too high.
The downside is that users who have invested in high-quality payware airports, such as Aerosoft EDDS, are now experiencing problems that didn’t exist before. In my opinion, the situation has actually become worse because the ILS paths have now been adjusted to match the incorrect stock airport elevations instead of the correct real-world elevations.
I understand that maintaining two different elevation references isn’t practical. I just hope a global solution can be found, especially since Asobo doesn’t seem likely to correct the default airport elevations. Otherwise, more and more third-party airports using real-world elevations will end up with incorrect ILS guidance.
Thanks for the clarification, and I appreciate that you’re already looking into a long-term solution.
It has nothing to do with practicality; it is simply not possible. It was a difficult decision for us, too. We only had two options: use the real-world data, associated false glideslopes worldwide, or use the sim data, associated false glideslopes in some 3rd party scenarios. We haven´t found any middle-way and you can´t change this value “on-the-fly”.
I know, a little bit frustrating and also not fair to you. I would also like to apologize for that, but we are not able to fix anything without the help of the underlying systems. I wish you a nice Sunday and again sorry for that “bad” news (at least for the moment).
Cheers,
Richard
