fix(fms): more robust navdata error handling and sorting #9774
+150
−108
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #[issue_no]
Summary of Changes
Improve robustness of procedure loading, discard procedures that are missing data rather than discarding entire airports.
Sort the procedures in the A32NX FMS (this is necessary when navdata is coming from multiple sources).
This potentially helps with INTERNAL ERROR, and certainly helps with some navdata issues I've seen.
Screenshots (if necessary)
References
Additional context
Discord username (if different from GitHub):
Testing instructions
Loading some airports in the A32NX, and ensure the procedures work okay (step through in PLAN mode), and that procedures are sorted in order on the arrival and departure pages.
How to download the PR for QA
Every new commit to this PR will cause new A32NX and A380X artifacts to be created, built, and uploaded.