Honeycomb Bravo Throttle Quadrant - Mapping Beacon - Taxi - Nav light switches

Is it a known issue that the Beacon, Taxi, and Nav light switches can’t be mapped? I just received my Honeycomb Bravo Throttle Quadrant and these 3 light switches were mapped by default but they do nothing - Landing, Strobe, Pitot Heat, and Avionics 1 were also mapped but those work fine.
I’ve tried re-mapping but still nothing. Note, I’m not using a Honeycomb Alpha Yoke which I realize has this switches mapped by default and can interfere but that isn’t relative in my case.

Can these there light switches be mapped?

Yes, they can be and I have it working on some aircraft where I’ve configured it. Just be aware of the challenges. Important you view this thread: Heading Increment Bug (10 degree instead of 1) Explained

I’m not sure what you’re telling me… that I need this utility to properly map? As for simconnect, I do use Little Navmap.

Thanks

FuzzyFassbender I’m not sure what you’re telling me… that I need this utility to properly map? As for simconnect, I do use Little Navmap.

What they are saying is that you can use the * SET commands for the always on switches the Alpha uses. The problem is that using them can break other things like adjusting heading, course, altitude, etc. Right now any time a button is held down all other multi press controls are getting accelerated. They end up moving way more than you expect. So people are using 3rd party tools to convert the always on switches to a pulse. As you have discovered this has uncovered the fact the following ON/OFF command are broken in game:
Beacon Lights On
Beacon Lights Off
Taxi Lights On
Taxi Lights Off
Nav Lights On
Nav Lights Off

They do nothing no matter type of controller is bound to them they are just broken in game. I searched for a topic on this and found one that was closed some time ago because of no votes. I think it is just starting to gain speed as more people get the Alpha and also use rotary knobs.

This issue is still alive after SU7. In my opinion is that one core function of the sim, that inputs and comands should work properly.

This thread is one of a number of reasons I have 100% moved away from in-game control mapping. I use axis and ohs for EVERYTHING now. MSFS2020 control profiles are blank for all my devices.

Why I moved away from MSFS in-game control mapping:

  • Automatic per-plane profile changes.
  • Ability to use On/Off functionality with toggle only inputs.
  • Complete control over the speed of input. E.G. Trim Wheel on Bravo is useless after SU5, I have to spin the wheel 10x times to get a noticeable trim input. Aith AAO I can set it to increase the rate of change as much as I want
  • NO MORE HAVING TO RESET PROFILES AFTER A SIM UPDATE! This one is key for me. My profiles get butchered typically after an update. If this happens now, I only have to re-create three instead of 9… And re-create means deleting ALL the inputs which is quick and easy.
  • All the input bug with rate acceleration as in the linked post are solved via using scripts or other workarounds.
  • I can map keys to things currently not present in the default key bindings. E.G Use the Bravo up/down rotate to adjust light values for the cockpit or use stream deck to do something similar.

IMO MSFS2020 is designed to work with an XBOX gamepad. Everything is secondary. The only way I’ve found to have a consistent experience is to stop using the default interface and use 3rd party software. This has been the ONLY way to have an “it just works” experience for a while now for me.

What 3rd party SW are you using?

Currently using AXIS and Oh’s by Lorbi, but SPAD.Next has my attention… Its lacking streamdeck interfacing currently, if that gets closed I may jump.

Did you find an easy way to use either of these programs from scratch so you dont have to manually input all 9000 buttons and axes at first?

On the 14 day trial of spad, the public profile section doesnt seem to work on mine, so i’ve kinda stepped back and gave up for now.