Status
Reproduced by @skylarkning
Product
EFIS Cube
Bridge Version
V3.0.0.1
Firmware Version
N/A
Simulator
MSFS 2020 / MSFS 2024
Aircraft/Add-on
iniBuilds A350
Issue
When using the Wingflex EFIS Cube with the iniBuilds A350 on Bridge V3.0.0.1, the EFIS range selector appears to force hardware state synchronization.
This prevents certain software-side EFIS range modes, such as 640 and Zoom, from being selected correctly. The hardware state overrides the aircraft/software state, making it impossible to stay on these modes.
Steps to Reproduce
- Launch MSFS 2020 or MSFS 2024.
- Load the iniBuilds A350.
- Open Wingflex Bridge V3.0.0.1.
- Connect the Wingflex EFIS Cube.
- Attempt to select EFIS range modes such as 640 or Zoom in the aircraft.
- Observe whether the selected range mode remains active.
Expected Result
The software/aircraft state should have higher priority where required. Which means if I select 640/Zoom, it should stay.
Users should be able to select and remain on EFIS range modes such as 640 and Zoom without the EFIS Cube forcing the state back to the physical hardware position.
Actual Result
The EFIS Cube forces hardware state synchronization, which prevents 640 and Zoom from being kept correctly.
Workaround
No confirmed workaround at this time.
Suggested Fix
The logic used in Bridge V2.5.1.13 is preferred and appears to handle this behavior correctly.
Consider reverting the EFIS Cube synchronization logic back to the V2.5.1.13 behavior, or updating the current logic so that software state has higher priority when required by the aircraft.
Notes
This affects the iniBuilds A350 in both MSFS 2020 and MSFS 2024.
Status
Reproduced by @skylarkning
Product
EFIS Cube
Bridge Version
V3.0.0.1
Firmware Version
N/A
Simulator
MSFS 2020 / MSFS 2024
Aircraft/Add-on
iniBuilds A350
Issue
When using the Wingflex EFIS Cube with the iniBuilds A350 on Bridge V3.0.0.1, the EFIS range selector appears to force hardware state synchronization.
This prevents certain software-side EFIS range modes, such as 640 and Zoom, from being selected correctly. The hardware state overrides the aircraft/software state, making it impossible to stay on these modes.
Steps to Reproduce
Expected Result
The software/aircraft state should have higher priority where required. Which means if I select 640/Zoom, it should stay.
Users should be able to select and remain on EFIS range modes such as 640 and Zoom without the EFIS Cube forcing the state back to the physical hardware position.
Actual Result
The EFIS Cube forces hardware state synchronization, which prevents 640 and Zoom from being kept correctly.
Workaround
No confirmed workaround at this time.
Suggested Fix
The logic used in Bridge V2.5.1.13 is preferred and appears to handle this behavior correctly.
Consider reverting the EFIS Cube synchronization logic back to the V2.5.1.13 behavior, or updating the current logic so that software state has higher priority when required by the aircraft.
Notes
This affects the iniBuilds A350 in both MSFS 2020 and MSFS 2024.