XSG-10995
Airport Vehicles on taxiways, runway and grass surface
Closed
Scenery bug report
Reported by:
FatihKoz
on October 19, 2020 11:09 AM
Assigned to:
Gateway Community
Reported by:
FatihKoz
on October 19, 2020 11:09 AM
Assigned to:
Gateway Community
HAYRİ BÜBERCİ October 19, 2020 7:20 PM
I tested the scenery 2 days ago after reading your post in the forums by doing a 10 nm approach towards RWY 36 and could not see a single ground traffic vehicle wandering over the grass, roaming around approach lights or crossing the runway/taxiway. There is a gT parking beside the VIP terminal and all traffic routes head towards Westerly direction. I have no ground traffic route set around RWY 18, only on Apron 1 which is 1.5 km away from RWY 18. Pls make sure that you have only one LTFM scenery in your Custom scenery folder. The old version had a traffic route along taxiway G in North/South direction and entered Apron 1 before ARFF building. Whole route was removed in the latest version.
FatihKoz October 21, 2020 10:05 PM
Hi, I have no other sceneries for LTFM installed (tested some non Gateway sceneries but not using them). I had no problems while approaching Rwy36 , ground traffic only appears while approaching Rwy18 from north (published 1B STARs was used from both west and east). Thanks again for your efforts, this may be a problem from my end, since the traffic is harmless I can accept their existence
HAYRİ BÜBERCİ November 9, 2020 5:19 PM
I will do some more tests tomorrow by approaching from North. I must remind you that there is a service vehicle parking area right after the taxiway H, towards the West of the VIP Terminal. The (ground) traffic you are seeing might be those that are using the parking lot. I will check whether they are moving out of their routes or not.
Jan Vogel March 12, 2021 7:11 AM
HBuberci uploaded a new version that may fix this - we will check again when it is injected into XPlane with one of the next updates. I will leave this report as “in progress” until then.
Jan Vogel August 30, 2021 5:54 AM
This should be fixed now.