Search Issue Tracker
Fixed
Fixed in 2022.2.0b12, 2023.1.0a14
Votes
1
Found in
2021.3.26f1
2022.2.0b1
2023.1.0a1
Issue ID
UUM-4100
Regression
No
[FrameDebugger][URP] Grey image displayed when MSAA is enabled
When using FrameDebugger with URP and MSAA the camera buffer displays a grey image and the following warning is displayed on console:
Metal: Shader\[Hidden/FrameDebuggerRenderTargetDisplay]: Incompatible texture type \[MTLTextureType2DMultisample] of texture \[_CameraDepthAttachment_825x461_Depth_MSAA4x MSAA] bound at index 0, expected \[MTLTextureType2D]
How to reproduce:
-Create a new URP project from 3D blank template
-enable FrameDebugger
-Click on Camera.RenderSkybox event.
- Notice how FrameDebuffer displays grey image
Expected: FrameDebugger should display correct color image with skybox contents
Disabling MSAA fixes the issue.
Comments (2)
-
alexmalyutindev
Apr 03, 2023 09:29
Hello! Will this fix backported to Unity 2021.3 LTS?
-
alexmalyutindev
Dec 12, 2022 11:27
Same for Unity 2021.3.15f
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
- 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
Resolution Note (fix version 2023.1.0a14):
The issue was with the shader used with the Frame Debugger. It has now been updated to support events using MSAA.
Resolution Note (fix version 2022.2.0b12):
The issue was with the shader used with the Frame Debugger. It has now been updated to support events using MSAA.