This is a summary of the Animancer v5.3 Change log.

When upgrading to a newer version of Animancer, you must delete any previous version from your project first.

See the Animancer v5.0 Upgrade Guide if you are upgrading from a version older than that.

Experimental

Several changes are currently being considered for the next major version (v6.0). Any feedback would be appreciated.

• Add a StateChange class to the FSM system instead of passing the previous/next state into the CanEnterState and CanExitState methods.
• Restructure the way Animancer Event callbacks are accessed in code.

Changes

• Reworked Mixer Synchronisation to fix several bugs:
  • Mixers now keep a list of references to the synchronised child states rather than a bool[] that indicates which children are synchronised.
  • This is slightly more efficient (significantly for nested mixers).
  • Added MixerState.AutoSynchroniseChildren to control whether newly added children are automatically added to the synchronisation list (default true).
  • Fixed it to work properly on nested mixers by giving their synchronised children to the parent mixer to synchronise them all together so that the outcome is not based on the non-deterministic AnimancerNode update order.
  • Fixed it to keep states synchronised even when none of those states have any Weight.
  • Fixed it to work properly with LinearMixerState.ExtrapolateSpeed.
  • Fixed it to work properly with negative speeds.
  • Fixed it to work properly with zero length states.
  • Added OptionalWarning.MixerSynchroniseZeroLength.
• Animancer Event markers on the TimeRuler can now be dragged to move their time.- Improved the PlayableAssetState binding system:
  • The “Markers” track in Timeline Assets is now automatically skipped.
  • The PlayableAssetState.Transition Inspector now highlights the size of the Bindings array as a warning if it does not match tracks in the the assigned Asset.
  • The track names are now used for their respective Bindings fields (instead of the default “Element X”).