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
- Crash on mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
Add comment