Resolved "A non-multisampled texture..." spams the Console

I don't know if it's a bug, but I don't know what to do with it.
After updating from 0b1 to either 0b2 or 0b3 or 0b4 I get this Error in the Console:

I guess it's related to URP which we're using, but I'm not sure.
Everything is OK in 2021.2.0b1.
The moment I add Camera to new Scene it starts spamming.
I also tried deleting Library folder.

P.S.: I tried creating new project in 0b4 to test if it shows up there too, but couldn't:

 

I was using Hub v3 Beta. Downgrading to v2 solved template issue.
I reproduced the problem and reported the bug by using manifest.json from actual project and URP asset settings from it.
Looks like it's related to Quality Anti Aliasing (MSAA) setting - the error appears when it's enabled.

 

Just to let you know I've had this bug as well, I spoke to someone from support about it briefly. The exact same things happens to me b3 and b4 both suffer from it. URP. Turning off all AA fixes it.

 

It's 1352005

 

Hi @LeonhardP. We just hit that same bug with 2021.2.0b6 and I was wondering if it has been confirmed as a bug by your team? Can we already track it in issuetracker.unity3d.com?

 

@LeonhardP We were able to get rid of the error by changing Depth Priming Mode to Forced. If I understand it correctly, it is not a problem if our shaders use depth data anyway - am I right? Does that option incur any performance overhead?

This is on Unity 2021.2.0b6.

 

@NicoLeyman Thank you for investigating this. So the problem probably lies with one of our shaders or materials. We will try to make a minimal repro and submit a bug.

In the meantime we did some benchmarking on 2021.2.0b6 vs 2021.1.11f1 and discovered that forced Depth Priming adds approx. 0.5 ms to frame rendering time in our project. Full results are here:
https://forum.unity.com/threads/degraded-performance-in-unity-2021-2-0b6-standalone.1155311/

 

@NicoLeyman So we're still trying to isolate a repro but in the meantime I noticed that on macOS I get one more warning every frame, in addition to the original error.

Perhaps that warning holds a clue as to what is causing the error? It specifically points at the Universal Render Pipeline/CopyDepth shader.

 

@NicoLeyman I was able to create a minimal repro project with only a Camera and a Cube. I have submitted a bug report with the project, case #1357776.

 

Thank you!

 

That's great, thank you!

 

Confirming, can't reproduce this bug in b15

 

@NicoLeyman Excuse me, I added another camera to the scene,The same error was reported,My version is 2021.3.3,What do I do,help me please

 

@NicoLeyman The same error was reported too when I use the virtual texture function,My version is 2021.3.1f1 on windows 10.
When I close the MSAA, the error is gone.
Could you check the problem in this environment?
Thanks

 

@NicoLeyman
The environment detail:
In a urp project, open Virtual Texture(VT) in project settings, and create a VT shader through ShaderGraph, then create a vt material and put the material on a gameobject of the scene, at last play the game.

 

This is marked as resolved several months ago, yet I'm seeing the error today.
MacM1, 2021.3.10f1
I installed UniStorm 5.2.0 ( did the URP file overwrite)

My console overflows like it is trying to capture a firehose *:
"Metal: Shader[Hidden/Universal Render Pipeline/CopyDepth]: Incompatible texture type [MTLTextureType2D] of texture [UnityDefault2D] bound at index 0, expected [MTLTextureType2DMultisample]"

I understand Metal is a reference to the graphic engine used by AppleM1 (I'm an Apple Developer as well.) I only have two years experience with Unity, but I get that the error reports a shader is receiving a texture from a material at position Index 0. That this texture is in an incorrect format. The error message is clear except it fails to report which material/ texture it is complaining about. I would appreciate any assistance in correcting this issue. Thanks.

* indicating that this is occurring multiple times per frame.

 

The error is occuring in 2021.3.3f1 when building to the Quest 2 -
OpenGLES3,
Empty scene with the OVRCameraRig,
URP with Depth Priming Mode set to Forced.

Setting Depth Priming Mode to Disabled, and the error does not occur.

This is not a workaround for us, because we need the depth texture for a renderer feature.

Alternatively, turn off MSAA in the URP Asset.

(It is not our feature causing the problem - the feature is removed in the above test).

 

This error is still not fixed. One thing that could be helpful for everyone is to include more information into the error message itself, for example, which shader and which texture is causing it.