Search Unity

  1. Calling all beginners! Join the FPS Beginners Mods Challenge until December 13.
    Dismiss Notice
  2. It's Cyber Week at the Asset Store!
    Dismiss Notice

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

Discussion in 'Editor & General Support' started by JJJAGUAR, Dec 25, 2017.

  1. JJJAGUAR

    JJJAGUAR

    Joined:
    Feb 16, 2015
    Posts:
    3
    Sometimes I get the attached errors for no reason.
    I'm still able to compile and run the game and everything works fine. Sometimes the errors even disappear, but come back randomly. Any ideas what is this?
     

    Attached Files:

  2. drcrck

    drcrck

    Joined:
    May 23, 2017
    Posts:
    281
    This thing is not fixed and still happens
     
  3. Immu

    Immu

    Joined:
    Jun 18, 2013
    Posts:
    154
    Same problem here. using Unity 2018.1.6f1 (with LWRP)
     
  4. malkere

    malkere

    Joined:
    Dec 6, 2013
    Posts:
    1,093
    My Frost Nova spell was working fine, 2017.1.0f3. Crashed. Throws this error every time now.
     
  5. Cinabutts0

    Cinabutts0

    Joined:
    Jul 11, 2018
    Posts:
    2
    Damn, i was hoping for an answer lol I'm using Unity 2018.1.6f1. I tried this lowpolywater asset and it's giving me this error and not making the water shader work.

    Shader properties can't be added to this global property sheet. Trying to add _RefractionTex (type 3 count 1)
    UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
     
  6. malkere

    malkere

    Joined:
    Dec 6, 2013
    Posts:
    1,093
    It seems to come and go without warning or reason. A restart or two seems to put it at rest.
     
  7. purnamasari

    purnamasari

    Joined:
    Mar 8, 2018
    Posts:
    17
    Damn, this things ruin my project. All I had to do is remove this experimental package and change the shader to standard again. Seriously, backup your project before trying this new things.
     
  8. drcrck

    drcrck

    Joined:
    May 23, 2017
    Posts:
    281
    Just deleted 20 GB of editor logs full of this error :mad:
     
  9. stream_in_space_

    stream_in_space_

    Joined:
    Dec 22, 2015
    Posts:
    3
    Switching between a scenes helped to me, unlike to rebooting the project and the pc... magic error.
     
  10. drcrck

    drcrck

    Joined:
    May 23, 2017
    Posts:
    281
    Any ways to understand what object causes it, at least?
    I get 999+ messages every time I switch to Scene tab

    PS Disable editor logs by adding -logFile NUL to unity shortcut or they'll take all available space on your system disk
     
  11. alanmthomas

    alanmthomas

    Joined:
    Sep 7, 2015
    Posts:
    171
    I just ran into this for the first time after installing the LWRP package. Oddly, it didn't occur until a day into using the LWRP. I've managed to resolve it. It was a matter of finding the offensive shader and deleting it.
     
  12. Bas-Smit

    Bas-Smit

    Joined:
    Dec 23, 2012
    Posts:
    113
  13. jeffweber

    jeffweber

    Joined:
    Dec 17, 2009
    Posts:
    564
    For what it's worth, I'm getting this currently in 2019.3.6 beta... seems tied to the Universal Rendering Pipline??
    Screen Shot 2019-10-04 at 2.35.28 PM.png