I’ve been recklessly leaving these animsaves in my games haha
Nice change
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.
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
Why is there no beta opt-in for it already so one can explore this new change
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!
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.
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)
please any roblox staff could see this ?
None of this makes sense to me just stop changing things for 5 seconds of extra loading time
Speaking of animations. Does any DEV know about the issues with emotes it seems like we dont have permission to use them in our game unless we have the original animation ID instead of the emote ID which we aren’t able to get with animation IDS. ALSO YOU GUYS NEED TO FIX THE ANIMATIONS COLLDING WITH EACH OTHER ISSUES UR FREAKING ME AND GIVING ME ALL THIS TRAUMA BC U DONT WANNA FIX OLD STUFF AND ADD STUFF WE DONT NEED LIKE CALLING
Its less loading time not extra.
I do not care that what i meant anyways
I aee no issue with this update. Having less loading time is always good.
If by animations colliding you mean two animations of the same priority then either change the priority or aet the weight properly.
It isnt a bug, its animation weight. Its a feature.
Emotes have animation weight? I’ve been using emotes in my game and they collide and have issues. it seems like a issue on roblox half (Also these emotes are forced to stop and they continue) the whole emote thing is just weird itself why are they like 2 different category nothing is making sense anymore on roblox
All animations have weight. If you have more than 1 animation on core priority it will blend the others by average on default. Roblox puts all of its animations including emotes on Core.
Just adapt
So I’d have to convert them all to have 0 weight? that seems unnecessary these animations should just work how they should work. They play and they stop. this feature should only be used by devs who wanna use it
This update has nothing to do with your problem. Just use a priority above core. Its that simple.
seems it affects to hands of Characters when want both arms to move, one of both that will lose accuracy, hard to make it better and edit, can you add a button on Setting Studio can be toggle between using Old/New Animation Editor for easy use(Like “Use2022Material” on MaterialService)?
seems this new animator editor make hard to create a new aniamtion like move many part of body, it’s not perfect like last version, can you add a button on Setting Studio can be toggle between using Old/New Animation Editor for easy use(Like “Use2022Material” on MaterialService) pls, this is so hard to use?