Additional features are provided by the gear switch, the trim wheel, and 7 freely programmable switches so the user does not need to reach out to the keyboard as often. It is correct that X-Plane 11 uses for specific hardware only 1 joy file. However, with this basic joy file you can create several user profiles and assign them to different aircraft. I’ll give you an example about this in the coming paragraphs. The problem is that the Bravo Throttle Quadrant has many switches, levers, knobs of which most can be configured within X-Plane but when it comes to the annunciator lights, the integral AP lights, the GEAR lights, for hose you need the Aerosoft AFC_Bridge configurator. I managed to get the Better Bravo software running automatically by goofing with the XML, though by then I was pulling out my hair with multiple and different changes, so I'm not at all sure what I changed that worked. But I can confirm what someone else above observed that it does not seem to be working with the Fenix, though I don't think the original drivers were, either.

I not only agree with all that was said here about the Bravo (I only have the Bravo), it is IMHO even worse: Aerosoft put a hardware product on the market, thereby insinuating that it is (more or less) complete. NOT SO! Obviously, the ‚software‘ to make it all work with a simulator is not present. I consider the profiles an essential part of the product. First deficiency. Clearly noted in the English (and for sure in the German and French too) manual is that when you follow the cleaning instructions of the 3M Micro-Suction, you can be use on and on. In other words, there’s no need to keep, once you’ve placed the mounting plate with the 3M Micro-Suction to the table, it mounted on the table. When you don’t need the mounting plate for a while, then follow the instructions in the manual, reapply the plastic covering to preserve quality and condition of the 3M Micro-Suction. What’s most important and something you and I would expect, is that all the AP related switches and levers (remember, only for a 4 engine jet aircraft) are correctly assigned. There’s an additional row of switches in front of the levers. These switches are not yet assigned to anything, so you’re free to use them for your own. Of course, you’re always free to change other already assigned switches, or knobs to what you prefer, but basically it should be left assigned to the most logical switch, knob or lever. When you select for example the commercial four engine configuration, then all levers belonging to this are correctly assigned.I feel that it’s time to finish this review. I went already much further than initially planned, but I would like to add the following regarding those who want to fly Airbus aircraft. The whole Bravo Throttle Quadrant feels heavy, no, better to say feels solid and made of durable components. I mentioned this before that the main housing is similar to the Alpha Flight Controls except for the front part. The plastic throttle, prop, mixture, thrust, flap and speedbrake levers are all made of plastic, but look and feel solid and realistic.

Also, if you use FSUIPC with P3D I highly recommend you locate the FSUIPC.ini, the associated .log files, and any FSUIPC profiles you have created and remove them to another location. I was having strange behavior in FSX SE even though I had gone into FSUIPC and had unbound all my button and switch settings, and my axis settings and calibration. Removing the FSUIPC files I mentioned above, then using the Honeycomb Configurator to set buttons and switches worked. Same with the yoke axis'. g. I then tried to assign them using (registered) FSUIPC6: I found ‚buttons‘ no. 82 to 89 (with subswitches), assigned them to the above functions: battery and alternator switches jumped up and immediately down again when switched ON on Bravo, of the other switches, only the landing lights worked; the flaps lever only lowered/raised the flaps entirely no increments possible (despite FLAPS_INC/DECR). The fun can start. I’m ready to start up X-Plane and test the Bravo Throttle Quadrant. This section is applicable to both Windows and macOS.It seems that when using Windows 10 and X-Plane 10.51r x, there’s not much difference then what I’ve seen on the Mac. That said, the moment I start Windows X-Plane, and connect the Bravo Throttle Quadrant for the first time to my iMac, you need in the same way as with macOS X-Plane, calibrate the six levers by moving them over their full travel. After that’s finished, the different Honeycomb pictures can be found with their switches, buttons and the levers. Since I only have macOS and Windows X-Plane, I wasn’t able to test the Honeycomb Bravo Quadrant with Linux. It isn’t a long term tested review of the Honeycomb Bravo Throttle Quadrant, but I can tell you right now that it’s a solid, modern and unique piece of hardware not seen before. The same what was applicable to the Alpha Flight Control is also applicable for the Bravo Throttle Quadrant. It is a heavy duty device, with a stiff mounting plate that can also be connected to the table with the 3M Micro-Suction pad. When you use the clamps, you could use it also in combination with the 3M Micro-Suction, but there’s actually no need for. You can leave the plastic on the mounting plate and connect it only with the clamps. Either way works and my personal preference was using only the 3M Micro-Suction since when I don’t fly, I would like to have a clean desk.

I for example, have so far not been able to make the switches work in P3Dv5. Although i did ‚program‘ them in the Bravo setup, they do not appear in P3D, and do not work. The sliders work, I assigned them in P3D options/controls; as do the gear lever and the flaps lever. I did program the AP buttons and knobs but did not test them yet. More important for me are the switches. I tried them in P3D „options“ and in FSUIPC6. When i throw a switch, it does not register in FSUIPC. The problem is, I do not know how to search for mistakes (I made) or missing settings or inputs, as I do not understand the programming philosophy behind it. The contents of this AFC_Bridge” folder has to be copied to the X-Plane plugins folder. It contains a Windows exe file as well as a macOS app file. What does is actually do? It offers a separate program that can be started without having X-Plane running, but you need to have the Honeycomb Alpha or Bravo device connected. to your PC or Mac. As of this writing – January 2021 – after several attempts I finally got Aerosoft AFC_Bridge program working with macOS Big Sur, but what said, only after several attempts. Perhaps this will be modified by kavster as soon as he has time. But the good news is that the Auto Pilot left-hand and right hand selectors on the Bravo are copying information to the ToLiss Auto Flight FCU (Flight Control Unit). That said, when I enter a speed, altitude or heading, it can be seen on the FCU. You and I need to keep in mind that for example the Zibo 738 and other add-on aircraft aircraft have complex Auto Flight systems. With these Auto Flight systems and the belonging MCP or FCU, it’s not always possible to cover every caution light on the Bravo or the Bravo Auto Pilot section. SummaryThere’s one more thing I would like to bring to your attention and that is using User Profiles and linking these user profiles to a certain aircraft. Lets go for an example; as you can see on the above GA related screenshot, it’s now all assigned to the “User Profile”. A better idea is to save it under a different name like GA Twin Engine. Everything just came together then. I did create a single fresh new profile in FSUIPC to help with a couple of obscure assignments that were difficult to find in the Honeycomb app. Just one or two switches, and they were on the Alpha. Understand that if you have FSUIPC assignments for a yoke or other controllers you will find it necessary to do fresh assignments since you removed your FSUIPC profiles. I did all but two of those for my Alpha yoke with the Alpha side of the configurator app. Run the install as administrator, program "AS_HONEYCOMB_MSFS_V2100.exe" or whatever the latest version is.