ansonlouis

Well, it must have been amazon caching it, as your link now seems to point to 3.2.0 where the original time I opened that link it was 3.1.2. Using the updated 3.2.0 does seem to resolve the issues I was seeing. Thanks!

In the same codepen, I removed the 3.1.1 asset and added the link you gave above in the JS settings. Without changing code and only swapping the asset, the animation jumps and is not smooth.

Thanks for the response. After using the supplied 3.1.2 beta, I'm seeing a lot more issues frankly (animations not smooth, callback still acting weird). I've reverted to 3.0.5 and I'm seeing the original issue no longer happening and everything seems to be working.

Maybe I'm overlooking something obvious, but I'm consistently seeing the master timeline's "onComplete" callback firing before the animation is complete. I'm using a toggle button to switch between a paused and play state. The reduced codepen example reproduces the case. Reproduction Steps: - Open the code pen link and have the browsers devtools open (console tab) - Click the toggle button to start the animation. - Click the toggle button again to pause the animation around 1 second or so into the whole animation. - Wait a couple seconds in the paused state - Click the toggle button again to resume the animation. You should see a console.log indicating the `onComplete` callback was called. The animation is clearly not over yet. Expectation: I would expect the onComplete to not fire until the child timeline is complete. I would expect the child timeline to not be considered complete until its two child tweens are complete. It doesn't seem like that is happening.