fix(atsu/efb): use msfs metar rather than fsx cloud data #8256
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
The FSX cloud data seems to have stopped updating a couple of days ago. Instead we get METARs from the sim with the API that was added a few updates back when the MSFS option is selected.
Screenshots (if necessary)
References
Additional context
Discord username (if different from GitHub):
Testing instructions
Test that METARs work on the EFB home screen and in the ATSU on the MCDU with the MSFS option selected, that they are the current date, and that they match the METAR shown in the VFR MAP. Check one of the other sources e.g. VATSIM to make sure it is still okay as well.
How to download the PR for QA
Every new commit to this PR will cause a new A32NX artifact to be created, built, and uploaded.