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
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
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