In the next phase of the rollout, we’ll remove the
Workspace.ClientAnimatorThrottling property, which means throttling will be enabled automatically for all places. We are committed to resolving any issues before this last phase of the rollout. Therefore, we want to hear from you about how animation throttling affects your places, especially if you either enabled or disabled the workspace property directly.
TL;DR for the Animation Throttler:
- It improves performance particularly in places with lots of animated characters by throttling off-screen and far away characters more intensely.
- Currently runs only on local clients.
- Animation throttling is applied only to characters that are remotely simulated.
For example, your own avatar should never throttle in this system since it’s locally simulated.
- On every animation update, the throttler collects high level performance stats, as well as per-character visibility information to determine a throttling intensity for each character.
[Resolved] Skinned Animations + RigidContraint issue - this issue was mistaken for an animation throttling issue, as it was causing Animations for skinned modes that used
RigidContraintsto throttle. We isolated the issue to a bug in the physics system resolved it in May.
If you have encountered issues with the Animation Throttler in your places or want to share any other feedback about the feature, please let us know below!