-
Notifications
You must be signed in to change notification settings - Fork 43
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
Airways entry "NOT ALLOWED" when flightplanning in MCDU #283
Comments
This is not a bug, it simply hasn't been implemented yet. |
Could you tell me when will this feature be implemented, please? |
OK, I see. Thank you very much! |
With my good technical skills, I will do my best to help you on this problem. |
It will come, when it comes. If you wanna implement this, feel free to fork and open a pull request. |
The problem is in FlightGear not in the A320 - airway support is not working properly yet. I believe it's been discussed on the mailing list but not corrected yet. Kind Regards, |
Got it. Thank you very much. I will turn to FlightGear developers for help. |
Fixed in #284. Closed. |
Dear Contributors of the A320-family Project,
Hi! Recently I have observed a flaw in your model when flying:
Maybe this is a feature request instead of bug report.
As is known to all, A320 MCDU flightplanning, in realism, is to enter LEGS -- airways and waypoints.
Real pilots enters a pair of airway and waypoint, one by one after the last SID waypoint, as follow: (captured from FlightFactor A320 for X-Plane11)
As a result, all the waypoints in the airway will be automatically added, liberating our hands:
I believe everybody will appreciate it if you fix this soon.
Yours sincerely,
noteas
The text was updated successfully, but these errors were encountered: