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

fix(a380x/efis): Fix VV pb indicator not turning on when TRK-FPA is selected #9656

Conversation

heclak
Copy link
Contributor

@heclak heclak commented Dec 14, 2024

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)

image

References

image

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

  1. Check that VV pb is off
  2. Press the HDG-V/S/TRK-FPA button to switch to TRK-FPA mode. Check that FPV is shown on PFD and VV pb indicator turns on.
  3. Press VV pb to check that VV pb cannot be turned off while TRK-FPA is selected
  4. Switch to HDG-V/S mode by pressing the HDG-V/S/TRK-FPA button on the FCU. VV pb indicator should turn off.
  5. Press the VV pb to toggle the VV on the PFD. Indicator light on the VV pb should sync with the VV display on the PFD.

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.

  1. Make sure you are signed in to GitHub
  2. Click on the Checks tab on the PR
  3. On the left side, find and click on the PR Build tab
  4. Click on either flybywire-aircraft-a320-neo, flybywire-aircraft-a380-842 (4K) or flybywire-aircraft-a380-842 (8K) download link at the bottom of the page

@heclak heclak marked this pull request as ready for review December 14, 2024 09:54
Copy link
Member

@BlueberryKing BlueberryKing left a 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?

@heclak
Copy link
Contributor Author

heclak commented Jan 1, 2025

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 L:A380X_EFIS_#SIDE_SIMVAR_GROUP#_VV_BUTTON_IS_ON back to 0 while TRK/FPA is on?

@BlueberryKing
Copy link
Member

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 L:A380X_EFIS_#SIDE_SIMVAR_GROUP#_VV_BUTTON_IS_ON back to 0 while TRK/FPA is on?

Ok, it makes sense not to worry about it until we know what the logic should be 👍.

@BravoMike99 BravoMike99 added QA Tier 1 QA Ready to Test A380X Related to the A380X aircraft labels Jan 8, 2025
@BravoMike99
Copy link
Contributor

Quality Assurance Tester Report

Discord Username : bruno_pt99
Object of testing : #9656
Aircraft : A380X
Tier of Testing : 1
Date : 09/01/2025

Testing Process:
Spawned with VV turned off.
Pressed switched to TRK/FPA through the FCU and verified VV light on ✔️
Pressed VV button on either side and the light remained illuminated ✔️
Switched back to HDG/VS & VV light turned off on both sides ✔️
In HDG/VS, the VV light is synchronized with the VV display on the PFD ✔️

Testing Results:
Passed

Media:

2025-01-09.20-01-41.mp4

@BravoMike99
Copy link
Contributor

Please fix the changelog conflict so we can merge 👍

@BravoMike99 BravoMike99 added the Please Resolve Conflicts The author of thie PR must resolve remaining conflicts label Jan 9, 2025
@heclak
Copy link
Contributor Author

heclak commented Jan 10, 2025

Please fix the changelog conflict so we can merge 👍

@BravoMike99 Changelog conflict resolved

@BravoMike99 BravoMike99 merged commit 2958590 into flybywiresim:master Jan 10, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A380X Related to the A380X aircraft Please Resolve Conflicts The author of thie PR must resolve remaining conflicts QA Passed QA Ready to Test QA Tier 1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

VV P/B does not light on both EFIS when selecting TRK FPA.
3 participants