Search Issue Tracker
Fixed in 2017.2.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
0
Found in
2017.1.0p4
Issue ID
946068
Regression
Yes
SkinnedMeshRenderer property sharedMesh is null when created via script
Reproduction steps:
1. Download project "TestProject.zip" and open in Unity
2. Open scene "testscene"
3. Enter Play mode
Expected: SkinnedMeshRenderer property sharedMesh should be initialized
Actual: code line "newSkinnedMeshRenderer.sharedMesh = new Mesh();" triggers error in Unity console:
"SkinnedMeshRenderer: Trying to set a mesh ("") that is unfit for use with SkinnedMeshRenderer. Most likely it doesn't have Skin information and/or is only assigned to the renderer during runtime, in which case Unity isn't aware of its use with SkinnedMeshRenderer. Mark the mesh as Readable or assign it to the renderer in the Editor before building.
UnityEngine.SkinnedMeshRenderer:set_sharedMesh(Mesh)"
Reproduced on: 2017.1.0p4; 2017.1.1f1; 2017.2.0b9; 2017.3.0a6
Not reproduced on: 5.5.4p4; 5.6.3p2; 2017.1.0f3; 2017.1.0p3
Regression started: 2017.1.0p4
Fixed on: 5.6.3p3; 2017.1.1f1
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
ecurtz
Oct 13, 2017 19:16
This is NOT fixed in 2017.2 - why isn't there a way to mark it as a regression?
spiritworld
Oct 12, 2017 17:35
I used 2017.1.1f1 and everything was fine. Today I installed 2017.2.0f3 and: kaboom, this bug appeared.
Peter77
Oct 03, 2017 05:51
Related forum thread:
https://forum.unity.com/threads/unity-bug-946068.498495/
jmitcheson
Oct 03, 2017 03:38
Oooo! It's fixed in 2017.3b2. It seems this fix never made it into 2017.2 though - I hope it will make it in soon.
jmitcheson
Oct 03, 2017 03:15
Not fixed in 2017.2.0f2 either (tested with project above)
Breaks pretty much all mesh baking!
Jason-RT-Bond
Sep 22, 2017 19:49
Despite the indication above, this does NOT seem to be fixed in 2017.2.0f1.
Reproduction: Download the free asset UMA Multipurpose Avatar 2.0, import into a fresh project, open any of the example scenes and run.
Could you please indicate which version of 2017.2.x a fix should be included in?