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. Dismiss Notice

m_InstanceID != 0 -- what is this error (caused by particle system?)

Discussion in 'Editor & General Support' started by guru20, Jul 10, 2015.

  1. guru20

    guru20

    Joined:
    Jul 30, 2013
    Posts:
    239
    I've searched the forums and answers, and Google, and find a lot of (generally older) references to an m_InstanceId == 0 error... but I'm getting the opposite that. At runtime, console warns m_InstanceID != 0 ...

    It appears to be tied to a particle pre-fab (cloud) I have added to the scene. When I take that away, it doesn't exist.

    Before I updated from 5.1.1p1 to 5.1.1p3, it wouldn't give an error -- it would just crash Unity at runtime. Now it gives this error.

    Only happens in one of my two scenes -- the other scene has the same particle cloud, and works fine, no problems...
     
  2. bfloch

    bfloch

    Joined:
    Jan 4, 2013
    Posts:
    24
    Have the same issue without a particle scene in 5.1.2

    EDIT: More info.
    I read this might be related to prefabs. Now I deleted the RigidBodyFPSController and instead of two I get a loop of this messages.

    Now if I have no camera I get the error twice.

    If I add a plain camera then no error at all.

    So if you ask me the RigidBodyFPSController is broken. This is a VR project btw.
     
  3. Rave-TZ

    Rave-TZ

    Joined:
    Jul 21, 2013
    Posts:
    72
    This is happening to me as well. Also in a VR project.

    Not sure its related but my game crashes at the same time this error shows up. Only shows up in editor and doesn't land in an output log. This happens when I leave one scene in to another.