Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.2.X, 2019.3.X
Votes
1
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1153439
Regression
No
[Cloth] The constraints do not match the scale of the object and are too large when the mesh has a high vertex density
How to reproduce:
1. Open the attached 'Constraints.zip' project
2. Open 'SampleScene' scene
3. Go to the Hierarchy tab -> 'Model' -> 'mesh'
4. In the Inspector press 'Edit Cloth Constraints' button and observe constraints
5. Observe and compare constraints of 'Cube1', 'Cube2', 'Cube3'
Expected result: Constraints match the scale of the objects and don't overlap
Actual result: Constraints do not match the scale of the objects
Reproducible: 2017.4.27f1, 2018.4.1f1, 2019.1.4f1, 2019.2.0b3, 2019.3.0a3
Comments (1)
-
NathanRH
Aug 16, 2019 13:35
Yes, we just need to have the size of these spheres exposed in the editor...
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
- "Assertion failed on expression" errors appear when selecting specific Tile Palette GameObjects
- “CommandBuffer: built-in render texture type 3 not found while executing” warning is displayed in URP project
- Player build logs a "material with shader doesn't have a '_MainTex' property" error when instantiating a specific amount of specific prefabs
- The LayerMask parameter is ignored when using Physics2D.GetRayIntersection method
- The Tilemap GameObject causes other Tilemap GameObjects to become invisible when its “Mask Interaction” is set to “Visible Inside Mask”
Resolution Note (fix version 2020.1):
The bug was fixed by adding the ability to vary the constraint size. It could be found in the "Constraint Size" setting under "Brush Radius" in the Cloth Constraints panel.
Fixed in: 2020.1.0a3
Backported to: 2019.2.15f1, 2019.3.0b7