Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
5.6.1f1
Issue ID
946809
Regression
No
Setting all boneWeights to 0 makes Renderer Bounds infinite and spams 'Assertion failed' errors
Steps to reproduce:
1.Open attached “BoneWeights.zip” Unity project
2.Open scene “Test"
3.Enter Play mode
Expected results:
Errors are not being spammed
Actual results:
Many different ‘Assertion failed’ errors are being spammed
Reproduced in: 2017.3.0b4, 2017.2.0f3, 2017.1.2f1, 5.6.4f1, 5.5.5f1, 5.4.6f2, 5.4.0f1
Note: if even a single boneWeight is not 0, no errors are being spammed
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment