Search Issue Tracker
Fixed in 5.0.X
Votes
4
Found in
4.0.1f2
Issue ID
530015
Regression
No
The SkinnedCloth points get messed up when a SkinnedCloth is added to a mesh with "Optimize Mesh" and the scene is saved
Steps to reproduce :
- import the project attached
- open the "testscene"
- select Male > Robe XXXXXXX from the Hierarchy
- Add Component > Skinned Cloth
- notice that some points turn black and they can't be selected
- select the Male from the Project Browser
- click Model > Optimize Mesh ( uncheck it )
- go back to Robe XXXXXX and add Skinned Cloth again
- notice all the points are blue
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Steviebops
Aug 29, 2014 00:27
What release will fix this? There have been a few since, it's still an issue.
Logic-Artists
Dec 17, 2013 11:36
I tried disabling Optimize Mesh on my model and it seemed to help a little, but I still get tons of black points. I found a forum thread here (http://forum.unity3d.com/threads/169045-Skinned-Cloth-and-Black-Vertices) that suggested it was something with "sharp edges", so I tried calculating smoothing groups instead of importing them and turning the smoothing angle waaaay up to 180, and it actually reduced the amount of black vertices I got, but it still puts them all along the edges of the mesh. At the moment it seems kind of broken and useless, but I'm not sure if there's just something we've missed. If it turns out there's no bug, better documentation would certainly help.