Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.3.X
Votes
0
Found in
2019.4
2021.1
Issue ID
1290726
Regression
No
Adding Cloth component to MeshRenderer results in incorrect bounds
Repro project attached - BuiltInSpotLightTest.zip (54.7 KB)
It happens in both built in and URP
- Create an empty scene
- Add Meshes/HouseWip1_fbx to the scene
- Select Cube.012
- Add cloth component
- Click Edit bounds on SkinnedMeshRenderer
- Observe the incorrect bounds https://i.imgur.com/REa3ma6.png
Notes:
- Adding a SkinnedMeshRenderer instead of the cloth component does produce correct bounds.
- As soon as you add the cloth component the bounds become bad.
Not sure if this is still valid:
Repro in 2021.1, 2019.4 & 2018.4(although it appears less consistently here?)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2021.1):
Fixed in: 2021.2.0a4
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0b10
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.1f1