[MSFS] FBW A320neo NAV/LOGO light switch does not work on V3.0 Beta

[skylarkning]

Status

Reproduced by @skylarkning. Needs engineering review.

Product

Overhead Panel

Bridge Version

V3.0.0.0 Beta

Firmware Version

N/A

Simulator

MSFS 2020 / MSFS 2024

Aircraft/Add-on

FlyByWire A320neo / A32NX

Issue

When using the Wingflex A320 Overhead Panel with the FlyByWire A320neo on Bridge V3.0 Beta, the NAV/LOGO light switch does not change state correctly.

The user report indicates that FBW may have changed the relevant variable.

Reported FBW variable:

L:A32NX_LIGHTS_NAV_LOGO

Reported enum values:

OFF - 0
SYSTEM 1 - 1
SYSTEM 2 - 2

Steps to Reproduce

1. Launch MSFS.
2. Load the FlyByWire A320neo / A32NX.
3. Open Wingflex Bridge V3.0.0.0 Beta.
4. Connect the Wingflex A320 Overhead Panel.
5. Move the NAV/LOGO light switch.
6. Observe whether the aircraft NAV/LOGO light state changes.

Expected Result

The NAV/LOGO light switch should change the FBW A320neo NAV/LOGO light state correctly.

Actual Result

The NAV/LOGO light switch does not change state.

Possible Cause

FBW may have changed the NAV/LOGO light variable to:

L:A32NX_LIGHTS_NAV_LOGO

Workaround

No confirmed workaround at this time.

Notes

User reports that this still needs correction in V3.0 Beta.

[mihunet]

Hi, i found some information about this thing in the FBW Documentation.

I took a look and test with Axis and Ohs and found out, that the described method worked by using the A-Variable "A:CIRCUIT SWITCH ON:17" and "A:CIRCUIT SWITCH ON:20"

Maybe this helps you also in case of the problem with the Landing light retraction

The default behavior of the SIMCONNECT events for landing lights and taxi lights is very weird for the A320 as SIMCONNECT does not really account for 3 landing lights, one of them on the same switch as the taxi light and an independent RWY TURN OFF light.

These events often trigger several lights and switches together, and it is very hard to specifically map them to single button/switches.

One solution we have found to be working, is:

Landing Lights L
Set LIGHTING_LANDING_2 to 0 (sets the switch to ON)
Set LANDING_2_RETRACTED to 0 (extends the landing light)
Delay of 8-10sec (to simulate the time it takes to extend the lights)
Set CIRCUIT SWITCH ON:18 to 1 (turns on the actual light)

Landing Lights R
Set LIGHTING_LANDING_3 to 0 (sets the switch to ON)
Set LANDING_3_RETRACTED to 0 (extends the landing light)
Delay of 8-10sec (to simulate the time it takes to extend the lights)
Set CIRCUIT SWITCH ON:19 to 1 (turns on the actual light)

NOSE
Set CIRCUIT SWITCH ON:17 (turns on TAXI lights and moves switch to TAXI)
Set CIRCUIT SWITCH ON:20 (turns on T.O. lights and moves switch to T.O.)
Set CIRCUIT SWITCH ON:17 CIRCUIT SWITCH ON:20 to 0 to turn off all NOSE lights and move the switch to OFF)

RWY TURN OFF
Set CIRCUIT SWITCH ON:21 to 1 (turns on left light)
Set CIRCUIT SWITCH ON:22 to 1 (turns on right light)

[skylarkning]

I was able to reproduce, suggest further investigation.

[skylarkning]

Work

Hi, i found some information about this thing in the FBW Documentation.

I took a look and test with Axis and Ohs and found out, that the described method worked by using the A-Variable "A:CIRCUIT SWITCH ON:17" and "A:CIRCUIT SWITCH ON:20"

Maybe this helps you also in case of the problem with the Landing light retraction

The default behavior of the SIMCONNECT events for landing lights and taxi lights is very weird for the A320 as SIMCONNECT does not really account for 3 landing lights, one of them on the same switch as the taxi light and an independent RWY TURN OFF light.

These events often trigger several lights and switches together, and it is very hard to specifically map them to single button/switches.

One solution we have found to be working, is:

Landing Lights L Set LIGHTING_LANDING_2 to 0 (sets the switch to ON) Set LANDING_2_RETRACTED to 0 (extends the landing light) Delay of 8-10sec (to simulate the time it takes to extend the lights) Set CIRCUIT SWITCH ON:18 to 1 (turns on the actual light)

Landing Lights R Set LIGHTING_LANDING_3 to 0 (sets the switch to ON) Set LANDING_3_RETRACTED to 0 (extends the landing light) Delay of 8-10sec (to simulate the time it takes to extend the lights) Set CIRCUIT SWITCH ON:19 to 1 (turns on the actual light)

NOSE Set CIRCUIT SWITCH ON:17 (turns on TAXI lights and moves switch to TAXI) Set CIRCUIT SWITCH ON:20 (turns on T.O. lights and moves switch to T.O.) Set CIRCUIT SWITCH ON:17 CIRCUIT SWITCH ON:20 to 0 to turn off all NOSE lights and move the switch to OFF)

RWY TURN OFF Set CIRCUIT SWITCH ON:21 to 1 (turns on left light) Set CIRCUIT SWITCH ON:22 to 1 (turns on right light)

Confirmed that the OVHD works with FBW Release V0.14.0. We do not provide up-to-date support for developmental builds. Planned for future patches once release build is updated.

[mihunet]

Understand these point, but keep in mind, the release of v2024.1.0 can be expected soon, as FBW wants to seperate the versions for 2020 & 2024. The actual released v0.14.0 is very old (12/2025).

https://github.com/flybywiresim/aircraft/releases/tag/v2024.1.0-rc3

If possible please test the nessesary changes with the RC, otherwise we wait and hope, that you can patch these points soon after the release.

[skylarkning]

Priority 4 until FBW updates stable build. Then it will be escalated to P3.

[mihunet]

New Stable Released - pls ecalate 😀

[mihunet]

Please change title, this issue also addresses the not correct working landing lights. Thx