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

Airways entry "NOT ALLOWED" when flightplanning in MCDU #283

Closed
noteas opened this issue Dec 17, 2022 · 8 comments
Closed

Airways entry "NOT ALLOWED" when flightplanning in MCDU #283

noteas opened this issue Dec 17, 2022 · 8 comments
Assignees
Labels
Component: Systems Systems related enhancement New feature or request

Comments

@noteas
Copy link

noteas commented Dec 17, 2022

Dear Contributors of the A320-family Project,

Hi! Recently I have observed a flaw in your model when flying:
1
2

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)
3
As a result, all the waypoints in the airway will be automatically added, liberating our hands:
4

I believe everybody will appreciate it if you fix this soon.

Yours sincerely,
noteas

  • OS: Windows 10 64-bit
  • FlightGear version: 2020.3.17
  • A320 Version: latest
@noteas noteas added the bug Something isn't working label Dec 17, 2022
@merspieler merspieler added enhancement New feature or request Component: Systems Systems related and removed bug Something isn't working labels Dec 17, 2022
@merspieler
Copy link
Collaborator

This is not a bug, it simply hasn't been implemented yet.

@merspieler merspieler changed the title Bug - Airways entry "NOT ALLOWED" when flightplanning in MCDU Airways entry "NOT ALLOWED" when flightplanning in MCDU Dec 17, 2022
@noteas
Copy link
Author

noteas commented Dec 17, 2022

Could you tell me when will this feature be implemented, please?

@noteas
Copy link
Author

noteas commented Dec 17, 2022

OK, I see. Thank you very much!

@noteas noteas closed this as completed Dec 17, 2022
@noteas noteas reopened this Dec 17, 2022
@noteas
Copy link
Author

noteas commented Dec 17, 2022

With my good technical skills, I will do my best to help you on this problem.

@merspieler
Copy link
Collaborator

It will come, when it comes.

If you wanna implement this, feel free to fork and open a pull request.
And we're here to help, if you've got questions about it.

@Octal450
Copy link
Collaborator

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,
Josh

@noteas
Copy link
Author

noteas commented Dec 18, 2022

Got it. Thank you very much. I will turn to FlightGear developers for help.

@noteas noteas closed this as not planned Won't fix, can't repro, duplicate, stale Dec 18, 2022
noteas added a commit to noteas/A320-family that referenced this issue Dec 24, 2022
noteas added a commit to noteas/A320-family that referenced this issue Dec 24, 2022
@noteas
Copy link
Author

noteas commented Dec 24, 2022

Fixed in #284. Closed.

@noteas noteas closed this as completed Dec 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Systems Systems related enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants