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. Join us on Thursday, June 8, for a Q&A with Unity's Content Pipeline group here on the forum, and on the Unity Discord, and discuss topics around Content Build, Import Workflows, Asset Database, and Addressables!
    Dismiss Notice

Bug Fader Errors and Melee Body

Discussion in 'Editor & General Support' started by Kaivian, May 17, 2021.

Thread Status:
Not open for further replies.
  1. Kaivian


    Jan 18, 2018
    1. UIS & UCC
    2. 2020.3.4f1
    3. Strange Behavior with improperly configured equipment. Probably also happens in base UCC
    A) Go to the demo integration scene. Break any of the Object IDs attached to the character for colliders for the "Melee Body" weapon. Try equipping any other weapon. Get strange results (varies every time you try!)
    B) Make a new scene with both character perspectives, but don't include any First Person Objects. Get related fader errors

    Expected behavior: Some kind of error prevention built into object fader for NREs. Also, more specific error reporting (like what object is being faded)? Main concern here is if something fails to properly load in the future, don't want to cause a complete game crash or character bugged out.
    Last edited: May 17, 2021
  2. Kurt-Dekker


    Mar 16, 2013
    I'm not sure why you think breaking linkages would not cause nullrefs. How is this surprising? To me it looks like a good old bog standard nullref.

    Did you debug why that error is happening there?? It might not be THE linkage you "broke" but it certainly could have stemmed from it, and that's certainly where I'd look first!!

    The answer is always the same... ALWAYS. It is the single most common error ever.

    Don't waste your life spinning around and round on this error. Instead, learn how to fix it fast... it's EASY!!

    Some notes on how to fix a NullReferenceException error in Unity3D
    - also known as: Unassigned Reference Exception
    - also known as: Missing Reference Exception
    - also known as: Object reference not set to an instance of an object

    The basic steps outlined above are:
    - Identify what is null
    - Identify why it is null
    - Fix that.

    Expect to see this error a LOT. It's easily the most common thing to do when working. Learn how to fix it rapidly. It's easy. See the above link for more tips.

    This is the kind of mindset and thinking process you need to bring to this problem:

    Step by step, break it down, find the problem.

    Here is a clean analogy of the actual underlying problem of a null reference exception:
    bobisgod234 likes this.
Thread Status:
Not open for further replies.