m66 - Conditions have no effect on gated axis actions

[Lolo401]

I am unsure if this is new with m66 as I have only been replacing all my virtual buttons axis events by gated axis recently. It might have been present in previous releases.

Whenever VJoy conditions are setup on gated axis, those conditions are ignored and the actions are executed regardless. Ex:
In this case, I have Vjoy 9 / Button 40 setup in such a way that when pressed, Auto Boost is enabled at then end of my thrusters axis in SC. If disabled, there is no auto-boost. VJoy 9/40 state is controlled by a switch on the panel.

My Axis (2) Y (Fwd-Aft thrust) was setup like this in the same container:
(1) Vjoy Remap for axis mapping in the game, and

(2) A Gated Axis action to trigger the auto boost at the end of the axis (passing 0.95 and -0.95)

I have tried two different ways to setup conditions:

(1) One global condition on the gated axis container:

(2) Conditions on the gate crossing:

In both cases, when the profile was enabled, Auto Boost would still be activated even if Vjoy 9 Btn 40 was released, indicating that conditions are bypassed entirely when using gated axis.

[Lolo401]

Note: not isolated to VJoy conditions, the following was tried with Joystick conditions. Same results:

[Lolo401]

Note 2: Setting up the condition on the entire container resulted in the Vjoy Remap action being deactivated correctly, however the gated axis inputs were not.

[muchimi]

I'd expect conditions to fail for keyboard, joystick or vjoy because they are all "the same" except in what they check.
Gated axis is weird because it uses nested containers, which is definitely not in the DNA of the original code logic so all is custom for this.

Let me see what I can do about it because I'm pretty sure I coded conditions for nested containers - what I fear is they are being ignored, so thanks for reporting.

[muchimi]

The plot thickens.
I just tested it and it worked for an axis.
The log file trace is correct and the output is correct for mapping a gated range.

Now testing for a gate crossing.

[muchimi]

Found an interesting inversion of button press in the logic for gate crossing. Fixed in the next patch.
This said, functional (outside of the reversal).

[muchimi]

resolved as of m67d and tested ok.

[Lolo401]

Tested ok when conditions are set inside the Gated Axis:

However, when the condition is set on the gated axis action it self, it is ignored:

[Lolo401]

Update:
When the condition is set to the container inside a gate or range, it is ignored:

At this point in time, the only way, in my conditions, to have conditions work is to set them on the Action inside the container inside the gated axis. Any attempt to set a global condition on the gated axis or containers will get ignored.

[Lolo401]

In other words: highlighted in green works, in red does not.

[Lolo401]

Not a huge issue as there is a workaround: set the condition at the lowest level of execution. But it would make life easier if we could set a condition on the Gated axis as a whole. Especially if there are a lot of gates or ranges.

[muchimi]

m70 had some enhancements around condition evaluation and tracing.
Is this still occurring?