Search Issue Tracker
Fixed in 5.0.1
Fixed in 4.1.3
Votes
0
Found in [Package]
5.0.0
Issue ID
1263266
Regression
No
[2D][Sprite Shape] BakeCollider requires GC every frame even when there are no changes in SpriteShape
[2D][Sprite Shape] BakeCollider requires GC every frame even when there are no changes in SpriteShape
Repro steps:
1. Create new 2D project
2. Create new Spriteshape profile (Project tab > right-click > Create > 2D > Sprite Shape Profile)
3. Drag/instantiate spriteshape onto scene
4. Add Polygon Collider 2D component and ensure "Update Collider" checkbox in Sprite Shape Controller component is enabled
5. Enter playmode and open Profiler tab
6. Click on CPU Usage module and search for SpriteShapeController.OnWillRenderObject()
7. Observe it has GC Alloc throughout graphed timeline
Expected Results: SpriteShapeController.OnWillRenderObject() and BakeCollider should not have GC Alloc when there are no changes in SpriteShape
Actual Results: SpriteShapeController.OnWillRenderObject() and BakeCollider have GC Alloc when there are no changes in SpriteShape
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
- Desktop Linux runtime does not respect -popupwindow command line argument
- Shader Graph more options dropdown button does not open the dropdown when clicked all the way to the right of the button
- “Attempting to draw with missing bindings“ warning lacks root cause indication and is thrown each frame when StructuredBuffer is accessed on DirectX12
- Shader Graph Import Settings documentation leads to "Sorry... that page seems to be missing!" page when opened through the documentation button in the Inspector window
- Unexpected Material change/transparency when switching between ShaderGraph and material at runtime in HDRP
Resolution Note (fix version 5.0.1):
A fix for this issue is available on Unity 2020.2.0b1 and above
Resolution Note (fix version 5.0.1):
A fix for this issue is available on Unity 2019.4.10f1 and above with 2D SpriteShape 3.0.13 package
Resolution Note (fix version 4.1.3):
A fix for this issue is available on Unity 2020.1.4f1 and above with 2D SpriteShape 4.1.2 package