Search Issue Tracker
Active
Under Consideration for 6000.2.X
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.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Inspector elements are rendered twice when the script component is added via drag-and-drop while the HideFlags.HideInInspector property is set
- Error "Light baking failed with error code 5 (Convergence data not available while rendering lightmaps)" thrown in Console when generating lighting for specific GameObjects
- Copy and Paste options for an Animation Property value are disabled in the Right click contextual menu
- Asset is not found when searching the Label "NewLabel" in Search Window
- "Compute dispatch: missing texture ID..." and "Compute dispatch: missing UAV ID..." warnings are thrown after changing the platform in High Definition 3D template
Add comment