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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- Scene dependency changes do not trigger a scene re-hash during Content Archives build
Add comment