Search Issue Tracker
Fixed in Unity 2018.2
Votes
1
Found in
2017.1.0f3
Issue ID
962027
Regression
Yes
When a Mesh is assigned to a SkinnedMeshRenderer with a Cloth component attached, the Cloth loses its constraints if it's active
How to reproduce:
1. Download attached project file and open "Scene" Scene
2. Enter Play Mode (observe how while the 'ClothCopier-Works' example shows a cloth that sways in place, the 'ClothCopier-Doesntwork' example flies away since it doesn't have any constraints)
Actual result: Replacing the instantiated mesh into the SkinnedMeshRenderer, the associated Cloth component loses all its coefficients, but only if it's enabled at the time. Disabling the GameObject (or the Cloth component) before the new mesh is assigned keeps the coefficients around
Reproduced with: 2017.1.2p2, 2017.2.0p1, 2017.3.0b8, 2018.1.0a2
Not reproduced with: 5.5.5.f1, 5.6.4p2
Regression since: 2017.1
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
- [Presets] DefaultInpector type needs to be blacklisted
- Default Inspector Header is shown when double clicking on a scene
- [LWRP] Base map is missing on some materials after upgrading LWRP package
- Metal error when using subsurface scattering in HDRP
- gameObject.SendMessage doesn't accept value as a function argument correctly in the .NET 4.x Scripting Runtime
AFrisby
Mar 22, 2018 04:38
*bump* Any fix in 2017.2?
AFrisby
Feb 26, 2018 07:29
See this is now fixed in future release - any indication which release?
AFrisby
Dec 22, 2017 01:09
Any ETA on when this is likely to be fixed?