Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
9
Found in
2019.3.0a6
2019.3.0a11
Issue ID
1175217
Regression
Yes
[Graphics] Shader errors are thrown when using DrawMeshInstancedIndirect()
How to reproduce:
1. Open the "SampleScene" in the attached "case_1175217-indirecterror" project
2. Press "Play"
Expected results: A cube Mesh is rendered without any issues
Actual results: A cube Mesh is being rendered, however, shader errors are thrown
Reproducible with: 2019.3.0a6, 2019.3.0a12
Not reproducible with: 2017.4.31f1, 2018.4.6f1, 2019.1.14f1, 2019.2.1f1, 2019.3.0a5
Adding these lines:
#pragma multi_compile_instancing
#pragma instancing_options procedural:setup
void setup() {}
to a shader "pass" block will fix this issue.
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