Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.6.0a3
Issue ID
853212
Regression
Yes
[FrameDebugger][GL] Frame Debugger doesn't render mixed draw calls/assertions appear, when shadows are enabled
Steps to repro:
1. Open attached project and 'test' scene on OSX;
2. Open Frame Debugger (Window -> Frame Debugger) and click 'Enable';
3. Select 'Draw Mesh' in Camera.Render - Drawing - Camera.RenderSkybox section of FrameDebugger window;
4. Notice that assertion:
'Assertion failed on expression: 'srcAttach < m_CurrentFramebuffer.colorCount && "We should always resolve only current RT"' '
is getting spammed in the console window.
5. Try to switch frame Debugger frames either by moving frame slider or by clicking arrow buttons inside of it.
Actual result:
Frame Debugger doesn't render overlaying draw calls (see attached gif video).
Regression introduced in Unity 5.6.
Expected result:
- Frame debugger should always switch frames and show overlaying draw calls;
- Assertions should not be thrown when operating Frame Debugger.
Notes:
- Reproducible in 5.6.0a3;
- Not reproducible in 5.5.0f2, 5.4.3f1;
- Reproducible only on OSX 10.12.1;
- Not reproducible on Windows 10;
- Reproducible only in Forward with Shadows turned off;
- Enabling shadows on Directional fixes the issue.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Add comment