Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
Issue ID
879548
Regression
Yes
SkinnedMeshRenderer's Mesh looks strange when different mesh is selected if object has cloth component
To reproduce:
1. Create a new project.
2. Create Empty game object.
3. Add "Cloth" component to it.
4. In "Skinned Mesh Renderer" select any default mesh (for example Sphere)
5. Now Select a different mesh. (for example Plane)
Expected result: Mesh looks normal.
Actual result: Mesh looks different than it should.
Reproducible: 5.5.0a6, 5.5.1f1, 5.6.0b7
Not reproducible: 5.4.3p1
Workaround:
It fixes itself when Play is pressed. Or when "Cloth" component is removed.
Also it gives 2 errors:
[Physics.PhysX] PxScene::addActor(): Actor already assigned to a scene. Call will be ignored!
UnityEditor.HostView:OnGUI()
[Physics.PhysX] PxScene::addActor(): Actor already assigned to a scene. Call will be ignored!
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
Add comment