Fix Honeycomb Bravo lights in MSFS 2024: install AFC_Bridge correctly, remove duplicate packages, check aircraft power and isolate USB faults.
In MSFS 2024 on PC, Honeycomb Bravo annunciator and gear lights require the Honeycomb integration package and its AFC_Bridge process; USB control bindings alone do not drive them. Install one clean bridge copy in the active Community folder, confirm it starts, then test with a powered default aircraft.
Why do the Bravo controls work but the lights stay dark?
The levers and buttons operate as standard USB controls, while the LEDs depend on simulator data sent through AFC_Bridge. This is why a Bravo can appear normally in the Controls menu and operate the aircraft while every annunciator remains dark.
Some lights are also conditional. Warning annunciators illuminate only when the corresponding aircraft state exists, gear lights need a retractable-gear aircraft, and autopilot indications may not work correctly when an add-on aircraft uses custom systems rather than standard simulator variables.
How to fix Honeycomb Bravo lights in MSFS 2024
- Begin with a powered aircraft. Load a default retractable-gear aircraft in a ready-to-fly state. A cold-and-dark cockpit, flat battery or unpowered avionics can leave legitimate Bravo indications dark.
- Install the MSFS integration package. A control profile is not a substitute for the Honeycomb bridge software. Our Honeycomb bridge installation and duplicate-removal checklist covers the full PC setup.
- Check the installation destination. Make sure the integration package is in the Community folder actually used by MSFS 2024. If MSFS 2020 is also installed, an installer can target its older package location instead. Custom package locations create the same trap.
- Keep only one bridge installation. Close the simulator and remove obsolete or duplicate Honeycomb integration folders before reinstalling. A renamed backup left inside Community may still be loaded as an add-on and conflict with the active copy.
- Confirm that
AFC_Bridgestarts. Load into a flight, then use Windows Task Manager to look for the bridge process. If it is absent, restart Windows after installation, repair or reinstall the package, and check whether Windows security software quarantined part of it. Do not start several copies. - Use matching Windows permissions. Run MSFS 2024 and the bridge at the same privilege level. Starting one as administrator and the other normally can interfere with communication between them.
- Test a direct USB connection. Connect the Bravo directly to the PC temporarily, avoiding an unpowered hub. Intermittent or flickering LEDs point more strongly towards USB power, cable or port trouble than an aircraft profile problem.
- Try another default aircraft. If the lights work there, the bridge and hardware are functioning. The original aircraft probably needs its own integration support or does not publish the standard variables expected by the Bravo.
If the axes and buttons are missing as well, treat it as a controller problem rather than a lighting-only fault. Work through our USB, axis and duplicate-binding checks for an unresponsive throttle.
What does each lighting symptom usually mean?
| Symptom | Most likely cause | First check |
|---|---|---|
| All lights dark, controls working | Bridge missing, installed in the wrong Community folder or not running | Look for AFC_Bridge after loading a flight |
| Lights appear after starting the aircraft | Normal electrical-state behaviour | Battery, alternator and avionics state |
| Works in MSFS 2020 but not MSFS 2024 | Integration installed only in the MSFS 2020 package location | Confirm the active MSFS 2024 Community folder |
| Works with default aircraft only | Add-on aircraft uses custom system variables | Aircraft-specific integration or profile requirements |
| Only some annunciators illuminate | No matching warning condition, unsupported variable or incorrect test aircraft | Use a powered default aircraft and trigger a known indication |
| Lights flicker or the Bravo disconnects | USB power, hub, cable or port fault | Connect directly to another PC USB port |
Do Bravo lights require a control profile?
Normal MSFS control profiles map the Bravo's levers, switches and buttons; they do not replace AFC_Bridge. Some aircraft-specific configurations can affect individual indications, but changing random axis bindings will not repair an entirely dark annunciator panel.
MSFS 2024 stores profiles per physical controller, so verify that the selected profile belongs to the Bravo rather than the Alpha or another device. Our guidance on how MSFS 2024 saves profiles for each peripheral explains this distinction. For the complete controller arrangement, see our separate Alpha and Bravo configuration procedure.
How can I separate a software fault from failed LEDs?
A known powered default aircraft is the best simulator-side test. If your installed Honeycomb utility includes a lamp test, use that as well: a successful lamp test with no in-sim indications points to the bridge or aircraft data, while a failed lamp test across every LED points towards USB, installation or hardware trouble.
Do not use one warning lamp as the sole test. The simulator will not illuminate an annunciator unless that condition is active, and a fixed-gear aircraft cannot provide a meaningful retractable-gear indication.
Can AFC_Bridge be installed on Xbox or PS5?
No. AFC_Bridge is a Windows process and cannot be installed on Xbox Series X|S or PlayStation 5. On consoles, Bravo recognition and LED operation depend on the supported console connection method and native simulator integration; moving a PC Community package to the console will not enable the lights.