Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.1.3f1
2019.2.0a1
2019.3.0a1
Issue ID
1159573
Regression
No
Mesh Renderer does not render Meshes with Sprites/Default Shader when GPU Instancing is enabled
How to reproduce:
1. Open the attached project "1159573.zip"
2. Create a Cube Prefab Instance in the Scene
3. Enable GPU Instancing on the sprite Material
4. Inspect the Cube instance
Expected result: Cube instance is rendered
Actual result: Cube instance does not render at all or renders incorrectly
Reproducible with: 2017.4.29f1, 2018.4.2f1, 2019.1.7f1, 2019.2.0b6, 2019.3.0a6
Notes:
Console throws an endless stream of warnings: Instancing: Use SpriteColor or SpriteFlip for renderers that are not sprite renderers. Values are undefined.
If GPU instancing is enabled before creating an instance, the Mesh does not render at all.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment