There is a default (generic) airport scenery for ZLXY in MSFS 2020.
This is shown and can be selected with Asobo/Microsoft Navdata.
When activating Navigraph Navdata the airport scenery is gone on the World Map!
Regards Hans
There is a default (generic) airport scenery for ZLXY in MSFS 2020.
This is shown and can be selected with Asobo/Microsoft Navdata.
When activating Navigraph Navdata the airport scenery is gone on the World Map!
Regards Hans
Hi Hans,
I can confirm this issue, but it is an issue from MSFS2020 - a very tricky one. However, I will try to explain it.
The Airport-Reference-Point (ARP) is incorrect in the stock MSFS 2020 scenery. You see this point on every airport diagram - for ZLXY (red circle):
The stock MSFS2020 scenery is outdated because in MSFS, the runway 05L/23R is marked by the yellow marker, and the ARP (blue circle) is located in a different place.
Now the BGLs organisation works with QMIDs. So, every point in this world is located within such a square (QMID), and that’s the issue here. The “old/outdated” ARP is in another “square” than the real-world ARP.
The old ARP is on 34.4450, 108.7500 (= QMID 307/89):
The real-world ARP is on 34.4550, 108.75 (= QMID 308,89):
You can see the green ILS feather in the screenshots. In the first screenshot, you can see that the ILSes are offset by 05L/23R because this is the MSFS 2020 stock scenery.
The second one is with our data. The runway 05L/23R is aligned with the ILS, and you can also see the blue ARP, which differs from the MSFS 2020 stock scenery.
You can also see this when you enter the coordinates on Google. By the way, here you can clearly see that this runway is new - in the satellite view, it was under construction.
Sorry, but this is a bit too technical; as I mentioned, it is very tricky. The MSFS2020 can´t assign our airport because the airport does not have the same QMID as the stock airport, and that´s because the stock airport uses an outdated ARP.
This is very special and very rare, but it can happen as we see. That is something we cannot handle. This should report to ASOBO/MS that they change the ARP to the correct/real-world one.
Cheers
Richard
Dear Richard,
thank you so much for this excellent explanation of the reasons for the issue. I appreciate that very much.
BTW I was thinking about the ARP but never of the QMID.
And did you make contact to Asobo that they maybe update the stock airport to the “real” thing?
Best Regards Hans
Thank you very much, Hans, for your kind words …
No, please report the outdated airport in the MSFS forum. We can´t really handle/follow up on these reports, so it is better you report this to ASOBO/MS in their forum.
As soon as they have “moved” the runway to the correct position, they must move the ARP to the correct real-world location too.
Thank you,
Richard
P.S.: By the way, this airport is also outdated in MSFS 2024, and the ARP is incorrect. Not helpful, I know, but to show that the MSFS2024 is not much better here ![]()
PPS: Hans, without loosing my respect to you and your age - but I assume, we know each other also nearly 20 years, right? ![]()
Richard,
we do know each other a long time. VATSIM and DAFIF and your engagement of bringing us pilots Navdata! Great time those days but I’m getting old now.
Indeed, but what story - or? Anyways you´re not alone
… I am also 20 years older ![]()
Liebe GrĂĽĂźe aus Wien & Danke!
Richard
Richard,
sorry I have to admit that the old and outdated stock airport of ZLXY is in MSFS 2024 usable with or without Navigraph Navdata. That is not the case in MSFS 2020.
And I think that Asobo/MS will not update the airport as long as there are no actual sattelite pictures to use by Bing. Terminal 5 was opened in Dec. 2024 and maybe the new runway 05L/23R about at the same time. And there is further work on the airport for an other runway.
And I found that Asobo/MS uses the same new ARP as Navigraph and the airport scenery shows up with that.