Search Issue Tracker
Fixed in 2020.2.X
Votes
5
Found in
2018.2.0a1
2018.4
2019.3
2019.3.5f1
2020.1
2020.2
Issue ID
1229548
Regression
Yes
SkinnedMeshRenderer not being rendered in Build
Reproduction steps:
1. Import the attached package "b123.unitypackage"
2. In the Project window drag and drop the "GameObject.Prefab" into the Scene view
3. Build the Project
Expected result: SkinnedMeshRenderer is rendered in Build
Actual result: SkinnedMeshRenderer does not render in Build
Reproduces on:2018.2.0a1, 2018.4.19f1, 2019.3.6f1, 2020.1.0b2, 2020.2.0a4
Does not reproduce on: 2017.4.38f1, 2018.1.9f2
Notes:
-MeshRenderer works as expected
-Does not reproduce on a New Project
-List of things the user tried as a workaround without results
- Disabling of "Dynamic Occlusion" on SkinnedMeshRenderer
- Enabling of "Update When Offscreen" on SkinnedMeshRenderer
- Editing of SkinnedMeshRenderer bounds
- Tweaking of Culling Mask on camera
- Near/Far clipping plane
- Toggling "GPU Skinning" and "Depth and Stencil" in player settings
- Various mesh export settings and formats in Blender
- Unity version update
- Using Universal Render Pipeline and different Graphics APIs
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
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
- Warnings due to obsolete Object.FindObjectsByType<T> usage and [SerializeReference] are logged when opening the Netcode for Entities setup scene
- Non-standard pointers cannot change Inspector values with arrow controls when crossing Inspector area
- No longer able to change the Toggle or Slider GameObjects' Target Graphic value and a NullReferenceException is thrown when the Target Graphic value is set to None at any point
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a6 by updating info message in the Inspector