Thank you for this solution. I have created another version of your example. Maybe it could help someone.
In this State Machine, I call the opacity reset animation for all layers every time the Input changes. It allows you to avoid adding 0% opacity to each animation for a layer whenever we add a new layer with 100% opacity. Instead, the animation for each layer (R, G, B) contains only 100% opacity for each of the layers, respectively.
It would be great if you could add the new state “Input Changed.” Or some similar option that allows you to catch the Input changes. In my example, I add the backward arrow with “outfit !=” condition to every animation to have the ability to catch Input changed. Of course, we have the workaround, we can create the new Input with type Trigger and call it whenever we change the Input with type Number, but it’s less convenient.