Search Issue Tracker

Fixed in 2019.3

Fixed in 2018.4, 2019.2



Found in


Issue ID




Adding Cloth component to SkinnedMeshRenderer changes its bounds



Reproduction steps:
1. Open project attached(
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 (12)

  1. Da37c8122786e06969aca297cb5c264b?d=mm


    Sep 08, 2019 16:16

    It is fixed in 2018.4.8

  2. 1ef184756ff2918aaeb80a5ae3e61515?d=mm


    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...

  3. Da37c8122786e06969aca297cb5c264b?d=mm


    Aug 16, 2019 12:28

    Ok, my previous solution does not work in particular builds. Pretty sure this problem started appearing with 2018.4.3f1 there is also mention in the changelog: Physics Fixed issue with bounds in SkinnedMeshRenderer. (1153167)

  4. Da37c8122786e06969aca297cb5c264b?d=mm


    Aug 15, 2019 18:48

    I had the same issue I couldn't upgrade to 2019.2 due to various other cloth bugs so I just force the skinned mesh renderer bounds in a script. This might help someone.

  5. 1ef184756ff2918aaeb80a5ae3e61515?d=mm


    Aug 07, 2019 07:26

    Not sure if this is the same issue or not, but I still get missing Cloth in 2019.2.0f1 when a Cloth component has "Update When Offscreen" unchecked. I have to toggle it, then toggle it off again to make the Cloth appear.

  6. 07bde68c57c6fb67c4add8dfe45b97ad?d=mm


    Aug 05, 2019 11:37

    I still have this problem in 2019.4.5

  7. 35b4b87227af8f7606f74ecc6ddecd32?d=mm


    May 27, 2019 12:04

    Same issue in Unity 2019.3.0a2 with HDRP.

  8. Bc39b8f327c5525e68344e45f6a26e45?d=mm


    Apr 13, 2019 17:31

    Could you please release an hotfix for 2018.3? Nit a single business could update to the alpha (and unstable) version of 2019 just to have an important fix like this

  9. A97946457721fe85bf9b934c927016a6?d=mm


    Mar 07, 2019 06:41

    Seriously this has not been fixed, thats insane ?

  10. 4d91a12973a190c05d42abe27c201f82?d=mm


    Apr 30, 2018 19:22

    Still there with 2017.4...I face every possible bug, damn it!

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.