Can not find element tree view (explorer view)

I am new to Rhino, mainly using it for converting/stripping 3D files I get from customers.

Thus far I have been unable to find what I consider as a very basic feature, which is to have a hierarchical tree of all the elements in the design.
For instance importing a large step file, which has a structure, I have no way to see this structure, and to directly jump to one element or sub-element. Till now I have to explode the model bit by bit in order to reach down to the element I need.
This makes it really annoying to handle complex assemblies.

Is there a way to have such a tree view ?


Just as a work-around, if you use the ExplodeBlock command, you won’t need to explode step by step and will be able to reach any ‘inner-most’ object right away.

trouble is of course than then I find myself with a “flat” model with possible thousands of elements, which I don’t want because it is then unworkable.
For instance, I want to delete/hide/show a group of elements, which is a few level down, I don’t want to explode any further that that.
And Ideally I actually don’t want to explode at all, to still be able to act globally after that.

So do you confirm that there is no good way of handling hiearchy of a model in Rhino ?

Well, … partly.
I agree that it would be good to have an option to put parts in a STEP assembly on their own layers (not-blocked) according to the hierarchy in the assembly.

I am not clear at what exactly you want to do with these but I think that you will find that you need to get rid of the blocks anyway - if you need to get in and do something with a certain component.

What do you mean by that?

I routinely work with these flat models with thousands of objects and don’t have any problems with that. You just have to organize things yourself and from the sound of it, you just need to select the things you don’t need and put these on an OFF-layer.

Take a look at the StepTree command. Maybe that will help.


Hi Timothé,

there is a python script from Pascal which “converts” the block hierarchy to Rhino’s layer structure.


That sounds interesting, I’ll have a look at it.