Search Issue Tracker
Fixed in 2021.3.30f1
Fixed in 2023.2.0a20
Votes
0
Found in
2022.2.21f1
2023.1.0b18
2023.2.0a16
Issue ID
UUM-37018
Regression
No
Graphics.DrawProcedural doesn't work like in DX11 when used with DX12
Reproduction steps:
1. Open the attached “ProceduralBugDX12.zip” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Observe the Game View
Expected result: 2 spheres are visible in the Game View
Actual result: Only 1 sphere is visible (on the right)
Reproducible with: 2022.2.21f1, 2023.1.0b18, 2023.2.0a16
Couldn’t test with: 2020.3.48f1, 2021.3.26f1 (Errors in user’s script)
Reproducible on: Windows 10 Pro (22H2)
Note: This issue is reproducible only with DX12
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
- 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
Resolution Note (fix version 2021.3.30f1):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-32295
Resolution Note (fix version 2023.2.0a20):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-32295