Search Issue Tracker
Fixed in 12.0.0
Votes
0
Found in [Package]
12.0.0
Issue ID
1352005
Regression
Yes
"A non-multisampled texture..." spams the Console
There's an auto resolve happening and then an incorrect Copy Depth pass.
1. After upgrading from 2021.2.0b1 to either 0b2 or 0b3 or 0b4
2. I get this Error in the Console
"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."
Caused by the Depth Priming PR, a fix was already in the works:
https://github.com/Unity-Technologies/Graphics/pull/5039
Duplicate bug with test project that does reproduce the issue: https://fogbugz.unity3d.com/f/cases/1357776/
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
- 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
Resolution Note (fix version 12.0.0):
Fixed in 2022.1.0a6