Flaps Switch Hardware Binding
-
So, the FLAPS_CONTINUOUS_INCR and FLAPS_CONTINUOUS_DECR events totally work for me in MobiFlight. I set up Flaps Down with an on hold action that repeats the
190 (>K:FLAPS_CONTINUOUS_INCR)command every 20 ms and it works... but that flaps gauge needle is veeeeery sticky and you have to tap the glass (emphasis on the have to... it is an absolute MUST) several times when lowering flaps.And I'm sure it's realistic and immersive...
But the problem is on the Honeycomb Bravo Throttle... there is no glass you can tap so either you do something like bind the AUTO PILOT button to the glass tap action (which does score high on the immersion factor...) or you're reaching with the other hand to the mouse to click on the glass while your third arm is holding the yoke and piloting the plane while on final.
I'm happy with the less immersive and more convenient FLAPS_INCR and FLAPS_DECR events. My smooth brain has enough to do when landing.
@fizzboy Glad to see that this does, in fact, work with 3rd party bindings. I have implemented this with the native binding for the next update, and provided an L:Var, but using 3rd party binding applications will always be more reliable and flexible.
The issue with many of these native bindings, btw, is that Asobo added them to the list of inputs, seemingly without realizing that many of them require input values, like your 190 above. Without any way to provide this input value in the native controls UI, I believe we're just sending a zero, so the flaps never move...
Also, just to make sure, did you have the engine running and the cabin warmed up when testing the flap gauge? On the ground, it's very sticky, but once the cabin is at a comfortable temperature and the engine is running at flight RPM, it should move pretty reliably, or at least arrive at the correct position after a second or two without needing to tap on the glass.
