When vectored direct to runway 01L into a direct headwind. There were two aircraft taking off directly into me. I was landing directly into a headwind. Also, when vectored and requested to report field in site, the controller repeated a previous heading and then stated I was not following ATC. This was about 3 miles from the runway on final approach. I hope reporting this here helps the community. If this is the wrong place to post bugs please let me know!
IMO it is a seriously misauthored flow: At night 19R departures and 01L arrivals => opposing traffic on same runway. Also all outbound headings were set to 0 degree's, no departure frequencies set (i.e. at 133.0 default), pattern runways not matching any active runway, wind rules allowing 20 kn tailwinds. I just submitted my attempt to fix it to the gateway.
roncondor,
the new flow got accepted. Can you please download the airport and test if the ATC now works as you expected ? I'm curious if the outbound heading updates also solve your strange vectoring around ... Can you also test with 10.50rc2, as the ATC has some updates in that version.
I tried loading the KMKE package with XP11. Upon loading I got a LR error message that some files were missing. I'm assuming this is not a XP12 pack and only meant for XP11? I expected the scenery to load with XP11
When vectored direct to runway 01L into a direct headwind. There were two aircraft taking off directly into me. I was landing directly into a headwind. Also, when vectored and requested to report field in site, the controller repeated a previous heading and then stated I was not following ATC. This was about 3 miles from the runway on final approach. I hope reporting this here helps the community. If this is the wrong place to post bugs please let me know!
Jennifer Roberts August 12, 2016 12:55 PM
This sounds like a bug with ATC, not necessarily with the scenery pack. What version of X-Plane are you using? There are some ATC fixes in 10.50.
An unknown user August 18, 2016 3:26 PM
IMO it is a seriously misauthored flow: At night 19R departures and 01L arrivals => opposing traffic on same runway. Also all outbound headings were set to 0 degree's, no departure frequencies set (i.e. at 133.0 default), pattern runways not matching any active runway, wind rules allowing 20 kn tailwinds. I just submitted my attempt to fix it to the gateway.
Michael
An unknown user August 18, 2016 3:35 PM
Its a WED 1.4 submission, but it also passed the ATC checks in WED 1.5 with last nights version from git, so it must be good
An unknown user August 23, 2016 10:23 AM
roncondor,
the new flow got accepted. Can you please download the airport and test if the ATC now works as you expected ? I'm curious if the outbound heading updates also solve your strange vectoring around ... Can you also test with 10.50rc2, as the ATC has some updates in that version.
Michael
Michael Minnhaar March 30, 2018 11:37 AM
Re-validated old scenery with WED 1.7.0 and it properly flags the original faulty flow. Current recommended gateway airport has good flow.
I tried loading the KMKE package with XP11. Upon loading I got a LR error message that some files were missing. I'm assuming this is not a XP12 pack and only meant for XP11? I expected the scenery to load with XP11
MFD529 January 31, 2023 8:45 PM
Sorry I hit the Close button thinking it was part of the web browser and not specific to the gateway
Jan Vogel February 1, 2023 12:05 PM
No, this airport will only work with XP12.
MFD529 February 1, 2023 6:42 PM
Danke