@fitpighter Thanks for getting back to us. While it might solve one issue, calling skeletonAnimation.ClearState() or skeletonAnimation.AnimationState.ClearTracks() is not recommended since you then don't get mixing between two successive animations (no smooth crossfade transition from one animation to another). Additionally, it is wasting CPU cycles for the clear operation which should not be necessary before adding an animation. We would recommend investigating the cause of the problem.