I just purchased a Honeycomb alpha yoke. Everything seems to work great, however I have noticed some odd behavior of the switches. It seems to occur with every switch, including the magnetos. For example, when I switch the master from off to on, the in game switch goes on, then off real quick, then back to on. Sure, the switch gets to the right positions but it’s rather annoying and kills the realism of the yoke for me. It also happens with the magneto switch when switching back from start to both. It will go to both, quickly back to start, then finally settle on both. I haven’t been able to find any other posts of people experiencing a similar issue.
No, I do not have a keybind conflict. All light keybinds are cleared on keyboard, mouse, my throttle, and rudder pedals. This was the first thing I did when I got the yoke. I have changed some of the binds and have 2/5 light switches working. Landing lights and strobes work correctly when the switches are bound to “Landing Light ON” and “Landing Light OFF” (or strobe lights). The other switches do not. The other switches only work when the “ON” bind is switched in game to “Nav Lights Set” instead. But when one bind is set to the “Set” function, the switches do the quick off/on thing. It appears to be a binding issue with the sim.
I should mention that the switches work in the menu when making the binds. For the beacon, the correct binding (On or Off) lights up when the switch is in the correct position. In the aircraft (172/152/TBM - the ones I have tested) the switch does not move. The On/Off binds of some lights are not communicating with the switch in-game.
I don’t want to sound conflicting but I had similar with mine at first and it was a key-bind in the alpha so please double check all bindings. I just want to help.
I used this video when I received my Bravo. By the time you finish, you will have it configured for all type of aircrafts. This guy (RMAG) is awesome. Hopefully this will help you. I use a G2 VR set, so now I have a VR profile and a standard profile for each aircraft. In my VR profile I disabled all the mechanical switches on my Honeycomb Alpha and the Bravo so I don’t have to fumble with the switches in the dark. 5 configurations for Honeycomb Bravo Throttle Quadrant in MSFS 2020. - YouTube
I don’t have a Bravo throttle, and I know how to create new profiles. My issue is what seems to be a glitch in the game. I have all light switches bound to their respective on/off functions, and no other buttons/keys bound to any lights. The landing light and strobe lights work as they should. The others do not, despite them working correctly in the keybind menu.
im getting the same thing. changed with SU5. i had cabin lights tied to swtiches 46 and 47 on several profiles. that binding now causes overhead lights to rapidly turn on and off.
i changed NOTHING. the sim did.
i should add, SU3 screwed up the bindings i had for anti-ice. thats still not fixed.
very irritating
Light switches got totally screwed up by the update, can confirm
Strobe is backwards, landing light is weird, a32nx used to have a perfect configuration on the alpha lights now it’s weird as hell
I spent a while messing with the bindings to get it work properly with the a32nx but with several switches having 3 options (nose light off, taxi, t/o for example) I can’t figure it out. Can’t even turn the nose light off with the mouse a binding is interfering with it
Yeah I’ve just unbound all of them now. But mine were broken before. Either the bind didn’t work (when each switch position was set to on/off) or they flick on then off then on quickly (if set to off/set). It’s a shame for such a nice yoke but honestly the switches aren’t at the same quality level of the rest of the yoke anyways so I just gave up lmao
Is it the switches or the bindings? Have you confirmed that the bindings work on another device?
I’ve found that some lights respond better to ‘set’ events than ‘on’/‘off’. You should not generally combine ‘off’ with ‘set’; you should use the ‘set’ binding for the ‘on’ position and have no binding on the ‘off’ position, so it sets the on/off state based on the ‘on’ side of the switch becoming active or inactive.
Sometimes using the ‘on’/‘off’ bindings can result in ‘flickering’ or constant clicking behavior in some aircraft because the sim interprets the constant pressing of the button as multiple events, trying to switch the switch ‘on’ or ‘off’ continuously, over and over. Sometimes some aircraft will handle this poorly while others handle it better.
Currently I’m using spad.next to do most input management and am binding via SimConnect, but these should be the same events that it was using back when I used MSFS’s direct in-game bindings, and should still behave similarly as far as I know.
Experiment with the different settings – beware that some lights behave differently from others already in pre-SU5 days – and see if you can find things that work more consistently.
Also test with a keyboard or mouse or controller binding to make sure that the behavior is related to either the binding or the device.
I shouldn’t have to do any troubleshooting whatsoever. The switches worked perfectly out of the box for months and suddenly one day they all broke without an acknowledgement from either Microsoft about bindings changing/specific instructions on how to adapt, or honeycomb with a driver update or something
I haven’t noticed any problems with mine, but again I’m using bindings in spad.next via SimConnect. Be sure to report any problems you’re having to ZenDesk!
Yes, I’ve done all that, trust me. Two of the switches work with on/off. The rest do nothing, even though the bindings are confirmed working in the menus. When set to off/set, all the switches quickly turn on/off/on when moving to the on position. I dont really have another device with dual position switches so I can’t really test that, but I have heard of others having the same issues.
I had all my bindings on Alpha and Bravo working well before SU5 but I know something went wrong in SU5. I have spent three days checking and changing them as I did when I first got it and now they are perfect again. I had a lot of trouble with the keyboard and my two numeric keypads being set to some default configs but eventually sorted it. It took so many changes and tests that I cannot remember how I got it back but I wish MS and Co wouldn’t change things like that.
Just seen Vibstroniums post and that it the best way to test bindings. Just bind a couple of keys to try with a keyboard and then transfer the same bindings to your controller.
Hope it works.
Ok, so turning off my input manager app (spad.next) and fiddling with the default profile for the Alpha I’m definitely having some problems!
It feels like some of the buttons are getting virtually “stuck on” from MSFS’s perspective, in a way that they don’t with my regular usage. This can lead to flipping rapidly between internal and external camera, or the view position getting stuck at a weird angle in external camera.
I’m sure it could similarly lead to light switches getting stuck with both on and off states simultaneously trying to be active, overriding each other constantly.
I suspect this might be some sort of bug with the total number of simultaneously active buttons, or something? Eg, a typical joystick or game controller would not cause this problem, and I wasn’t having this problem when assigning only the non-continuously-on buttons on the yoke to MSFS bindings, and all the continuously-active buttons to spad.next. …
DEFINITELY report this to ZenDesk!
Amusingly after restarting MSFS on the default profile for the Alpha, I’m now encountering none of these problems. All five light switches work perfectly on the C172 G1000. So … I don’t really know what the hell is going on but something ain’t right.
I’ll be right back…