Search Issue Tracker
Fixed
Fixed in 6000.2.0a9
Votes
0
Found in
6000.2.0a1
Issue ID
UUM-97986
Regression
No
[Documentation] Graphics.RenderMeshIndirect arguments naming is misleading
Steps to reproduce:
- Read https://docs.unity3d.com/6000.0/Documentation/ScriptReference/Graphics.RenderMeshIndirect.html
- Notice that 3rd argument is called "commandBuffer", and same wording is used in the whole explanation.
Actual results:
Devs get confused with the Unity CommandBuffer type.
3rd argument is not a CommandBuffer but just a regular GraphicsBuffer.
Expected results:
3rd arguments is renamed something less confusing such as "indirectDrawArgsBuffer"
Reproducible with versions:
Not reproducible with versions:
Can’t test with versions:
Tested on (OS):
Notes:
- The same problem exists in our internal source code.
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
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
- Group Node name text is way smaller in the renaming state than the actual display size
Resolution Note (fix version 6000.2.0a9):
The Graphics.RenderMeshIndirect GraphicsBuffer typed argument "commandBuffer" has been renamed to "argsBuffer" to reduce confusion about the type.