How do I install Honeycomb Bravo drivers and MSFS profiles?

On PC, the Honeycomb Bravo does not need a conventional Windows driver: connect it by USB, install Honeycomb’s Microsoft Flight Simulator software only for LEDs and Configurator functions, then create a device-specific control preset in MSFS. Bind each axis, remove duplicate assignments, save an aircraft-specific profile, and test every lever and switch.

Do you need a Honeycomb Bravo driver for MSFS?

No conventional Windows driver is required because the Bravo Throttle Quadrant is a standard USB input device. Windows should recognise it before Microsoft Flight Simulator is opened.

The separate Honeycomb MSFS package supplies the bridge used by annunciator lights and optional Configurator profiles. The controls can therefore work while every light remains dark; that usually means the bridge software is missing or inactive, not that the quadrant has failed.

These instructions apply to PC. Console editions cannot run the Windows installer or import desktop Configurator profiles, so their setup is limited to supported hardware connections and the simulator’s own control menus.

How to install and configure the Honeycomb Bravo

1. Close Microsoft Flight Simulator. Obtain the Honeycomb software package intended for your simulator generation. Do not assume an older MSFS 2020 package is compatible with MSFS 2024 unless the package documentation explicitly says so.
2. Install the companion software. Allow the installer to use the active MSFS Packages or Community location. The bridge component is commonly shown as AFC_Bridge; its exact presentation can differ between package releases.
3. Remove obsolete duplicate bridge copies. When updating or reinstalling, do not leave old and new versions active in separate Community folders. Multiple copies can prevent the bridge from loading correctly.
4. Connect and verify the quadrant. Plug it directly into a reliable USB port, then run joy.cpl from Windows. Select the Bravo and confirm that its axes and buttons respond. Do not apply Windows calibration merely because an aircraft’s detents are wrong; detents normally belong in MSFS or the aircraft’s own calibration page.
5. Create a custom MSFS preset. Open the simulator’s Controls settings, select the Honeycomb Bravo and duplicate the default preset or create a new one. Give it an aircraft-specific name such as “Bravo Twin Piston” or “Bravo Twin Jet”. Our device-profile setup and conflict guide explains the broader control system.
6. Clear conflicting assignments. Search by input and remove commands that MSFS has assigned twice. Check the yoke, pedals, keyboard and any gamepad as well as the Bravo.
7. Bind the axes deliberately. Use a generic throttle axis when one lever should control every engine; use numbered commands such as throttle 1 and throttle 2 for separate engines. Apply the same rule to propeller and mixture levers. Our Bravo throttle-axis mapping notes cover separate engines, reversed axes and lever selection in more detail.
8. Test before adding complex functions. Check full travel, idle, reverse, flaps, gear, trim wheel and autopilot controls in a simple default aircraft. Save the preset, then create separate copies for aircraft with different engine counts or detent systems.

A mistake we see constantly is assigning both Throttle Axis and Throttle 1 Axis to the same lever. That can make both engines move together, produce jumping inputs or cause one command to override the other.

Which kind of Honeycomb Bravo profile are you installing?

A Bravo “profile” can refer to three different configuration layers, and they are not interchangeable.

Keep ordinary axes in MSFS unless a particular aircraft’s instructions require another method. Use the Configurator for functions that cannot be expressed cleanly through standard bindings, and use the aircraft calibration layer for its detents. Sending the same command through two layers causes double inputs.

How do I import a Honeycomb Configurator profile?

Import a Configurator profile inside the Honeycomb application rather than copying the profile file into the Community folder.

1. Check compatibility. Confirm that the profile was made for the Bravo, your MSFS generation and the exact aircraft. A profile for another aircraft may call events that do not exist in the one you are flying.
2. Open the Configurator. Use its profile import command and select the supplied profile file. Menu wording can vary between software releases.
3. Select and activate the profile. Importing alone may only add it to the profile list; apply or activate it before starting the simulator.
4. Restart MSFS if necessary. This ensures the bridge and activated configuration are loaded together.
5. Select the matching in-sim preset. Remove any MSFS button assignments already being sent by the Configurator, while retaining the required axes.

If the Configurator rejects the file, it is probably the wrong profile format or software generation. Renaming the file does not convert it, and an MSFS control preset cannot simply be imported as a Honeycomb Configurator profile.

Why are the Honeycomb Bravo lights not working?

Dark Bravo lights usually indicate a bridge, power-state or aircraft-event problem rather than a failed USB driver.

• Turn on aircraft electrical power. Many annunciators and autopilot lights remain off until the battery, avionics or relevant system is active.
• Check the active Community folder. The bridge must be installed where that copy of MSFS actually loads packages.
• Confirm the bridge can run. Windows security software must not have blocked its executable or background process.
• Remove duplicate installations. Keep only the compatible bridge package intended for the simulator you are launching.
• Test a default aircraft. Some add-ons use custom events that the generic lighting profile cannot read.

Bravo autopilot LEDs normally reflect the aircraft’s simulated state, not merely the last physical button pressed. A button may therefore operate correctly while its light remains off because that aircraft rejected the mode or does not expose the expected event.

Why do the Bravo throttles move backwards or control both engines?

Wrong direction, linked engines and jumping levers are usually caused by axis inversion, generic and per-engine assignments being active together, or the wrong preset being selected.

• Lever moves backwards: reverse the axis in one configuration layer only. Do not invert it in Windows, MSFS and the aircraft simultaneously.
• One lever moves both engines: remove the generic throttle assignment and retain only the appropriate numbered engine axis.
• Travel stops short: inspect the raw response in joy.cpl, then check dead zones and sensitivity in MSFS.
• Reverse thrust activates unexpectedly: verify whether the fitted reverser is detected as an axis region or button input, then follow the aircraft’s own detent calibration procedure.
• A button fires twice: remove either its MSFS binding or its Configurator action.
• Mappings change between aircraft: confirm that the intended Bravo preset is active before departure.

If the preset has become tangled, reset only the Bravo’s unwanted bindings and rebuild a clean preset. If Windows or MSFS does not detect the axes at all, follow our USB, detection and throttle troubleshooting checks before reinstalling profiles.