I've spent two or more days getting everything set up for my new Alpha & Bravo. All axes in FSUIPC6 and all buttons & switches in SPAD.neXt. Then I realized the Bravo leds weren't working for the gear indicators or caution / warning lights. I then reluctantly downloaded and installed the Aerosoft Honeycomb software V2200. So, then the leds were all working but it nearly completely messed up all the switches and buttons. I uninstalled the AS HC software and the controls and switches now work again but no leds. I found a set of lua scripts that seem to be tested only in MSFS and I can't figure out how to fix them for P3D. Surely others have solved this problem. I'm trying right now to set it all up for the RealAir Legacy v2.

Thanks!

I would recommend heading over to the Spad.next discord.  Very lively group over there.  

Sure. But I don’t think SPAD.neXt is the problem or the solution. I think the HC configurator is setting some competing bindings that I don’t know how to negate. 

My solution was to delete all of the bindings in the HC configurator except for the controls that impact the LEDs.  It took a few minutes but I haven't had to touch them since.  There is probably a way to configure this in SPAD.Nxt, however, I haven't taken the time to research it.  There are also multiple youtube videos on how to configure HC devices that can help.

Thanks. I tried deleting all HC configurator bindings except the LED controls but still seemed to impact the SPAD.neXt buttons. Maybe I missed something. At least for now I have abandoned SPAD.neXt in P3D and I've made some profile in the HC configurator. I may try going back since the HC configurator isn't as flexible with complex controls and doesn't automatically recognize aircraft assignments. I am trying to use SPAD.neXt in MSFS since I prefer that over the organic controls assignments. Not having the same conflicts there.