AnimationTrack.Looped Does Not Replicate

I think at this point we just accept that Looped does not replicate

Hey mate, any luck yet? Still having the issues.

9 Likes

bro when will this thing be live? it has been months now :face_exhaling: :sob:

2 Likes

Thanks for your feedback and years of patience!
The Looped Property of AnimationTrack should now replicate!
Feel free to give it a try, and let us know if you encounter any unexpected behavior.

12 Likes

Iā€™m still experiencing this problem. Iā€™m Playing an AnimationTrack on the client, which is a short animation that is looped. When played, the server and other clients will see the animation play once with the defined weight. However, while the client playing the animation will see the animation loop, the server and other clients will not.

1 Like

Still does not work.

I setup a simple studio place where I created an animation that in the editor has looped set to true.

I then played in a server script the animation on my character, setting the animation trackā€™s looped to false (I tried setting it both before calling :Play() and after).

The animation does not loop on server but on client is looping despite having set loop to false.

There are still replication issues when playing animation tracks on the server, though also found a few workarounds to hopefully help with debugging this bug internally. This was tested on an empty baseplate.

The animation was a non-looped animation, and I attempted to set the Looped property of the animation track through a server-side script. The animation loops properly on the server, but without workarounds will not replicate the loop to the client.

Setting the Looped property before playing the animation failed to replicate the loop.

local animaitonTrack = Animator:LoadAnimation(animation)
animaitonTrack.Looped = true
animaitonTrack:Play()

Workaround 1

Playing the animation before setting the looped property seemed to fix it for me, through @Askavix has also noted otherwise so might not be a reliable fix.

local animaitonTrack = Animator:LoadAnimation(animation)
animaitonTrack:Play()
animaitonTrack.Looped = true

Workaround 2

Another stranger fix Iā€™ve found is creating the exact same animation track twice. For some reason, the second animation track will properly replicate, even when setting the property before playing the animation (which didnā€™t work previously).

Definitely hacky, but might be a good lead for investigating this bug further?

local animaitonTrack = Animator:LoadAnimation(animation)
animaitonTrack.Looped = true
animaitonTrack:Play()

animaitonTrack = Animator:LoadAnimation(animation)
animaitonTrack.Looped = true
animaitonTrack:Play()
1 Like

6 years later, still an issue, is the team still aware of this?

That bug still exist, and not only looped gets broken, the client cannot replicate stoping the animation. After the client stopped the animation it still being played for other people

Iā€™m still experiencing this issue. Iā€™m playing an AnimationTrack on the server, set ā€œloopedā€ to false for that animation, and it still plays as looped on the client. I have a very large bunch of mesh animations that I would have to go through and somehow just reupload without the loop and it would make 100% more sense if the animationtrack loop property just replicated properly instead.

1 Like

Still a problem today, sadly none of the workarounds posted here worked for me. Please do something about this!!! Its been years!

Still happens as of today, roblox noticed this back in october 2018. So, itā€™s been 6 years since.

1 Like

I just recently started looking into animations and, dang, this is a disappointing bug. The documentation even suggests using the track Looping property, which doesnā€™t work.

Hereā€™s a little workaround I found, assuming the animation is published with looping set to off:

local track = script.Parent:LoadAnimation(animation)

track.Stopped:Connect(function()
	track:Play()
end)

This simulates a loop which properly replicates. You could throw in some kind of condition check to stop the loop if needed.

1 Like

Bug still not fixed after 6 years, thanks Roblox.