-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
fix(a380x/efis): Fix VV pb indicator not turning on when TRK-FPA is selected #9656
fix(a380x/efis): Fix VV pb indicator not turning on when TRK-FPA is selected #9656
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happens if
- You're in HDG/VS, VV is off
- Turn on TRK/FPA, VV turns on
- Press the VV button, VV stays on
- Turn back to HDG/VS
The VV would now be on because L:A380X_EFIS_#SIDE_SIMVAR_GROUP#_VV_BUTTON_IS_ON
was actually toggled while in TRK/FPA, right? Is this expected?
Yes. This is expected behaviour for this PR at this point. Partly because I can't find any docs to confirm if the pb blocking should occur or not. Another because we had a discussion to not complicate the XML logic when i considered blocking the vv pb via the XML. https://discord.com/channels/738864299392630914/747572666780745828/1317287045890048082 If we can confirm that the VV logic should be blocked/changed in the situation which you mentioned, then a FCU logic rewrite would probably need to occur to avoid putting the logic in the XML. Forcing the |
Ok, it makes sense not to worry about it until we know what the logic should be 👍. |
Quality Assurance Tester Report Discord Username : bruno_pt99 Testing Process: Testing Results: Media: 2025-01-09.20-01-41.mp4 |
Please fix the changelog conflict so we can merge 👍 |
@BravoMike99 Changelog conflict resolved |
Fixes #9520
Summary of Changes
Fix VV pb indicator to account for the FPV shown on the PFD when TRK-FPA is selected.
Screenshots (if necessary)
References
Additional context
The testing instructions in #9520 extend into GA mode indications which shouldn't be in the scope of this PR. Will recommend creating a separate issue for fixing GA mode issues if reproduced.
Discord username (if different from GitHub): Heclak
Testing instructions
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.