Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2021.3.11f1
2022.2.0a7
Issue ID
UUM-17390
Regression
No
Rendering calls do not clean the previous state in the Frame Debugger (SRP Batch) when rerendering
Steps to reproduce:
1. Open the user’s project
2. Open the “Frame Debug” window (Window → Analysis → Frame Debugger)
3. Click the “Enable” button
4. Expand ScriptableRender.Execute → DrawOpaqueObjects → RenderLoop.DrawSRPBatcher
5. Select SRP Batches and observe the Game view
6. Alt-Tab (or command+tab) to rerender
Expected result: The previous state was cleaned
Actual result: The previous event was not cleaned
Reproducible with: 2021.3.11f1, 2022.2.0a7
Not reproducible with: 2022.2.0a8, 2022.2.0b10, 2023.1.0a13
Could not test with: 2020.3.40f1 (Package errors), 2022.1.18f1 (SRP Batches are blank)
Reproduced on: macOS Monterey 12.5.1 (Intel)
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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note:
This issue not reproducible on latest 2023.1 or 2022.2. To avoid unnecessary risks to LTS versions we will not backport the fix to 2021.3.
Resolution Note (2022.2.X):
This issue not reproducible on latest 2023.1 or 2022.2. To avoid unnecessary risks to LTS versions we will not backport the fix to 2021.3.