Search Issue Tracker
Fixed
Fixed in 2021.3.36f1, 2022.3.21f1, 2023.2.13f1, 2023.3.0b9
Votes
4
Found in
2021.3.35f1
2022.3.19f1
2023.2.9f1
2023.3.0b6
Issue ID
UUM-63246
Regression
Yes
"Draw indirect argument buffer too small" is thrown when using an argument buffer of 4 ints
How to reproduce:
1. Open the “2022.3.18f1_DrawProceduralIndirect“ project
2. Open the “SampleScene“
3. Enter Play mode
4. Observe the Console
Expected result: No errors are seen in the Console
Actual result: An error is seen in the Console
Reproducible with: 2021.3.35f1, 2022.3.18f1, 2022.3.19f1, 2023.2.9f1, 2023.3.0b6
Not reproducible with: 2022.3.17f1
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
Error message: Draw indirect argument buffer too small. Must be at least 20 bytes (5 ints).
Comments (1)
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
- ComputeBuffer readback fails when Render Graph is enabled
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
bfoddy
Feb 08, 2024 12:48
It doesn’t just cause an error, it prevents the draw from happening.