Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2017.4
2018.4
2019.2.11f1
2019.3
2020.1
2020.2
Issue ID
1224213
Regression
No
Cloth component sets Renderer bounds to NaN when constraints of all vertices are set to 0
How to reproduce:
1. Create new or open an existing project
2. Add a Quad 3D Object to the Scene
3. Add Cloth component
4. Start editing Cloth constraints and set all to 0
5. Start Play mode
6. Check Console and Skinned Mesh bounds in Inspector
7. Exit Play mode and start editing Cloth constraints again
Expected result: Skinned Mesh bounds do not change, can continue editing constraints
Actual result: All Skinned Mesh bound values become NaN, bounding box errors are thrown in Edit mode, Scene view becomes blank after starting editing Cloth constraints again
Reproducible with: 2017.4.38f1, 2018.4.19f1, 2019.3.6f1, 2020.1.0b2, 2020.2.0a3
Comments (4)
-
sameng
Jan 14, 2025 04:35
Oops, meant Unity 6000.0.33f1
-
sameng
Jan 14, 2025 04:35
Still broken on Unity 6000.3.33f1
-
alpha_noob_73
Jan 12, 2025 20:35
Like Speepers, i'm also getting this issue in unity 6.0000.0.28f1
-
speppers
Jan 11, 2025 18:42
Still getting this issue in Unity 6000.0.32f1
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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a18
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b17
Resolution Note (fix version 2018.4):
Fixed in 2018.4.26f1