Mecanim "trigger" parameter behaviour with multiple animator layers

Question

Hi, everybody.

I've noticed a strange behaviour of mecanim's "trigger" animator parameter.

Let's say I have an animator controller with multiple layers and a trigger parameter defined in t$$anonymous$$s controller. T$$anonymous$$s trigger is used to perform transitions on different layers. Moreover, t$$anonymous$$s transitions can and should be performed simultaneously. E.g. when setting "walk" trigger character should stop suffering animation (w$$anonymous$$ch is on the layer with index, 2) and start walking (layer with index 1). So the problem is: transition on $$anonymous$$gher layer (i.e. with $$anonymous$$gher index) can never be fired. If the transition on lower layer is performed too fast, the trigger will be reset before $$anonymous$$gher layer even start its transition. T$$anonymous$$s can happen if Time.timeScale value is big (I reproduced with timeScale equals 3), or if you set some triggers right after another.

I've implemented some sort of triggers queue to handle t$$anonymous$$s strange behaviour in case of multiple triggers set one after another. But cannot t$$anonymous$$nk up anyt$$anonymous$$ng to fight with timeScale.

Actually, I t$$anonymous$$nk, that some kind of triggers queue (synchronized with multiple layers) should be implemented internaly in Mecanim, it would be a much more intuitive for usage.

So the first question is: Why Unity implemented such behavoiur of triggers?

The second one: Any suggestions how to cope with timeScale issue.

Answer 1

Best Answer

Answer by JustMax · Jan 19, 2015 at 02:09 PM

http://unity3d.com/unity/whats-new/unity-4.5.5

Here is said: "Mecanim: Fixed trigger parameter consumption when used by multiple layers."

I'm pretty sure that the issue i've described is already fixed in Unity version over 4.5.5.

0 Show 3 · Share

juan-jo · Aug 26, 2016 at 06:08 PM 0

Share

The problem persists (or is back) in Unity 5.4

The trigger is 'consumed' when used by the first layer.

dazzle_jukka · Jul 12, 2017 at 05:47 PM 0

Share

Just in case someone stumbles over this thread while searching for an answer. After a while I managed to figure out how to get trigger parameters to work on multiple layers in Unity 2017.1. So yeah, triggers do work on multiple layers but the gotcha is this:

Let's say that we have Base layer, layer A and layer B and a trigger parameter MrX. All of them have a transition that will be triggered by MrX and on the Base and A layer the transition doesn't have exit time but on layer B the transition has an exit time. In this scenario, the transition would be successfully performed on the layers Base and A, but not on B, because when the statemachine on layer B evaluates transition conditions, it will have missed the trigger due to exit time.

Hopefully this clears up. And this is just something that seemed to be the case when I was playing around and testing it, so don't treat this as the absolute truth :D

datagreed dazzle_jukka · Jul 25, 2020 at 07:43 PM 0

Share

None of my transitions have an exit time and sometimes the trigger is "consumed" by one layer, sometimes by another, I did not find any pattern for this, unfortunately.

Mecanim "trigger" parameter behaviour with multiple animator layers

1 Reply

Welcome to Unity Answers

Follow this Question

Related Questions