… YAY!
Pretty good update, i love it.
15 Likes
My scripts only access the published animations directly. With that being said however, I remove the animations when I move things over to the published game. I like to keep the animations around in case I need to modify them for whatever reason later down the road.
14 Likes
Not everyone animates in a baseplate?
So this is how the other half lives…
12 Likes
Apart from the fact that theyll have to migrate to instance attributes, making any developed workflows obsolete?
13 Likes
Right? I saw this and I was thinking, oooh, I can improve my game’s load time.
Checked my game. I have no rig in workspace with animsaves in it.
Apparently, I moved the rig to serverstorage after I was done making animations with it.
I wouldn’t think enough devs are leaving these dummies lying around in workspace to warrant an effort such as this to contain it, but here we are.
15 Likes
No it has nothing to do with blending…
Im referring to this: https://devforum.roblox.com/t/failed-to-load-animation-sanitized-id/2556354
13 Likes
Okay, that bug looks unrelated from this update (and the changes from this update haven’t been made live yet). After digging deeper in the bug report, there were several reasons provided as to why that error occured, and solutions were also provided.
To answer your original question, “wonder if this has anything to do with the issues,” the answer is no. 
11 Likes
solutions may have been provided but that doesn’t mean they worked… literally every “solution” recommended was like “your obv not the owner of the anim” or “make sure its not a group anim”.
11 Likes
Unnecessary change, you shouldn’t leave Animations inside characters in Workspace/ReplicatedStorage anyways, if it’s not supposed to be in the game, it’s not supposed to be in the places replicated to the game.
This helps nobody but unorganized people, while making a change that affects existing plugins.
How are things like this approved? it’s not like the priority list for Roblox is empty or anything.
13 Likes
Are you still running into this, and if so how recently?
This was caused by an internal issue thanks to heavy load over thanksgiving and should be fully resolved now.
12 Likes
This is a great change! On a slightly unrelated note, will we ever see a change to how curve editor rotation is handled? Right now if any axis for rotation goes above 180 or below -180, it flips for that keyframe, which causes unwanted spinning on the affected limbs.
This is a major hinderance to animation workflow that make use of the curve editor, this issue was brought up in another post, and in response we were told to fix the curve keyframes manually, but if you make any kind of change to the animation after fixing the keyframes, the curve keyframes flip again.
The only real workaround I’ve found is to animate the entire animation without the curve editor enabled, and once the animation is done, enable it and do your curve editing from there.
13 Likes
Yes I and most of my discord members seem to face this issue almost daily. and while it does resolve shortly after (around 30 mins) its still a pain to have to wait and test animations.
8 Likes
I’ve been recklessly leaving these animsaves in my games haha
Nice change
9 Likes
They won’t “have” to do that, no. Load times are more important and I like that they are doing this now rather than waiting for an unspecified future with instance attributes when the load time impacts will be the same.
8 Likes
the types of people to leave animsaves in production rigs are the same people who leave all their server code in modulescripts in workspace i can’t believe this was a necessary change
8 Likes
Why is there no beta opt-in for it already so one can explore this new change 
6 Likes
Hi there, thanks for your feedback.
The main reason we didn’t implement this as a beta feature is that if users have the possibility to opt-in, they also have the possibility to opt-out, and opting out after the animations have been migrated won’t move them back to the original place anyway. This is something experienced developers can easily do, but that can be more complicated for new developers.
Nevertheless, we will re-evaluate the implications of releasing this as a beta feature.
Cheers!
9 Likes
We’ve made an additional fix which should solve the issue with transient animation loading failures once and for all. (You’ll still be able to get the error if you’re legitimately missing permissions of course)
Let us know whether this gets things resolved for you.
8 Likes
I’m not sure if it’s related, but it seems like I’m getting the error when loading Roblox owned animations now (specifically the DefaultFallbackMoodAnimation)
8 Likes
please any roblox staff could see this ?
6 Likes