Yes. Having any of these callbacks on a HOTAS is not a function that a HOTAS does. So, having a pit is the only way to even use the ICP callback in a realistic way. I don’t have a pit and don’t think I will ever get one because I like more than just the F-16. Hopefully I haven’t been entered into the Falcon frag list for saying that.
I have my Stick, Throttle, MFD’s and Pedals setup in 4.33 U1 and now need to decided what I want on the button panels. Being a newbie to Falcon BMS I guess that will come slowly as I learn what is most important.
r6 - I use the Leo Bodnar boards as well in my pit. Since they essentially create additional game controllers mapping the inputs via straight DX assignments is quite easy. I use them for most multi-position switches and BMS does a good job of reading the right position so things don’t get out of sync. And the axis inputs are perfect for radio volume settings and the HCMS brightness. If you don’t plan on using the axis then the button box boards are your best bet. Keep in mind that BMS has a LOT of buttons/switches so you will be surprised at how many game controllers you may need. To help get around this I have used an encoder board from x-key (http://xkeys.com/PIComponents/USBEncoderBoards.php) for things that are truly momentary connections such as ICP buttons, the threat warning buttons, elec caution resets, etc.