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
- 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:
There are no fixes planned for this Bug