Search Issue Tracker
Fixed in 9.0.0-preview.55, 10.0.0-preview.26
Fixed in 7.5.1, 8.2.0
Votes
0
Found in [Package]
7.2.0
Issue ID
1270966
Regression
Yes
[URP] Frame Debugger renders a blank view or applies a red mask when MSAA is enabled
How to reproduce:
1. Open the attached project named "URP_FrameDebuger"
2. Select the used URP asset and check if MSAA is enabled
3. Enable Frame Debugger
4. Select Render Opaques -> RenderLoopNewBatcher.Draw
Expected result: The Frame Debugger renders the opaque meshes as in Scene view
Actual result: The Frame Debugger renders a blank screen or the view receives a red mask(Depending on the Graphics API used)
Reproducible with: 2019.3.7f1(7.2.0), 2019.4.11f1(7.4.3), 2020.1.0b16(8.1.0), 2020.2.0b3(9.0.0-preview.35)
Not reproducible with: 2019.3.7f1(7.1.8), 2019.4.11f1(7.5.1), 2020.1.0b16, 2020.1.6f1(8.2.0), 2020.2.0b3(9.0.0-preview.55, 10.0.0-preview.26)
Fixed in: 7.5.1, 8.2.0, 9.0.0-preview.55, 10.0.0-preview.26
Notes:
1. When tested with D3D11 and D3D12 the Frame Debugger would render the view with a red mask
2. When tested with Vulkan, OpenGLCore and Metal Frame Debugger would render a blank window
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
- Animator state transition preview clips are flickering when zooming in
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- "DebugAllocatorMode" option changes when changed in another Editor instance
Resolution Note (fix version 9.0.0-preview.55, 10.0.0-preview.26):
Fixed in URP - 9.0.0-preview.55, 10.0.0-preview.26 and above
Resolution Note (fix version 8.2.0):
Fixed in - URP 8.2.0
Resolution Note (fix version 7.5.1):
Fixed in - URP 7.5.1