Search Issue Tracker
By Design
Votes
0
Found in [Package]
14.0.0
Issue ID
1390210
Regression
No
Graphics.DrawMeshInstancedIndirect API doesn't draw Meshes when the SRP isn't BiRP
How to reproduce:
1. Open the user's attached "URPGPUInstancingTest" project
2. Enter the Play Mode in the "SampleScene 1" Scene
Expected result: Meshes are generated in the Game view without any errors
Actual result: Only one pink Mesh is generated or nothing. In some versions "ArgumentNullException: Value cannot be null." error is additionally thrown. Only one Mesh is generated when generating Meshes with the current SRP-compatible Shader
Reproducible with: 7.7.1 (2019.4.36f1), 10.8.1 (2020.3.31f1), 12.1.5 (2021.2.14f1), 13.1.7 (2022.1.0b7), 14.0.0 (2022.2.0a7)
Notes:
- Reproducible with HD RP
- Not reproducible with BiRP
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
The example in the builtin Unity manual is only designed for use with the Builtin renderer. To make this work in URP you will have to make tweaks to the shader code example. For more information about making a URP compatible shader please see the documentation here: https://docs.unity3d.com/Packages/com.unity.render-pipelines.universal@latest