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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment