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.
-
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
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.