Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.38f1
2021.3.8f1
2022.1.13f1
2022.2.0b4
2023.1.0a6
Issue ID
UUM-11934
Regression
No
DrawProceduralIndirect: baseVertexLocation and startInstanceLocation are broken when using DirectX11, DirectX12, OpenGL and Metal
Reproduction steps:
- Open the attached project
- Open the “/Assets/Scenes/SampleScene.unity” Scene
- Observe the Game View
- Change the Graphics API to “Direct3D12” in the Player Settings (Edit > Project Settings > Player > Other Settings > Graphics APIs for Windows)
- Observe the Game View
- Change the Graphics API to “Vulkan” in the Player Settings (Edit > Project Settings > Player > Other Settings > Graphics APIs for Windows)
- Observe the Game View
Expected result: The pallet and the gear are rendered correctly when using the “Direct3D12 (Experimental)” and “Direct3D11” Graphics APIs
Actual result: The pallet and the gear are clipping and rendered incorrectly when using the “Direct3D12 (Experimental)” and “Direct3D11” Graphics APIs
Reproducible with: 2020.3.38f1, 2021.3.8f1, 2022.1.13f1, 2022.2.0b4, 2023.1.0a6
Reproducible on: Windows 10 (21H2), M1 MacOS 12.4 (21F79)
Notes:
- This issue is also fully reproducible using the Metal Graphics API
- The objects are rendered correctly, but they are still clipping with each other using the OpenGL 4.5 and OpenGL ES 3.2 Graphics APIs
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
Currently, we are not easily able to support using the `baseVertexLocation` in the cross-platform manner described in the issue, given the limitations of the various graphics APIs. Marking the issue as *Won't Fix*, but also created a feature request to explore being able to support this in the future.