Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
1
Found in
2017.4.0f1
2018.3.0a1
2018.3.8f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1153027
Regression
No
Cannot remove Cloth Self-Collision and Inter-Collision when they are applied onto a GameObject
How to reproduce:
1. Open "SampleScene" Scene in the attached "case_1153027.zip" Unity project
2. In the Hierarchy tab, select the GameObject "Plane"
3. In the Inspector tab, select "Edit cloth self/inter-collision" inside the Cloth Component
4. Drag-select the "Plane" GameObject in the Scene tab
5. In the Cloth Self-Collision and Inter-Collision window, untick "Self-Collision and Inter-Collision"
6. Re-select the GameObject "Plane"
7. Repeat steps 3 and 4
-- Notice the "Self-Collision and Inter-Collision" checkbox
Expected result: the Self-Collision and Inter-Collision box remains unticked
Actual result: the Self-Collision and Inter-Collision stay applied to the Cloth Component
Reproducible with: 2017.4.26f1, 2018.4.0f1, 2019.1.2f1, 2019.2.0b1, 2019.3.0a2
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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 2018.4.26f1