Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flyover Fixes #427

Closed
erikquinn opened this issue Apr 7, 2016 · 1 comment
Closed

Flyover Fixes #427

erikquinn opened this issue Apr 7, 2016 · 1 comment

Comments

@erikquinn
Copy link
Collaborator

Brought up by @headphase in #425:

it would be excellent if we could designate fly-over fixes with a symbol, maybe a hashtag or something? Especially since they are important on these RNAV procedures.

I agree, and think this could further improve SIDs/STARs/IAPs realism. Probably easiest to denote with some character as a flag, perhaps '#', '!', '^', or something. Then we would have the power to decide which method we want the aircraft to use for turning toward the next fix, as does the FAA in real life.

image

@erikquinn
Copy link
Collaborator Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant