Fix Honeycomb Bravo lights not working in MSFS 2020 by checking AFC_Bridge, the active Community folder, USB power and aircraft compatibility.
Honeycomb Bravo lights in MSFS 2020 usually stay dark because the AFC_Bridge output software is missing, installed in the wrong Community folder, duplicated or blocked. The switches can still work because inputs and LEDs use separate paths. Install or repair the bridge, then test a powered default aircraft before changing control bindings.
A mistake we see constantly is treating the Bravo as one device with one software path. Windows and Microsoft Flight Simulator can recognise its buttons, levers and switches while receiving no software-driven LED output at all. Our explanation of how the Bravo's driver, profiles and LED layer fit together covers that distinction in more detail.
Why do the Bravo controls work but the lights do not?
The Bravo's controls are USB inputs, while its annunciators, autopilot LEDs and landing-gear lights depend on status information sent back from MSFS 2020. That output is normally handled on Windows by the Honeycomb software and AFC_Bridge.
The lights are not simply USB power indicators. They reflect simulator states, so plugging in the quadrant does not make every lamp illuminate. Many will remain dark in a cold-and-dark aircraft or when the selected aircraft does not expose a standard output that the bridge understands.
| What you see | Most likely cause | Best next check |
|---|---|---|
| Controls work, but every light is dark | AFC_Bridge is missing, duplicated or not running | Repair the Honeycomb MSFS installation |
| Neither controls nor lights work | USB, device detection or controller profile problem | Use our MSFS 2020 input troubleshooting |
| Lights are dark only when cold and dark | Aircraft electrical state | Test from a runway or in-flight start |
| Default aircraft work, but one add-on does not | Custom aircraft variables or missing aircraft-specific support | Use a profile or integration intended for that exact aircraft |
| Lights fail after sleep or during a long session | USB power saving or a stopped bridge process | Reconnect the device and inspect USB power management |
How do I get Honeycomb Bravo lights working in MSFS 2020?
A clean bridge installation in the active Community folder fixes most cases where all Bravo LEDs remain dark.
- Establish a powered baseline. Load a stock retractable-gear aircraft from a runway or in-flight start. Confirm that the battery, avionics and relevant electrical buses are on. A powered aircraft with its gear down should provide a clearer test than a cold-and-dark fixed-gear aircraft.
- Find the Community folder MSFS 2020 is actually using. The location varies between Microsoft Store, Steam and custom installations. The
InstalledPackagesPathentry near the end ofUserCfg.optidentifies the active packages location; its Community folder is the one that matters. - Repair the official Honeycomb MSFS software. Close the simulator first, then reinstall or repair the package that supplies
AFC_Bridge. Do not place it in the Official or OneStore folder. Our Bravo package-installation checks for MSFS explain the bridge and duplicate-package checks without guessing at installation paths. - Remove duplicate bridge copies. Keep only one active
AFC_Bridgepackage. Renaming an old copy to something such as “backup” does not necessarily disable it if it remains inside Community. Also check that the package has not been buried inside an extra wrapper folder. - Confirm that the bridge starts. Launch MSFS 2020 and inspect Windows Task Manager for the bridge process. If its Community package exists but no process starts, repair the installation rather than repeatedly opening several copies by hand. Check security-software quarantine records, restoring a file only when it came from the official Honeycomb installer.
- Check the USB connection. Connect the Bravo directly to the computer for testing, or use a known powered hub. Replace the cable if the device disconnects or resets. Change Windows USB power-saving settings only when the fault appears after sleep or after the quadrant has been idle.
- Run a clean add-on test. If the bridge is running but the stock aircraft test still fails, temporarily move unrelated packages out of Community, leaving only the bridge. Restart MSFS after every Community-folder change; changing packages while a flight is loaded is not a valid test.
Do not start by deleting the rolling cache or rebuilding every control binding. Neither action installs the output bridge, and both can create unrelated work.
Why do the lights work in default aircraft but not add-on aircraft?
If stock MSFS 2020 aircraft drive the Bravo lights correctly, the hardware, USB connection and basic bridge installation are working. The remaining fault is normally specific to the add-on aircraft.
Complex aircraft often use custom local variables and internal logic instead of the standard simulator outputs expected by a generic Bravo configuration. Use an aircraft-specific profile or supported integration only after the default-aircraft test passes; a profile made for another model can produce incorrect autopilot or gear indications. Our broader Alpha and Bravo configuration notes cover profile selection and add-on compatibility.
Remember that an autopilot LED may represent the mode reported by the aircraft, not merely the button you pressed. If the mode is armed, rejected or replaced by another mode, the hardware indication may differ from the physical switch position.
Should I reset my MSFS control profile?
No—resetting the control profile is not the normal fix when the levers and switches already respond but the LEDs remain dark. Input bindings and lighting output are separate.
Change profiles when an axis, button or switch has the wrong assignment, or when a particular add-on requires its own configuration. For completely dark lights across all aircraft, concentrate first on AFC_Bridge, the active Community folder and whether the bridge process starts.
Do these AFC_Bridge fixes apply on Xbox?
No—the AFC_Bridge and Community-folder procedure applies to the Windows PC version of MSFS 2020. Xbox cannot install the Windows bridge or use PC Community-folder packages.
On Xbox, Bravo lighting depends on a supported console-compatible Honeycomb hardware arrangement, its firmware and the simulator's console output support. If the controls work but the LEDs do not, copying PC bridge files is not a solution.