Search Issue Tracker
By Design
Votes
4
Found in
2018.1.0f2
Issue ID
1039311
Regression
No
Animators.ProcessRootMotionJob uses a lot of resources even when humanoid character is not in camera view
How to reproduce:
1. Open attached project "Animator Events Tests.zip" and scene "SampleScene"
2. Open Profiler window
3. Enter Play mode
4. In Profiler window search panel write "animators." (easier to see the process)
5. In Scene view, look at the characters
6. In Profiler window, observe Animators.ProcessRootMotionJob and Animators.IKJob
7. In Scene view, look away from all the characters
8. In Profiler window, observe Animators.ProcessRootMotionJob and Animators.IKJob
Expected result: both processes do not consume any resources
Actual result: Animators.ProcessRootMotionJob consumes quite a lot of resources even though the characters are not seen
Reproducible with: 2017.1.4f1, 2017.2.3f1, 2017.4.4f1, 2018.1.2f1, 2018.2.0b5
Resolution reason:
Core parts of the Animation evaluation are happening in those passes:
- Process Root Motion
* Animating the root bone (even when not evaluating as Root Motion)
* Updating clip times and reading new clip values
* Collecting Animation Events
- IKJob
* Human unrolling of roll bones after retargeting
-
Xerioz
Sep 11, 2018 20:16
Same here, all root motion is disabled, yet ProcessRootMotionJob is still taking up a big chunk of CPU. Even when LOD Group hides the object, root motion is still active.
-
hal_tajima
Jun 11, 2018 08:20
Generic has similar problems.
When playing animation, it will occur frequently when it comes to the second half (per 7200 frames).
And 60 FPS can not be maintained.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Symlinks are broken when a package which contains .xcframework + symlinks is added through Unity Package Manager.
- Crash on ApplyMaterialPass when opening a specific scene
- Memory leak when using Native Plugin in Windows IL2CPP Build
- [URP][Tutorial] Universal 3D Sample tutorial issues
- Gradle error: "...Unexpected error during link..." is thrown when building for Android and targeting API Level 34
Resolution Note:
We are closing this bug since the regression was introduced in 5.0 and the new buggy behaviour is there since 3 major version, We can't just fix it because it may break other projects relying on the new behaviour.
We did add a new item on our road map to get back the old behaviour. see description provided by david geoffroy for detail