Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.3f1
6000.4.0b3
6000.5.0a4
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment