When you upload an animation and overwrite it in Studio, it gets cached and can't be changed

Bug Reports Studio Bugs
,
#1

Animations that are seen in game won’t be seen in studio, even after updating them.

Repo steps

  1. Make an animation
  2. Upload it
  3. Test it in Studio by pressing play. Your changes are visible.

Now repeat:

  1. Make a change
  2. Upload it to the original animation
  3. Test it in Studio by pressing play. Your changes are visible.

This is the expected result

Now try this:

  1. Make a change
  2. Upload it
  3. Test it in Studio by pressing play. Your changes are visible.
  4. Publish the game
  5. Test it in the game by pressing play. Your changes are visible.

HOWEVER, as soon as you try to publish another change to this animation, both in Studio and in the game, you will never see a new version of that animation on this device.

Thus, we’re forced to make new animations, with new IDs, which makes updating the game really painful.

Expected behavior

I expect when I update an animation, to be able to see it, the cache should be invalidated, this is a significantly workflow issue with making animations on Roblox, especially when we’re doing lots of back-and-forth updates between animations and gameplay.

2 Likes
#2

Bug Report: Animation Asset version not updating after running servers

Steps to Reproduce:

  1. Upload an animation to Roblox.
  2. Overwrite the animation asset ID with an adjusted version or any modification.

Issue: When testing this in Roblox Studio, the expected result is achieved. In studio it actually shows the most recent version of the animation. However when the game is published with the old version and you later attempt to overwrite the animation asset ID with adjusted data, the update doesn’t take effect. Even after restarting servers it continues to play the old version.

Expected Results: The asset ID that was overwritten with the new adjustment should play the updated version of the animation.

Current Outcome: The animation playback does not play recent version and it continues to play the old version despite attempts to update it forcing a reupload of a complete new asset ID

#3

Hi there! Thanks for your report.

We have opened a ticket and will look into this as soon as possible.

Cheers!

2 Likes
#5

Hi, sorry for the long wait. Is this bug still happening for you? A couple of changes were made to caching since this was posted, and I wanted to check with you again first. I’ve been trying to repro the issue, and I’m seeing the animation not changing in Player but updating immediately in Studio.

For Roblox Player, this is currently the expected behavior because we’re trying to reduce the load on the backend. We do check for asset updates in the background, but the initial asset load will use the cache whenever possible. Sorry if this is inconveniencing you; we’ve been having some discussions about how to better handle asset updates in Player.

In Studio, we should always be fetching the latest version of the asset. If you’re still seeing the old version in Studio, then something is going wrong