[0.16.10.0] Toggling on/off a toggle module with "Toggle" after using "SetOn/SetOff" requires multiple inputs to go through

Bug Report
1

After setting a Toggle Module to its opposite state via a “SetOn/Off” connection, attempting to toggle it via a “Toggle” connection will not work on the first input (requires 1-2 extra inputs).

Steps to Reproduce

For “SetOn”:

  1. Set the Toggle Module’s state to Off.
  2. Using a “SetOn” output, set the Toggle Module’s state to On.
  3. Using a “Toggle” output, attempt to set the Toggle Module’s state to Off.

For “SetOff”:

  1. Set the Toggle Module’s state to On, but only by sending a “Toggle” output (using “SetOn” makes it happen sometimes, but only rarely)
  2. Using a “SetOff” output, set the Toggle Module’s state to Off.
  3. Using a “Toggle” output, attempt to set the Toggle Module’s state to On.

What I expected to happen

The Toggle Module’s state toggles properly to its opposite state.

What happened

The Toggle Module’s state remains in its current state until the toggle input is sent multiple times.

Notes / Media

2

Fix for this is coming with a client hot fix.

3

The hot fix for this is now out.

1 Like