Search Issue Tracker
Feature Request
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
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
- Group Node name text is way smaller in the renaming state than the actual display size
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.