[MSFS] FCU Combo Cube Displays Do Not Blank After Aircraft Power-Off

[skylarkning]

Status

Confirmed by multiple users. Needs fix.

Product

FCU Combo Cube

Bridge Version

V3.0.0.1-Hotfix

Firmware Version

N/A

Simulator

MSFS 2020 / MSFS 2024

Aircraft/Add-on

Fenix A320 Family
iniBuilds A340
iniBuilds A350
Other Airbus aircraft may also be affected

Issue

When powering down the aircraft to cold and dark, the FCU Combo Cube display digits remain on instead of blanking.

Users report that the numbers stay active even after leaving the simulator or closing WingFlex Bridge.

This issue has been confirmed by multiple users on V3.0.0.1-Hotfix and appears to affect multiple Airbus aircraft, including the Fenix A320 Family, iniBuilds A340, and iniBuilds A350.

Steps to Reproduce

1. Launch MSFS 2020 or MSFS 2024.
2. Load an affected Airbus aircraft, such as the Fenix A320 Family, iniBuilds A340, or iniBuilds A350.
3. Open WingFlex Bridge V3.0.0.1-Hotfix.
4. Connect the FCU Combo Cube.
5. Power down the aircraft to cold and dark.
6. Observe the FCU Combo Cube displays.
7. Close the simulator and/or WingFlex Bridge.
8. Observe whether the display digits remain active.

Expected Result

When the aircraft is powered down to cold and dark, the FCU Combo Cube displays should blank correctly.

When WingFlex Bridge is closed or the simulator is no longer running, the displays should not remain active with stale values.

Actual Result

The FCU Combo Cube display digits remain on after aircraft power-off.

In some cases, the numbers remain active even outside the simulator and after WingFlex Bridge has been closed.

Workaround

No confirmed software workaround at this time.

Disconnecting USB power may be required to fully blank the displays.

Notes

Reported by Velocity on 2026-07-08.

Confirmed by WladjPanacek on 2026-07-11.

Confirmed by Serenus on V3.0.0.1-Hotfix with Fenix A320 Family, iniBuilds A340, and iniBuilds A350.

[skylarkning]

Patch is delayed as firmware protocol is getting updated.

[skylarkning]

Backlog, updated as Priority 3, might take up to six months to fix. Issue is only cosmetic and does not affect normal functions. The reason for the delay is that all devices are getting updated to a open protocol standard which will support a unified way for cold and dark modes, this work is taking some time and therefore a patch for this particular issue has been delayed.