Just looking through the forum to find a thread on this. Where can I add my +1 for an objects panel in Rhino. You would think it was one of the first things to do, yet here we are with Rhino 7 and still no way to see an actual list of objects I have in my scene or see what is contained in a Layer.
Can someone from McNeel explain why it wasn’t deemed necessary when there is not a single 3D programm out there that I have seen that does NOT have one? I mean even Sketchup had this before they were ever bought by Google in the early 2000s.
I just don’t understand what is so hard about that? All the information is there. There are Panels for so many obscure things… a web browsers, tutorials, etc. There is a separate panel for Lights and many others that could all be reduced down to a simple Objects/Layers Panel. You have your layers and in the layers you have your objects. They can be anything, meshes, NURBS objects, lights, etc.
It would solve so many issues. If you want to lock or hide specific things you select them and then hide them. But then how do you know what you have hidden? You have to unhide everything and then select and hide things again. Why? Why can’t I just see all the objects in a panel and it has a little icon for hiding/showing and one for locking… like in so many other 3D softwares. Its not like it will get in the way of anyone, even if it is part of the layer panel. If you just want to see the layers, you just keep them collapsed, but if you want to see and interact with the objects you click to open the layer and you see the objects. I mean right now you can’t even tell if a layer contains any objects or how many. Or how about accessing an object in a group? So easy if you have an outliner and can see object hierarchies.
I think this screenshot from an article how to transfer stuff over to Unreal Engine shows a nice side by side comparison of the panels. Notice how Rhino just stops at the layer level and Unreal just goes one step further and makes it so much more useful to be able to see and interact with the actual object in a layer:
Don’t get me wrong, I love Rhino, and its precisely why its so frustrating that it has all these incredible capabilities and in some areas, mainly the UI and user experience, it just feels like its light-years behind others (as evidenced by that huge thread on the UI overhaul).
And I know the old argument that you are catering to the pro users and they’ve all been fine so far, but that is not a valid argument. You keep pushing the expert stuff, but don’t forget about the basics. Rhino always had a technoligical edge with NURBS and Grasshopper that meant everyone just put up with the quirks. But that doesn’t mean that anyone would mind these basics to be there. It would lower the barrier for entry and just make everything a little more accessible for newcomers. And its precisely why Grasshopper is such a success. Great design and attention to detail in the basics!