My "FLAP Switch - Cycle" key bind have a strange behaviour

[gbechtinger]

Hello! 

My "flap switch cycle" on the F18 binded to one of my throttle buttons doesn't work as expected. Even pressing many times the switch doesn't move. But if I use a mouse click to move it, the bind for the throttle start to work! Maybe it's a bug? Even creating a mission starting from the air, the button not work until I click with the mouse or I presso another keyboard bind, F key por example.  I try to remove all the binds  for the flaps and leave only the one I need, but it not solve the issue.

 

In the input configuration file it shows as:

 

["d3017pnilunilcd2vd0vpnilvunil"] = {
            ["added"] = {
                [1] = {
                    ["key"] = "JOY_BTN19",
                },
            },
            ["name"] = "FLAP Switch - Cycle",
        }

 

I have two Arduino Micro, one in my DIY Throttle and another with my DIY Stick, maybe there is some conflict between them and DCS? they have different names and different lua files for the configuration. I attached a image with the two configuration files in DCS Folder.

 

 

[diamond26]

I have the same behavior without the complexity of your setup. Single binding which doesn’t work unless there is manual intervention with mouse.

[pete_auau]

yep  same  here  once i start  engines  all i need  to do is  cycle  the  flap switch  up  and  than  every  is  normal after  that  can use  my switch on my throttles  as many  times i like

[gbechtinger]

I found out that the problem occurs also on the keyboard bind... so, it seems like a real bug and not a device specific problem.

[gbechtinger]

One thing I got in mind is that maybe DCS needs to last states to be able to calculate the next toggle position. As example, how DCS will know from HALF position, if you want to go from AUTO or FULL? After you click on the button, they know the last two positions it's half and full, so in the next cycles it will go half-auto-half-full-half-auto...

[diamond26]

29 minutes ago, gbechtinger said:

One thing I got in mind is that maybe DCS needs to last states to be able to calculate the next toggle position. As example, how DCS will know from HALF position, if you want to go from AUTO or FULL? After you click on the button, they know the last two positions it's half and full, so in the next cycles it will go half-auto-half-full-half-auto...

The problem with this is that even with cold start where you change manually flaps from full to half the binding is still not working