Temporary animations created using AnimationClipProvider:RegisterAnimationClip() will not play on the client when in multi-client testing mode. The animation will still play normally on the server side. This bug doesn’t happen when using the regular testing mode.
The video below shows a temporary animation replicating from client to server but not playing on both.
The same things happens for animations replicated from server side to client side.
On client side, Animator.AnimationPlayed still fires with the animation track.
On client side, AnimationTrack.Stopped will never fire.
Hello, thank you for your patience. We have spent some time investigating this issue and determined it is expected behavior as this is a test function for use in local-only testing:
RegisterAnimationClip is not designed to work in a multi process scenario (as in actual regular client ↔︎ server model). Right now it will work on RCC if a server script calls RegisterAnimationClip and it will work on clients if a client script calls RegisterAnimationClip, but to have this work for both you will need to follow the instructions noted here and publish the animation:
Developers wishing to generate an asset ID that can be used online should upload the AnimationClip to Roblox.
Please reach out if you have any questions or further issues. cc @NotARobloxEngineer
If it matters at all, the reason I’m not just uploading my animations is because I have a jank research setup where I have to preprocess the keyframes of my animations. So creating temporary animations helps me iterate faster.
Really nice movement and animation work. And got it, good to know that iteration speed is the primary benefit, which makes total sense, it’s just not unfortunately how the function is designed to work. I copied one of our lead engineers on this thread in case there is anything else we can do to assist your workflow.