Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.3.X
Votes
0
Found in
2018.1.0a1
Issue ID
960479
Regression
Yes
Mesh Collider keeps adding on prefab in the hierarchy when selecting it from the project folder
After adding cloth component on a prefab from project folder, selecting prefab in the hierarchy mesh collider keeps adding up and throws errors in the console.
To reproduce:
1. Create new unity project
2. Create cube in the hierarchy
3. Drag it to project folder to make it a prefab
4. Select the prefab in the project folder and add cloth component, notice as there is no Mesh Collider
5. Select the prefab in the hierarchy
6. Observe as the mesh collider appeared on the prefab
7. Repeat steps 4 - 5 and observe as the prefab in the hierarchy gets more and more Mesh Colliders
Expected result: mesh collider does not add up on the prefab
Actual result: mesh collider keeps adding up on the prefab
Reproduced on: 2017.3.0b1 2017.3.0b5 2018.1.0a1
Not reproduced on: 2017.2.0f3 2017.3.0a3 2017.3.0a6
|Regression introduced in: 2017.3.0a7
Notes: also reproduces on MAC.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Chipinators
Apr 23, 2018 20:48
Not fixed in 2017.3.1f1 really need this fixed asap.
Poxican
Apr 15, 2018 16:51
As others have said, this is very much still an issue in 2017.
drcrck
Apr 03, 2018 10:13
not fixed in 2017
Daeruk
Mar 08, 2018 19:40
not fixed
Keaneo
Mar 06, 2018 07:45
How can this be considered "fixed" - it is still present in latest stable version, downloaded from Unity homepage, 2017.3.1f1?