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
- [Android] Texture Compression default texture format is set to PVRTC when building via script BuildPipeline.BuildPlayer
- [Android][GameActivity] APK built with Development Build enabled gets flagged as having Malware
- Default name of manually created Global Light 2D GameObject differs from the one included in the initial project Scene
- Option for "Acceleration Structure Build Flags" cannot be toggled when Lightmaps have been Generated for a Mesh Renderer
- Lights in Batch keep resetting to 0 in the Light Batching Debugger when a new GameObject is created and the mouse cursor is hovered over the Inspector window
Add comment