Search Issue Tracker
By Design
Votes
0
Found in
2017.1.1f1
Issue ID
958762
Regression
No
Calling "CommandBuffer.EndSample" after "ScriptableRenderContext.Submit" messes up the Frame Debugger hierarchy
Reproduction steps:
1. Open "CommandBuffer.EndSample after Submit bug.zip" project*
2. "Window" -> "Frame Debugger" -> "Enable"
3. Select "MoonRenderPipelineAsset.asset" scriptable object in the Project window
4. In the Inspector window, check "Submit Postprocessors Before End Sample" checkbox
Expected Result: "CommandBuffer.BeginSample" groups the Frame Debugger hierarchy
Actual Result: Calling "CommandBuffer.EndSample" after "ScriptableRenderContext.Submit" messes up the Frame Debugger hierarchy
Reproduced with: 2018.1.0b1, 2017.3.0p1, 2017.2.1p1, 2017.1.3f1
Did not reproduce on: 5.6.5f1(Experimental Rendering functions only implemented as of 2017.1)
Note:
Check Edit*
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on memcpy when using ScreenCapture.CaptureScreenshot with superSize set to zero
- [URP] Package Samples - Missing scripts in Unity 2022+
- [URP][Package Samples] Continuous "Renderer at index _ is missing for camera _" warnings when opening sample scene
- [URP] Package Samples - Missing scripts in Unity 6
- [URP] Package samples - scenes using FirstPersonController not working in Unity 6
Add comment