Erratic behavior of unstable switches

[MSFS 2024] Bug Reports Aircraft
1

Version: 1.7.27.0

Frequency: Consistently

Severity: High

Marketplace package name: azurpoly-aircraft-jaguar-a

Bug description:

Hello,

We use this custom template in many of our aircraft to simulate an unstable switch that goes back to its neutral position when the mouse is released.

While it is working fine on MSFS 2020 aircraft, the same XML code is not working well in MSFS 2024 native aircraft. The switch has a tendency to always go to the same direction, even if the mouse is moved in the opposite direction (see the attached video). The only solution is to use legacy interactions.

<Template Name="AZP_UNSTABLE_SWITCH">
        <Parameters Type="Default">
            <FREQUENCY>3</FREQUENCY>
            <UPDATE_CODE_DOWN></UPDATE_CODE_DOWN>
            <UPDATE_CODE_UP></UPDATE_CODE_UP>
            <TOOLTIP_DOWN></TOOLTIP_DOWN>
            <CODE_NEUTRAL></CODE_NEUTRAL>
            <TOOLTIP_NEUTRAL></TOOLTIP_NEUTRAL>
            <TOOLTIP_UP></TOOLTIP_UP>
        </Parameters>
        <Component ID="#NODE_ID#" Node="#NODE_ID#">
            <UseTemplate Name="ASOBO_GT_Switch_3States">
                <CODE_POS_0>
                    1 (&gt;O:_TrimDelta)
                </CODE_POS_0>
                <CODE_POS_1>
                    0 (&gt;O:_TrimDelta)
                    #CODE_NEUTRAL#
                </CODE_POS_1>
                <CODE_POS_2>
                    -1 (&gt;O:_TrimDelta)
                </CODE_POS_2>
                <STATE0_TEST>(O:_TrimDelta) 0 &gt;</STATE0_TEST>
                <STATE1_TEST>(O:_TrimDelta) 0 ==</STATE1_TEST>
                <STATE2_TEST>(O:_TrimDelta) 0 &lt;</STATE2_TEST>
                <STATE_MAX_TIMER>0.01</STATE_MAX_TIMER>
                <STATE0_TIMER>0.01</STATE0_TIMER>
                <ANIMTIP_0>#TOOLTIP_DOWN#</ANIMTIP_0>
                <ANIMTIP_1>#TOOLTIP_NEUTRAL#</ANIMTIP_1>
                <ANIMTIP_2>#TOOLTIP_UP#</ANIMTIP_2>
                <MOMENTARY_SWITCH/>
                <WWISE_EVENT>switch_toggle</WWISE_EVENT>
            </UseTemplate>
            <UseTemplate Name="ASOBO_GT_Update">
                <FREQUENCY>#FREQUENCY#</FREQUENCY>
                <UPDATE_CODE>
                    (O:_TrimDelta) 0 != if{
                        (O:_TrimDelta) 0 &gt; if{
                            #UPDATE_CODE_UP#
                        } els{
                            #UPDATE_CODE_DOWN#
                        }
                    }
                </UPDATE_CODE>
            </UseTemplate>
        </Component>
    </Template>

Is there any reason why it would work differently in MSFS 2024?
Are we forced to use new EX1 templates instead ?

Also, this issue is not reproducible on Xbox (even with a mouse device).

Thanks, kind regards,

Romain