Search Issue Tracker
Fixed
Fixed in 6000.6.0a4
Fix In Review for 6000.5.2f1
Votes
1
Found in
6000.0.65f1
6000.3.3f1
6000.4.0b3
6000.5.0a4
6000.6.0a1
Issue ID
UUM-132672
Regression
No
Procedural rendering is disabled when using Graphics.RenderPrimitivesIndexedIndirect()
Reproduction steps:
1. Open the attached project “ReproProject”
2. Open the scene “SampleScene“
3. Enter Play Mode
4. In the Hierarchy window, select “ProceduralRender” GameObject
5. In the opened Inspector Window on the right, in the component “Procedural Render MB“ change the “RenderMode“ from “RenderMeshIndirect” to “RenderPrimitivesIndexedIndirect”
6. Observe the results in the Game View
Actual result: Only one cube is visible, procedural rendering is disabled
Expected result: Multiple cubes are visible, procedural rendering is enabled
Reproducible in: 2023.1.0a1, 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Workaround: RenderPrimitivesIndexedIndirect can be forced it to work by manually calling material.EnableKeyword("PROCEDURAL_INSTANCING_ON"); before rendering with RenderPrimitivesIndexedIndirect()
Notes:
- Also reproducible in Standalone Player for Windows
- Reproducible with DirectX11 and DirectX12 Graphic APIs
- Script “ProceduralRenderMB“ that is used, is located at Assets → ProceduralRenderBug → Scripts
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
- Typo on "Chromatic Abberation" and "chromaticAbberationIntensity" when instead it should be aberration
- UI Document (UXML) UI disappears from the Game view when any asset is imported and does not reappear until clicking in the Editor
- Warnings about invalid URIs are thrown when UI Builder's Material field is set to null
- Warnings about invalid URIs are thrown when UI Builder's Variable Asset Reference field is set to null
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
Resolution Note:
Fixed in 6000.6.0a4
Resolution Note (fix version 6000.6.0a4):
Fixed in 6000.6.0a4
Resolution Note (fix version 6000.5.2f1):
Fixed in 6000.5.2f1