Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.3.X, 6000.4.X, 6000.5.X, 6000.6.X
Votes
3
Found in
6000.0.67f1
6000.3.8f1
6000.4.0b8
6000.5.0a7
6000.6.0a1
Issue ID
UUM-134993
Regression
Yes
Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
How to reproduce:
1. Create and open a new Universal 3d project using Vulkan
2. Navigate to Window → Package Manager
3. Find the “Universal RP“ package
4. Open the “Samples” tab
5. Import the “URP Package Samples“
6. In the Project tab, search for the “DepthBlit“ scene and open it
7. Observe the Console tab
Actual result: Error messages are spammed in the console
Expected result: No errors are present
Reproducible with: 6000.0.22f1, 6000.0.68f1, 6000.3.9f1, 6000.4.0b9, 6000.5.0a7
Not reproducible with: 6000.0.21f1
Reproducible on: Windows 11, Ubuntu 22.04
Notes:
- The issue does not occur on other graphics APIs
- The issue does not occur when the “Main Camera” GameObject’s “Camera“ component’s “MSSA” setting (located under “Output“) is switched from “Use settings from Render Pipeline Asset“ to “Off“
- Full error message:
”A non-multisampled texture being bound to a multisampled sampler. Disabling in order to avoid undefined behavior. Please enable the bindMS flag on the texture.
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)”
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment