Search Issue Tracker
Duplicate
Duplicate in 2017.3.X
Votes
18
Found in
2017.3.0a7
2017.3.0f3
Issue ID
981132
Regression
Yes
[Regression] Hitting 'Apply' on a prefab with cloth collider creates multiple Mesh Collider components
How to reproduce:
1. Create new project file
2. Add a new 3D GameObject in Hierarchy Window
3. Add Cloth component
4. Drag GameObject to Project folder to make it a prefab
5. Select GameObject in the Hierarchy Window and repeatedly hit 'Apply' in Inspector
Actual result: Hitting 'Apply' on a prefab with cloth collider creates multiple mesh collider components
Reproduced with: 2017.3.0f3, 2018.1.0b1
Not reproduced with: 2017.2.1p1
Regression since: 2017.3.0a7
Comments (11)
-
TheKingOfTheRoad
Jul 10, 2018 20:38
Our game needs this.
-
castor76
Apr 22, 2018 13:16
Need fix for 2017.4.x !
-
Keaneo
Mar 06, 2018 07:43
Just upgraded to 2017.3. Cloth is ESSENTIAL in our game and this is requires a patch ASAP.
-
Klamore74
Feb 26, 2018 00:14
link to duplicate issue # 960479 is dead!
-
Zahidylin_Marat
Feb 22, 2018 17:34
link to duplicate issue # 960479 is dead.
-
browne11
Feb 21, 2018 01:59
Link is dead....
-
WF-AMP
Feb 19, 2018 15:09
Link to duplicate issue 960479 is dead.
-
Padrre
Feb 17, 2018 20:37
I created a script that finds all the Meshkolliders and removes them. But this is certainly not the solution ...
-
ozonex
Feb 14, 2018 13:57
I just found workaround. Disable Cloth gizmos and when applying prefab make sure Cloth component is not visible in inspector. It works for us.
Looks like it creates temp meshcollider for painting/editing tools and when hitting apply it saves it into prefab file.
-
Hodgia
Jan 03, 2018 18:31
Actually after step 4, you can see two MeshColliders are added to the prefab instance already.
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
- Previous model to world matrix is not correctly set for ASW
- More calls are made to GC.Alloc in an HDRP Sample Template when compared to the 2022.3 stream
- Generating Light Probe lighting returns inconsistent results on a specific mesh
- Two Warnings appear for every Soft Delete Operation when Deleting Sub Assets in the Project Browser
- “Item m_LightProbeSystem not found” warning is thrown when pressing the “Open” button multiple times in the Adaptive Probe Volume component warning
This is a duplicate of issue #960479