easy5 pts · first answer countsunity

Object still there after Destroy

After calling Destroy(gameObject) in Unity, code on the next line still reads the object's position without error. Why?

A.Destroy only hides the objectB.Destroy does nothing in buildsC.Destroy is delayed until after the current frame's Update loop, so the object exists until thenD.Destroy runs on a background thread

← Per-frame code in Unreal Health ratio is always zero →