You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 2018 and later (potentially 2017 as well, haven't tested) Unity has problems cleaning up the RuntimeDebugDraw object nested inside the hidden wrapper object when exiting play mode. For some reason it complains about something trying to delete its Transform component:
There is no call stack, so this is originating in Unity's own internal code.
The text was updated successfully, but these errors were encountered:
JohannesMP
added a commit
to JohannesMP/unity3d-runtime-debug-draw
that referenced
this issue
Jan 17, 2020
(See issue jagt#10) In 2018 Unity has problems cleaning up the `RuntimeDebugDraw` object nested inside the hidden wrapper object when exiting play mode. For some reason it complains about something trying to delete its Transform component: https://i.imgur.com/aZ6oEmF.png - there is no call stack, so this is originating in Unity's own internal code.
By un-parenting the object right before the play mode scene is cleaned up this error appears to not occur and the object is cleaned up as expected without Unity's backend for some reason trying to delete its Transform component.
This issue appears to be resolved with changes in my pull request.
Since the RuntimeDebugDraw object only is destroyed like this when exiting play mode, it can be mitigated by unparenting it right as play mode exits, but before it is cleaned up. The object is still cleaned up correctly, just without an annoying error.
In 2018 and later (potentially 2017 as well, haven't tested) Unity has problems cleaning up the
RuntimeDebugDraw
object nested inside the hidden wrapper object when exiting play mode. For some reason it complains about something trying to delete its Transform component:There is no call stack, so this is originating in Unity's own internal code.
The text was updated successfully, but these errors were encountered: