Search Issue Tracker
Fixed
Fixed in 2022.3.16f1, 2023.2.4f1, 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
- Property field override bar does not update transparency correctly when switching between valid and invalid GameObjects
- Project window selection is not updated when search term is changed
- Error when adding valid MonoBehaviour script to Prefab in Project window
- Editor Launch Screen will close when Enter is pressed on it
- ObjectPool's pool is destroyed when entering Play Mode without reloading Domain
Add comment