Error: "Shader properties can't be added to this global property sheet."

This worked for me. I reset the layout editor to a default layout and stop the error. Maybe is abug in editor layout, very funny.

 

I was having this error as a part of AOE Magic Spells pack (https://assetstore.unity.com/packages/vfx/particles/spells/aoe-magic-spells-vol-1-133012). I am running 2D and URP. But they have added a Support Package for it's shader conversion and that converted the pipeline of it's shader to URP and it resolved the error (https://assetstore.unity.com/packages/tools/utilities/support-package-for-hovl-studio-assets-157764)
Hope this helps...

 

In my case the error was spamming when a certain material was in fustrum. Hunting down the exact object allowed me to find a non-compatible shader on a material.

I wish It helps.

 

Migrated to 2020.3.30f1. This arose as I am going through the process to launch ShaderGraph.
I executed the quote instructs. Clear the console, less or same appear, clear the console, less appear, clear the console, all gone.

But in time it reappears. Will have to do what @bytewav suggested since my path is dealing with shaders.

So the question is 'How does one find the offending shaders. Are they pink?'

 

A new post to add the interogation process.
I disabled all the GOs and the errors stopped.
I clicked on a disabled GO and the error starts back up.
Click on camera and errors stop.

I then go into the asset material folder of the offending asset.
I sequentially click on materials to start the errors again.

 

I fixed this error by removing the following (unused) line from a shader:

GrabPass { }

 

I think my faulty shader had a grabpass too. Started creating problems after a migration from legacy to hdrp.

 

I have the answer: I noticed in the scene editor view as I rotated round to look at one of the objects in my scene view it would start complaining, so I switched off all the objects and eventually I found it was the water shader in my case that I needed to use another rendererrer for, so do this: switch off all the objects clear the errors and they should stay cleared, enable the objects chunk by chunk until the errors start up again, identify the component causing you issues, and fix it (can't shed any real light on that other than picking a different shader until it stops complaining), job done and good luck!

 

Thanks that worked for me! Much appreciated.

 

same here with the same package

 

If you downloaded the "Realistic FX Package V4" it's the "Distort" material that is causing the error. I deleted it and it's fine.

 

The HDRP is totally different, so cant port shaders directly between, as there is no grab pass and many other things are working differently

Only the very base stuff can be ported or vertex fragment shaders that not use any special passes or unity side directives

 

I also got this error in unity 2021.3.9f1. I installed a couple of packages but I supsect the Nature Manufacturer Forest Tree package. It did break the Foilage Shader of the same supplier as well as a water shader. After I reinstalled from a previous prefab export, things went back to normal.

 

Thankyou, my error went away when I double clicked on the URP folder and clicked on import.

 

I removed KriptoFX Realistic Effects and found a problem in their Mesh Effects shader as well. This fixed it. Props to everyone who pointed me to KriptoFX and also the tip about panning your camera around until you tripped the error. Took me 10 minutes to solve once I had these tips, you legends probably saved me hours.