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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment