Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Votes
10
Found in
5.5.0p3
Issue ID
879696
Regression
No
Adding Cloth component to SkinnedMeshRenderer changes its bounds
Reproduction steps:
1. Open project attached(UnityBugRepro.zip)
2. Open scene (test)
3. Select Rig_Male_Thief_Thug -> Rig_Male_Thief_Thug_Body
4. Add cloth component to it.
Expected result: SkinnedMeshRenderer bounds will stay in its place.
Actual result: SkinnedMeshRenderer bounds changes position.
Fixed in: 2019.3.0a3
Reproduced on: 5.3.7p3, 5.4.4f1, 5.5.1p3, 5.6.0b8.
Comments (34)
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
- Tile Palette grid is moved after entering Play Mode
- Tile Palette Edit mode turns off in Play Mode
- The Editor crashes when Generating Font Atlas in the Font Asset Creator with “9999999999” padding and 256x256 Atlas Resolution
- [iOS] An “ArgumentNullException” error is thrown when GetIntroductoryPriceDictionary() method is called
- Font Import Settings documentation page is missing when the documentation button is pressed in the Inspector window
TacticalShader
Apr 24, 2020 07:38
Still happening in 2019.3.7f1
terry213
Apr 20, 2020 02:57
(Continuing on my last comment...) Also setting root bone on Skinned Mesh Renderer to None
terry213
Apr 20, 2020 02:53
I'm using Unity 2019.3.0f3 and I think I may have found a solution, at least for simple cloth like a flag drooping down. I made a joint chain for a simple plane in maya, bind the plane to the joints, then export. Afterwards I put the binded plane in my scene and on Skinned Mesh Renderer component, I ticked Update When Offscreen to True. I'm not sure about other complicated meshes, but it seems having a joint hierarchy worked for me.
aleannox
Apr 17, 2020 19:29
Still present in 2019.3.17
I cam up with this fix: https://gist.github.com/aleannox/207c0089f98eed4d78706ab8fc240b9a
IamAnewUser
Mar 10, 2020 13:56
I'm really starting to get mad at Unity. "Fixed in 2018.4, 2019.2, Fixed in 2019.3" my @$$. Every bug that is marked "Fixed" has a 70% chance that it's NOT "fixed" and then they refuse to reopen the issue >:(
The only one who really helps with the bugs is the community that finds a workaround.
What does the "S" in "LTS" stand for? "Sham"? Long Term Sham?
PS : 2020.1.0a22 and still not working. And, no, It doesn't work in the LTS versions(eg 2019.3.4f1) either.
stonebits
Feb 09, 2020 23:26
I'm seeing this in 2020.1.0a22
studentfirst18
Feb 08, 2020 16:55
Heres a possible fix that worked in my case. https://www.polygon-treehouse.com/blog/2017/8/4/howtoponcho
It says to add a empty game object, then add skin mesh renderer component, and finally add the cloth component. This worked for me and fixed the scaling issue. Hope this helps
MostHated
Oct 17, 2019 19:00
None of the proposed fixes are working for me on 2019.2
ElasticSea
Sep 08, 2019 16:16
It is fixed in 2018.4.8
Skjalg
Aug 26, 2019 09:40
What does it mean that this is "By Design" in 2018.4 ? It broke during 2018.4 development...
So much for LTS being the safest option for us developers...