solved X: COCKPIT PERFORM CLICKABLE ACTION is leaving keys in a presses state

[karpiyon]

Hi,

I download a mission were the mission creator used a multiple "X: COCKPIT PERFORM CLICKABLE ACTION" commands.
When the mission starts, it appears those command are all performed together, something which may violate the proper command timing delay.
It leaves, in this case, some buttons presses (6 & ENTER) as seen below:

The problem. in my case is that I am using DCS-BIOS to later press some commands. Since the buttons are not in their normal state it disrupt the entire sequence. 

It there a limitation on the number of "X: COCKPIT PERFORM CLICKABLE ACTION" which can be sent on the same command?
If there isn't then there is a problem.null
null

[karpiyon]

Hi,

I download a mission were the mission creator used a multiple "X: COCKPIT PERFORM CLICKABLE ACTION" commands.
When the mission starts, it appears those command are all performed together, something which may violate the proper command timing delay.
It leaves, in this case, some buttons presses (6 & ENTER) as seen below:

The problem. in my case is that I am using DCS-BIOS to later press some commands. Since the buttons are not in their normal state it disrupt the entire sequence. 

It there a limitation on the number of "X: COCKPIT PERFORM CLICKABLE ACTION" which can be sent on the same command?
If there isn't then there is a problem.null
null

[Rudel_chw]

3 hours ago, karpiyon said:

It there a limitation on the number of "X: COCKPIT PERFORM CLICKABLE ACTION" which can be sent on the same command?

 

Not that I know of, but there are some clickable actions that do require a small pause between inputs, for example on the Mirage F1 the TACAN tuning knob requires a pause because of the knob animation, on that case I use the X: COCKPIT PERFORM CLICKABLE ACTION using separate triggers with a 1 sec delay in-between.

[karpiyon]

I appeared that the creator of the mission neglected to press down the, pressed buttons.

Setting them to "0" fixed it