Search Issue Tracker
Feature Request
Feature Request in 6000.4.X
Votes
0
Found in
6000.0.58f1
6000.2.7f1
6000.3.0b4
6000.4.0a1
Issue ID
UUM-121030
Regression
No
"ProcessRootMotion" method is called when "Apply Root Motion" is disabled in the Animator
How to reproduce:
1. Open the attached “IN-118908_ProcessRootMotionPerformanceBug” project
2. Open the “SampleScene”
3. Enter Play mode
4. Select the Profiler tab
5. Select a frame to monitor, by clicking anywhere on the chart
6. Observe the Main Thread in the details panel
Expected result: “AnimationScriptPlayable.ProcessRootMotion” is not present
Actual result: Three instances of “AnimationScriptPlayable.ProcessRootMotion” are present in the Timeline
Reproducible with: 2023.1.0a1, 6000.0.58f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Reproducible on: macOS 26.0 (M1 Pro)
Not reproducible on: No other environments tested
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
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
Resolution Note:
The behavior is as-designed, and would represent a change outside the scope of a bugfix.
Therefore we will close this bug, and process this instead as a feature request.
Thank you for providing these assets supporting your request, we will be using them to inform our investigation into this improvement.
Resolution Note (6000.4.X):
The behavior is as-designed, and would represent a change outside the scope of a bugfix.
Therefore we will close this bug, and process this instead as a feature request.
Thank you for providing these assets supporting your request, we will be using them to inform our investigation into this improvement.