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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment