Hey folks,
I’ve got a somewhat large scene (~1000s of Mesh
es/InstancedMesh
es) and I’m trying to keep them somewhat organized in the inspector. I’m currently creating TransformNode
s with no transform to use as parents for some of the elements which works reasonably well.
Now that I’m taking a look at the application’s performance, I see the TransformNode
constructor showing up on the flame graph with the Node
superclass constructor being much less (~20-30%) of that. Changing over to Node
instead of TransformNode
for our groups seems to work well and save some cycles, but doing so removes the whole group from the inspector. Is there some reason why Node
s aren’t shown in the inspector, or perhaps some other very lightweight grouping mechanism I can use?
Thanks!