Search Issue Tracker
Fixed in 5.6.0
Votes
2
Found in
5.5.0f3
Issue ID
857443
Regression
No
[GC Alloc]Playables API "SetInputWeights()" method generates tons of garbage collector allocation
Steps to reproduce:
1. Download and open the attached project.
2. Open the Profiler window
3. Enter play mode
Expected result: no, or minimal GC Alloc
Actual result: SetInputWeight generates a lot of garbage collector allocation
Reproduced on: 5.3.7p2, 5.4.4f1, 5.5.0f3, 5.5.0p3
Unable to test on 5.6 because the Playables API seems to not work
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
- Graphics.Blit() performs the operation only to the last display when a multi-display environment is used
- [Windows] Multiple Separation Lines are present in the Light Create Menu
- Warning "Item m_LightProbeSystem not found in window PC_RPAsset" logged when navigating to RP Asset from Probe Volume Component
- Editor UI is pink when a project has builtin_shaders-2021.3.11f1
- Tessellation has poor performance in URP when rendered using Metal
PhilSA
Jan 19, 2017 15:46
I tested it in 5.6b4 after these examples were posted : https://forum.unity3d.com/threads/animationclipplayable.451854/#post-2926897
The GC alloc for SetInputWeight() seems to be gone completely now. The problem appears to be fixed
TheValar
Jan 13, 2017 18:34
This is a huge problem. I think many use-cases for this system involve setting input weights every frame. For me this is basically unusable until this is fixed :(