Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

Question Error messeage after updating to Unity 2022

Discussion in 'Shader Graph' started by Settos, Jan 28, 2023.

  1. Settos

    Settos

    Joined:
    Aug 3, 2015
    Posts:
    14
    Hi, I've recently updated to Unity 2022 and since then I get the following error message:

    "NullReferenceException: Object reference not set to an instance of an object
    UnityEditor.ShaderGraph.Drawing.MaterialGraphEditWindow.OnDisable () (at ./Library/PackageCache/com.unity.shadergraph@14.0.4/Editor/Drawing/MaterialGraphEditWindow.cs:417)"

    The thing is that everything still works perfectly fine, but this error message keeps popping up all the time.
    It may seem to work fine, but do I have to worry that this might be able to crash an app?
    Does anybody now what I need to do?
     
  2. WimeSTone

    WimeSTone

    Joined:
    Jul 29, 2016
    Posts:
    3
    What version are you on? I have the same error occurring on 2022.2.5f1, but not on 2022.2.1f1.
    I've rolled back to 2022.2.1f1 for now, however upon doing so I had to reinstall the Universal RP package in safe mode.
    2022.2.5f1 apparently changed URP version for me.
     
  3. Settos

    Settos

    Joined:
    Aug 3, 2015
    Posts:
    14
    Thanks for the reply. I'm using 2022.2.2f1. My initial thought was to remove shadergraph, then install it again. but unity won't allow that anymore. I'll try what you did later.
     
  4. iLollipop

    iLollipop

    Joined:
    Jan 19, 2023
    Posts:
    3
    same error in unity 2022.2.2 I cant find a way to fix it. I delete the universal RP and the error still appeared .then download URP the error still appears .Did you fix it ? if yes how?
     
  5. Trecker17

    Trecker17

    Joined:
    Jun 5, 2019
    Posts:
    1
    Upgrading from 2022.2.2f1 to 2022.2.9f1 fixed this problem for me.

    It might just be a very specific 2022 bug. The error didn't cause any issues as far as I could tell. Just cluttered up the console.