-
Notifications
You must be signed in to change notification settings - Fork 4
GameObject destroy errors reported in editor on the UWP platform #97
Comments
Could you paste in the error stack trace please? |
No stack trace, the only error reported is:
Interestingly, it doesn't occur when the "Windows Mixed Reality spatial locatability state" is "Inhibited". |
Hmm, sounds like a race condition where the object is already cleaned up by the time we iterate over the collection to try and clean up manually. I'll check it out. |
When I stared the Holographic emulation everything seemed to work fine for me. @FejZa could you possibly troubleshoot this with your device connected to the editor? |
Will do |
One other interesting thing to note, when starting then stopping emulation then trying this again in the editor, I didn't get the errors again until after I restarted the editor. |
Here's the list of errors I'm getting atm:
So the things I don't understand. We're not trying to destroy any transforms in our implementation. We call Destroy on the GameObjects themselves. I'm wondering if these errors are coming from somewhere in Unity's internal implementation as the scene is cleaned up. |
Edited the errors with the internal callstacks |
XRTK - Mixed Reality Toolkit Bug Report
Describe the bug
There seems to be an issue with the Spatial Object management where it is cleared prematurely in the editor when the scene is closed.
To Reproduce
Expected behavior
No errors
Actual behavior
Your Setup
The text was updated successfully, but these errors were encountered: