You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
Brought up by @headphase in #425:
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.
The text was updated successfully, but these errors were encountered: