Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.61f1
Issue ID
UUM-102823
Regression
No
BatchRenderGroup mesh bounds contain uninitialized values
How to reproduce:
1. Download and open the “brg-shooter” project
2. Open the “brg_shooter” scene
3. Load RenderDoc
4. Enter Play Mode
5. Take a RenderDoc capture
6. In RenderDoc, open the capture
7. Find an event named “DrawIndexedInstance” and select it
8. In Vertex Shader (VS) view, find a constant buffer that begins with name “D3D12PageAllocator::AllocateNewResourceInternal() Scratchbuffer”
9. Observe the top-most values in the Vertex window
Expected result The returned values match to the local bounds of mesh that's associated with the current ‘BatchDrawCommand’
Actual result: The returned values contain uninitialized data
Reproducible in: 2022.3.61f1
Not reproducible in: 6000.0.45f1, 6000.1.0b14, 6000.2.0a8 (This feature was added in 2023.1)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
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
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
- 2D light leaks through ShadowCaster2D when ShadowCaster2D components are disabled then re enabled at runtime in Player builds
- Unity Hub redirects to The Unity Roadmap when navigating to “Send Feedback” option
- UI Toolkit throws warning and fails to clear references when fields are not typed as UnityEngine.Object
Resolution Note:
There are no fixes planned for this Bug