Search Issue Tracker
Fixed in 2017.2.0f3
Votes
1
Found in
5.6.0f3
Issue ID
903687
Regression
Yes
Animator.SetLayerWeight CPU usage is increased compared to 5.5
Steps to reproduce:
1. Download 903687_repro.zip and open "test" scene
2. Open profiler and enter play mode
3. In Profiler check BehaviourUpdate->SetWeightTest.Update()
Expected results: CPU usage should be around 0.2% same as in Unity 5.5
Actual results: CPU usage is around 2% also some times CPU usage spikes up to 15%
Reproduced with: 2017.1.0b1, 5.6.0p2, 5.6.0b1
Not reproducible with:5.5.3p2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment