Search Issue Tracker
Fixed in 5.6.0f3
Fixed in 5.6.X
Votes
0
Found in
5.6.0f3
Issue ID
898923
Regression
Yes
Crash in SkinnedMeshRenderer::UploadCloths() when removing mesh with a Cloth component present
Steps to reproduce:
1. Open attached project
2. Open scene crash.unity
3. Select the Plane game object
4. Attach the Cloth component to it
5. In the SkinnedMeshRenderer component, set the Mesh to 'None'
- Unity crashes at this point
- Setting the Mesh parameter to 'None' with no Cloth component does not cause a crash
Reproduced in: 2017.1.0a6, 5.6.0f3, 5.6.0a1
Not reproduced in 5.5.3f1, 5.4.4p4
Regression since: 5.6.0a1
Verified with 2017.1.0b2 version
Comments (2)
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
stream_in_space2
Jun 01, 2017 14:18
I confirm, this steps still invoke crash. Impossible to work with cloth component, unity all time crashes in different points.
Unity 5.6.1f1 (64-bit)
TimGS
May 01, 2017 05:06
It still exists in 5.6.0p3 (it's the latest patch atm)
Why did you mark it as fixed?