Search Issue Tracker
Fixed
Votes
0
Found in
2020.3.39f1
2021.3.10f1
2022.1.16f1
2022.2.0b8
2023.1.0a10
Issue ID
UUM-14881
Regression
Yes
Graphics.DrawMeshInstanced() will throw an error when the shader is compiling asynchronous
Reproduction steps:
# Open the user attached project
# Press the Play button
Expected result: No errors in the Console
Actual result: Error in the Console
Reproducible with: 2020.3.39f1, 2021.3.9f1, 2021.3.10f1, 2022.1.16f1, 2022.2.0b8, 2023.1.0a10
Not reproducible with: 2021.1.0a1, 2021.3.8f1
Reproduced on: macOS Monterey 12.4 beta
Not reproduced on: Windows 10
Note: To successfully reproduce the issue make sure to enable "Asynchronous shader compilation" in the project settings [https://docs.unity3d.com/Manual/AsynchronousShaderCompilation.html|https://docs.unity3d.com/Manual/AsynchronousShaderCompilation.html|smart-link] Also, it seems like the issue is not reproducible constantly, if the issue is not reproducible, try restarting the project
Error: DrawMeshInstanced does not support the shader 'Custom/Grass' because it does not read any instanced properties. Try switching to DrawMeshInstancedProcedural if the shader is doing procedural instancing.
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
- Certain textures are incorrectly marked in the render pass list when observed through Render Graph Viewer
- "Assertion failed on expression" error occurs when multiple Animation Components are instantiated after changing the Culling Type
- MacOS persistentDataPath uses old path when built compared to Editor Play mode
- Crash on RaiseException when entering Play Mode in a specific project
- Debug Console does not reappear when disabling and re-enabling Debug.developerConsoleEnabled
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-13174