Search Issue Tracker
Active
Votes
25
Found in
Issue ID
1281021
Regression
No
[Windows] Not possible to deduce the source of 'Shader properties can't be added to this global property sheet.' error
1) Clone https://github.cds.internal.unity3d.com/unity/stw-20-2-cannon-fodder-3-style-game. Update to https://github.cds.internal.unity3d.com/unity/stw-20-2-cannon-fodder-3-style-game/tree/bugs/1281021
2) Open the project with the Windows Editor from https://saihai.hq.unity3d.com/build/1275 or build using rev e2067236bd5c (2020.2/staging).
Observe the endless spam of errors
Shader properties can't be added to this global property sheet. Trying to add _GrabTexture (type 3 count 1)
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)
The user can't click the error and get taken to the offending shader, it will just open up the
Expected behavior: the user is taken to the shader / script where the offending property is set.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Qilbby
Jun 19, 2022 16:48
@Radivarig, Thanks, this worked for me. I was deactivating one by one until I found the problem. It was in the shader of a portal that was not adapted for URP.
Radivarig
Dec 14, 2021 12:18
You can deduce the source like this:
- have the scene/game tab open and ensure that the error keeps being thrown when clicking in anywhere in the hierarchy
- don't rotate/move the camera or the object with the shader will be out of viewport and not render
- disable all gameobjects
- optionally clear the console
- start enabling gameobjects, when the error appears it will be on the last enabled gameobject which is the parent of where the shader is attached.