'To be released soon' is indeed subjective :) FT Las Vegas was also 'coming soon' in December 2018, but released in April 2019. ;) LOL

Really excited about it!

Still having this issue. Is anyone else experiencing the same?

Not behind my PC right now, but next to updating the runway numbers, you will also need to check the runway taxi lines and make sure they reflect to 16/34 as well.

Many thanks Emilios!

Using AI perhaps? If so, check if the issue occurs when putting the AI sliders to 0%... I had a similar issue at LAS and it was caused by one of my AI models.

Everyone is experiencing this, with any payware airport including moving vehicles.. Do not know whether it is a limitation or a decision made for performance for example.

Hi Emilios,

I tried the above file (was already present in my v1.1) but I have still one of these holes left when approaching 26L. Same as on screenshot found here viewtopic.php?f=34&t=13213#p65197

Appreciate your suggestion, but i hope Emilios can fix it in an upcoming release.

I found out that the issue was AI related. After trying out several things it came down to my Las Vegas Sands flightplan. After I substituted the FSPainter A340-500 for a 747SP the issue was solved for me. No clue on how an Ai aircraft can interfere with terrain but my issue is solved. Took me a day...

I may be off base, but I don't think the ATC directly corrolates with add on scenery. Rather the ATC utilizes the default scenery much like the default GPS. You may try https://www.aero.sors.fr which updates the runway identifiers as well as other navaids. Not sure if it will solve the issue or not...

Is also reported in another thread: https://www.flytampa.org/forum/viewtopi ... 34&t=13239

Hi Emilios,

I was flying to Las Vegas and wanted to land on RWY 26L. I requested it via ATC and want to take the ILS 26L. But in the ATC menu the approaches are still listed as 25L and 25R. Can this be fixed in the next update?

Issue solved. Thanks!