Search Issue Tracker
Fixed in 2022.3.16f1
Fixed in 2022.3.X, 2023.2.X, 2023.3.X, 2023.3.0a16
Votes
0
Found in
2022.3.13f1
2023.1.20f1
2023.2.0b17
2023.3.0a13
Issue ID
UUM-54792
Regression
Yes
Frame Debugger: "A multisampled texture being bound to a non-multisampled sampler" errors when inspecting depth texture with MSAA
The Frame Debugger often logs out errors when looking at events using MSAA. This is the error that is logged out:
{code:java}
A multisampled texture being bound to a non-multisampled sampler. Disabling in order to avoid undefined behavior. Please use Texture2DMS in the shader.
{code}
I bisected the issue and it started happening when this PR landed:
https://github.cds.internal.unity3d.com/unity/unity/pull/24848
Repro steps:
- Open the attached "RenderGraphTest" project
- Enable the Frame Debugger
- Select the "Draw Opaque Objects" event
- Click the dropdown showing "RT 0" and select "Depth"
- Notice the errors appearing in the console and black game window and texture in the Frame Debugger.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment