/WillNotFix_Unity-Bug-Report-Playable-IN-39561

[Avoidable] [Won't Fix] `ProcessRootMotion` and `ProcessAnimation` methods of the AnimationJob will not be executed if the `AnimationScriptPlayable` is output to a `ScriptPlayable` and it’s not the first(at index 0) input of the `ScriptPlayable`.

Primary LanguageC#

[Avoidable][Won't Fix] Unity-Bug-Report-Playable-IN-39561

Unity has stated that they will not fix this bug.

RESOLUTION NOTE: It's an edge case of the ScriptPlayable, and there is also a workaround by inserting an AnimationLayerMixerPlayable into the stream.

About this issue

ProcessRootMotion and ProcessAnimation methods of the AnimationJob will not be executed if the AnimationScriptPlayable is output to a ScriptPlayable and it’s not the first(at index 0) input of the ScriptPlayable.

Sample

How to reproduce

  1. Open the "SampleScene".
  2. Enter play mode.
  3. In the Game view, you will see "Connect to Port 0" and the value of the counter is increasing.
  4. Click the "Switch Connection" button, and you will see "Connect to Port 1" and the value of the counter has unexpectedly stopped increasing.

View the topology of the PlayableGraph in the PlayableGraph Monitor (Tools/Bamboo/PlayableGraph Monitor).

Similar issue

If a ScriptPlayable<T> (directly or indirectly) outputs to an AnimationPlayableOutput , only its first output port is valid. Connecting to other output ports will not trigger updates for this ScriptPlayable<T> and its child Playables.

Solution

You should always ensure that the ScriptPlayable<T> connected to the AnimationPlayableOutput has at most 1 input port and 1 output port.

You can temporarily fix this issue by inserting an AnimationLayerMixerPlayable between the ScriptPlayable and the AnimationScriptPlayable.

Please refer to AnimationJobTest_TempFix.cs for more details.

Playable Graph