July 3, 20214 yr I've had the alpha for a month or so and have been waiting on the bravo to arrive. It has and I'll get to break it out this weekend however prior to I've been reading folks tips on config setups and I've seen mention of software downloadable from Aerosoft for the bravo and alpha regarding (at the least) LED status. Is this even required for MSFS anymore? I thought I'd read this was a non-issue now. If there is any required software is Aerosoft the source or Honeycomb? Honeycomb has one link on their site but its non-working and another that links to Aerosoft but just for LED status from a couple of months back. Thanks for your help...
July 3, 20214 yr No piece of software is required. The LED fix fixes just that, the LED warning panel. vatsim s3
July 3, 20214 yr I use the led software from HoneyComb, I could not download it with Chrome, but it went well with Edge. System: I ASRock X670E | AMD 7800X3D | 64Gb DDR5 6000 | RTX 4090 | 2TB NVMe | Seasonic Vertex 1000W I LG Ultra Gear 34 UW I
July 3, 20214 yr I have the fix for the lights on the Bravo, not sure if it is still needed but works for me. One other thing to mention...some switches on the Brave conflict with the switches on the Alpha, you will need to reassign them (lights primarily) Edited July 3, 20214 yr by PIC007 Added info Jay
July 3, 20214 yr 25 minutes ago, PIC007 said: One other thing to mention...some switches on the Brave conflict with the switches on the Alpha, you will need to reassign them (lights primarily) Or simply clear those Bravo switch settings until you determine what other functions you may wish to assign. I wish there was a more organized method for sharing profiles. That would be a huge help. Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
July 3, 20214 yr Not that I am aware of. I use joystick gremlin along with vJoy to circumvent it, but it means that I have to spend some extra time configuring the buttons. vatsim s3
July 3, 20214 yr 2 hours ago, Virtual-Chris said: Has the issue with the switches and 10-deg heading bug been addressed? Yes. System: I ASRock X670E | AMD 7800X3D | 64Gb DDR5 6000 | RTX 4090 | 2TB NVMe | Seasonic Vertex 1000W I LG Ultra Gear 34 UW I
July 3, 20214 yr 2 hours ago, Virtual-Chris said: Has the issue with the switches and 10-deg heading bug been addressed? 37 minutes ago, Ixoye said: Yes. And note that it was not Honeycomb that needed to address it.... Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
July 3, 20214 yr Author can we not just copy out the files containing the profiles that correspond to the input device(s)? a quick search reveals...not much. I'm looking into this if anyone knows of projects related to this please lmk
July 4, 20214 yr The default Bravo profile in MSFS still has a few bugs I believe. At least I had to remove a few double assignments to the autopilot knob in order to make it work as expected. Flightsim rig: CPU: AMD 5900x | Mobo: MSI X570 MEG Unify | RAM: 32GB G.Skill Trident Z Neo | GPU: Gigabyte RTX 3090 | Storage: M.2 (2 & 4 TB) | PSU: Corsair RM850x | Case: Fractal Define 7 XL Display: Acer Predator x34 3440x1440 | Speakers: Logitech Z906 Controllers: Fulcrum One Yoke | MFG Crosswind v2 pedals | Honeycomb Bravo Quadrant |Thrustmaster TCA Quadrant | Stream Deck XL & Plus | TrackIR 5 Tobii eye tracking
July 4, 20214 yr Congratulations on grabbing a Bravo. I got mine this past Thursday and am super happy with it. No software is required for the Bravo itself. The LED software is just for the gear and annunciator lights.
July 4, 20214 yr 13 hours ago, badgenes said: can we not just copy out the files containing the profiles that correspond to the input device(s)? a quick search reveals...not much. I'm looking into this if anyone knows of projects related to this please lmk Unlike the Honeycomb profiles for FSX/P3D saved via the Honeycomb Configurators, The MSFS profiles seem to be saved by MSFS into relatively obscure locations with obscure names. If those can be tracked down, and if the filenames are not a barrier (i.e. unique names from one person's installation to another's) then it is possible. Then all that is needed is a repository like the Library here on Avsim or perhaps on TO. I have hit a couple of dead ends attempting to assign Bravo switches in MSFS. One example is pitot heat when there are two pitot heat switches like in the twins. I can find only one assignment to use in MSFS itself, not two. I am not to this time attempting to use FSUIPC7. Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
July 4, 20214 yr Found for instance my Honecomb Bravo settings file. Here is the path to the folder that holds it: C:\Users\Owner\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\000901FDE8E88D49_00000000000000000000000069F80140\5D9A10D974DF4123B7BEEB6CA7A81B61\ And here is the filename in that folder: 8B0D957B55EF46D999E0E6E366EFCBCA How much more obscure can they make it? Open this box to see the xml details: Spoiler <?xml version="1.0" encoding="UTF-8"?> <Version Num="1544"/> <FriendlyName>Bravo Throttle Quadrant Twins</FriendlyName> <Device DeviceName="Bravo Throttle Quadrant" GUID="{155DEBA0-4F65-11EB-8001-444553540000}" ProductID="6401"> <Axes> <Axis AxisName="X" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/> <Axis AxisName="Y" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/> <Axis AxisName="Z" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/> <Axis AxisName="rX" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/> <Axis AxisName="rY" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/> <Axis AxisName="rZ" AxisSensitivy="0" AxisSensitivyMinus="0" AxisNeutral="0" AxisDeadZone="0" AxisOutDeadZone="0" AxisResponseRate="-1"/> </Axes> <Context ContextName="PLANE"> <Action ActionName="KEY_MINUS" Flag="2"> <Primary> <KEY Information="Joystick Button 14">13</KEY> </Primary> </Action> <Action ActionName="KEY_PLUS" Flag="2"> <Primary> <KEY Information="Joystick Button 13">12</KEY> </Primary> </Action> <Action ActionName="KEY_AP_MASTER" Flag="2"> <Primary> <KEY Information="Joystick Button 8">7</KEY> </Primary> </Action> <Action ActionName="KEY_VOR_OBS" Flag="2"> <Primary> <KEY Information="Joystick Button 18">17</KEY> </Primary> </Action> <Action ActionName="KEY_ELEV_TRIM_DN" Flag="2"> <Primary> <KEY Information="Joystick Button 22">21</KEY> </Primary> </Action> <Action ActionName="KEY_ELEV_TRIM_UP" Flag="2"> <Primary> <KEY Information="Joystick Button 23">22</KEY> </Primary> </Action> <Action ActionName="KEY_AP_APR_HOLD" Flag="2"> <Primary> <KEY Information="Joystick Button 3">2</KEY> </Primary> </Action> <Action ActionName="KEY_AP_HDG_HOLD" Flag="2"> <Primary> <KEY Information="Joystick Button 1">0</KEY> </Primary> </Action> <Action ActionName="KEY_AP_ALT_HOLD" Flag="2"> <Primary> <KEY Information="Joystick Button 5">4</KEY> </Primary> </Action> <Action ActionName="KEY_AP_BC_HOLD" Flag="2"> <Primary> <KEY Information="Joystick Button 4">3</KEY> </Primary> </Action> <Action ActionName="KEY_AP_NAV1_HOLD" Flag="2"> <Primary> <KEY Information="Joystick Button 2">1</KEY> </Primary> </Action> <Action ActionName="KEY_FLAPS_INCR" Flag="2"> <Primary> <KEY Information="Joystick Button 15">14</KEY> </Primary> </Action> <Action ActionName="KEY_FLAPS_DECR" Flag="2"> <Primary> <KEY Information="Joystick Button 16">15</KEY> </Primary> </Action> <Action ActionName="KEY_AUTO_THROTTLE_TO_GA" Flag="2"> <Primary> <KEY Information="Joystick Button 29">28</KEY> </Primary> </Action> <Action ActionName="KEY_THROTTLE1_DECR" Flag="2"> <Primary> <KEY Information="Joystick Button 24">23</KEY> </Primary> </Action> <Action ActionName="KEY_THROTTLE2_DECR" Flag="2"> <Primary> <KEY Information="Joystick Button 25">24</KEY> </Primary> </Action> <Action ActionName="KEY_MIXTURE1_DECR" Flag="2"> <Primary> <KEY Information="Joystick Button 28">27</KEY> </Primary> </Action> <Action ActionName="KEY_MIXTURE2_DECR" Flag="2"> <Primary> <KEY Information="Joystick Button 33">32</KEY> </Primary> </Action> <Action ActionName="KEY_PITOT_HEAT_ON" Flag="2"> <Primary> <KEY Information="Joystick Button 34">33</KEY> </Primary> </Action> <Action ActionName="KEY_PITOT_HEAT_OFF" Flag="2"> <Primary> <KEY Information="Joystick Button 35">34</KEY> </Primary> </Action> <Action ActionName="KEY_GEAR_UP" Flag="2"> <Primary> <KEY Information="Joystick Button 31">30</KEY> </Primary> </Action> <Action ActionName="KEY_GEAR_DOWN" Flag="2"> <Primary> <KEY Information="Joystick Button 32">31</KEY> </Primary> </Action> <Action ActionName="KEY_AP_AIRSPEED_SET" Flag="2"> <Primary> <KEY Information="Joystick Button 17">16</KEY> </Primary> </Action> <Action ActionName="KEY_AP_VS_HOLD" Flag="2"> <Primary> <KEY Information="Joystick Button 6">5</KEY> </Primary> </Action> <Action ActionName="KEY_AP_VS_SET" Flag="2"> <Primary> <KEY Information="Joystick Button 20">19</KEY> </Primary> </Action> <Action ActionName="KEY_AXIS_MIXTURE1_SET" Flag="132"> <Primary> <KEY Information="Joystick R-Axis X ">770</KEY> </Primary> </Action> <Action ActionName="KEY_AXIS_MIXTURE2_SET" Flag="132"> <Primary> <KEY Information="Joystick L-Axis Z ">1058</KEY> </Primary> </Action> <Action ActionName="KEY_HEADING_BUG_SELECT" Flag="2"> <Primary> <KEY Information="Joystick Button 19">18</KEY> </Primary> </Action> <Action ActionName="KEY_ALTITUDE_BUG_SELECT" Flag="2"> <Primary> <KEY Information="Joystick Button 21">20</KEY> </Primary> </Action> <Action ActionName="KEY_VSI_BUG_SELECT" Flag="2"> <Primary> <KEY Information="Joystick Button 20">19</KEY> </Primary> </Action> <Action ActionName="KEY_AIRSPEED_BUG_SELECT" Flag="2"> <Primary> <KEY Information="Joystick Button 17">16</KEY> </Primary> </Action> <Action ActionName="KEY_TOGGLE_FEATHER_SWITCH_1" Flag="2"> <Primary> <KEY Information="Joystick Button 26">25</KEY> </Primary> </Action> <Action ActionName="KEY_TOGGLE_FEATHER_SWITCH_2" Flag="2"> <Primary> <KEY Information="Joystick Button 27">26</KEY> </Primary> </Action> <Action ActionName="KEY_THROTTLE1_AXIS_SET_EX1" Flag="132"> <Primary> <KEY Information="Joystick L-Axis Y ">1042</KEY> </Primary> </Action> <Action ActionName="KEY_THROTTLE2_AXIS_SET_EX1" Flag="132"> <Primary> <KEY Information="Joystick L-Axis X ">1026</KEY> </Primary> </Action> <Action ActionName="KEY_PROP_PITCH1_AXIS_SET_EX1" Flag="132"> <Primary> <KEY Information="Joystick R-Axis Z ">802</KEY> </Primary> </Action> <Action ActionName="KEY_PROP_PITCH2_AXIS_SET_EX1" Flag="132"> <Primary> <KEY Information="Joystick R-Axis Y ">786</KEY> </Primary> </Action> <Action ActionName="KEY_AP_FLIGHT_LEVEL_CHANGE" Flag="2"> <Primary> <KEY Information="Joystick Button 7">6</KEY> </Primary> </Action> <Action ActionName="KEY_PARKING_BRAKE_SET" Flag="2"> <Primary> <KEY Information="Joystick Button 47">46</KEY> </Primary> <Secondary> <KEY Information="Joystick Button 48">47</KEY> </Secondary> </Action> </Context> </Device> Frank Patton Corsair 5000D Airflow Case; MSI B650 Tomahawk MOB; Ryzen 7 7800 X3D CPU; ASUS RTX 4080 Super; NZXT 360mm liquid cooler; Corsair Vengeance 64GB DDR5 4800 MHz RAM; RMX850X Gold PSU;; ASUS VG289 4K 27" Display; Honeycomb Alpha & Bravo, Crosswind 3's w/dampener. Former USAF meteorologist & ground weather school instructor. AOPA Member #07379126 "I will never put my name on a product that does not have in it the best that is in me." - John Deere
Archived
This topic is now archived and is closed to further replies.