The originally reported error message is due to a well know and longer standing bug in X-plane.
There was never any discernable scenery error or anomality found to be causing this bug, nor is there any suspected or even confirmed scenery modification to avoid this bug (lots of rumors though - I personally know two prolific sources of such rumors - every time I dig down into it - I can not find it to be reproduceable even once).
Also, this bug has never been reported to have lead to a crash, nor is the original bug report here really suggest any evidence of correlation between the (bogous) scenery error message and the actual crash.
You can check the (attached) latest AIRAC from Navigraph that the current scenery is outdated. UUEE has currently three runways: RWY 06L/24R (to the northwest of Terminal C; you can see it under construction in Google Maps; this RWY is already in use in the real airport mainly for departure under poor visibility conditions); RWY 06C/24C (formerly the 06L/24R); and the unchanged 06R/24L. This missing RWY was confusing me, because ATC and ATIS tried to direct me to this non-existing RWY using the latest AIRAC from Navigraph.
On fly-in to moscow area, app crash occurs. Log reads:
Traffic flow rule of airport UUEE found in file indicated above refers to an invalid runway. I'm ignoring this rule.
Taxiway of airport UUEE found in file indicated above connects to a non-existing runway. X-Plane cannot build the taxi net. It must be fixed.
--==
{This application has crashed!}==--
--> Reinstall of Scenery Pack 31929 solved the repeating issue.
RandomUser July 28, 2018 2:38 PM
I've tried to fix this based on scenery pack 46433. Please try the attached, modified pack.
RandomUser July 28, 2018 2:40 PM
Since attachments don't seem to work with .zip files, here's a link to GD.
https://drive.google.com/file/d/1qU_1eI6Ninu9YiMmFPnQWHAcLUos8LYv/view?usp=sharing
Michael Minnhaar July 28, 2018 9:23 PM
The originally reported error message is due to a well know and longer standing bug in X-plane.
There was never any discernable scenery error or anomality found to be causing this bug, nor is there any suspected or even confirmed scenery modification to avoid this bug (lots of rumors though - I personally know two prolific sources of such rumors - every time I dig down into it - I can not find it to be reproduceable even once).
Also, this bug has never been reported to have lead to a crash, nor is the original bug report here really suggest any evidence of correlation between the (bogous) scenery error message and the actual crash.
Jan Vogel February 27, 2021 10:37 AM
As per Michaels explanation - this report can be closed.
You can check the (attached) latest AIRAC from Navigraph that the current scenery is outdated. UUEE has currently three runways: RWY 06L/24R (to the northwest of Terminal C; you can see it under construction in Google Maps; this RWY is already in use in the real airport mainly for departure under poor visibility conditions); RWY 06C/24C (formerly the 06L/24R); and the unchanged 06R/24L. This missing RWY was confusing me, because ATC and ATIS tried to direct me to this non-existing RWY using the latest AIRAC from Navigraph.
xplanejunky January 16, 2019 1:55 AM
Please remove the attachment (this was supposed not to be public). Thanks.
xris June 16, 2019 12:30 AM
This can be marked as closed, thanks to scenery pack 67678, which added the missing third runway.
Jennifer Roberts February 23, 2021 3:59 PM
Closing reports that were last updated 1 year ago or more in bug base clean up. These are most likely fixed due to Gateway scenery cuts in that time.
Can not read version 11.30 APT DAT file in this package. Thanks, Kevin
Julian Lockwood July 22, 2019 7:53 PM
This is a third-party product.
нет нумерации гейтов и стоянок
PLS add 10E, 10W, 11E, 11W, 12E, 12W, 13E, 13W stands