DebugDisplay.DrawComponent

Unity Engine
, ,
1

This gameobject keeps getting created in my editor scene (not the game scene).

I think it’s created by some sort of async task that is not stopped, It seems to get created just before PlayMode is entered, but since I’m really struggling with physics baking processes, maybe this is created by something I inadvertently do?

9201537--1283451--upload_2023-8-8_9-17-42.png

2 Likes
2

This is an internal component that’s needed by the Physics Debug Display to trigger the debug draw at the right moment.
You can safely ignore it.
It’s not caused by anything you do, other than the fact that you added a Physics Debug Display to your scene.

3

At least for me, two things I noticed about it that were confusing and made it unclear if this was working or not:

  1. The Script property is empty and makes it look broken. Double clicking the empty script also goes to an empty inspector:

9237108--1290603--upload_2023-8-21_10-14-18.png
9237108--1290606--upload_2023-8-21_10-14-25.png

  1. The docs link goes to a 404:

9237108--1290609--upload_2023-8-21_10-14-54.png
9237108--1290609--upload_2023-8-21_10-14-54.png1580×696 67.6 KB

2 Likes
4

Yeah put some hideflags on that thing already

5

I was just looking into this.

Fun fact: hiding the game object with the draw component in the hierarchy also doesn’t call its OnDrawGizmos() function anymore, which then deactivates the debug display hehe
The workaround I found is to hide its parent in the hierarchy, which works like a charm. The debug display shows up without this internal game object appearing in the hierarchy anymore.

1 Like
6

Note that this will be fixed in the next release of 1.1.