zlsa / atc

https://openscope.co/
342 stars 107 forks source link

Dangerous approach outside the command area #774

Closed panther2 closed 7 years ago

panther2 commented 7 years ago

Experienced on EDDH today: 1

eliuuk commented 7 years ago

How often are you seeing these?

On 30 December 2016 at 16:46, P@nther notifications@github.com wrote:

Experienced on EDDH today: [image: 1] https://cloud.githubusercontent.com/assets/20812775/21568800/cdd2d656-ceb7-11e6-86c8-cbb2100c3793.gif

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/zlsa/atc/issues/774, or mute the thread https://github.com/notifications/unsubscribe-auth/ASgmWJuTW-Q6Pf6YSOBv4wH1tL5zcq0Gks5rNTVLgaJpZM4LYR1j .

panther2 commented 7 years ago

I noticed it the first time today... did not play for long, though...

eliuuk commented 7 years ago

In that case, it can be fixed through airport design by adding an offset - isn't particularly major though, so I'll fix that some time in the first weeks of 2017.

scott-j-smith commented 7 years ago

I think I've seen this at other airports since 3.2.0 was merged too (possibly EDDF?) - might have affected the airport arrivals algorithm? If I see it anywhere I'll post the details here.

erikquinn commented 7 years ago

The most likely cause is the way the arrivals are arranged in the airport file. A few things to point out to that end:

erikquinn commented 7 years ago

The ATC repository is being migrated to it's new home at https://github.com/openscope/openscope, and thus, all issues are being closed. If this is still an issue with the latest version of the sim (accessible at http://www.openscope.co), or is a feature you still think we are lacking, please reopen the issue at the new repo.

Please note that the vast majority of these issues have been copied to the new repository, or else are covered by other issues created there. See the below screenshot for what it looks like when your issue is known in the new repo:

image

Thank you!

Closing this issue.