I have a Rhino file with some layers in a hierarchy and the Layer-States are completely unpredictable. This is soo bad that I’m asking myself if the problem is on my side?
It is hard to explain so I recorded a short, simplified video (my original file has much more layers and a more complicated hierarchy):
Can you provide the file?
This is a pretty well established feature so thinking there might be a slight workflow issue rather than a bug.
Here is a good breakdown. Rhino 8 Mac Import Layer States confusion - #14 by mary
Here is the download link:
Thank you for the file and I understand your changes. You have set up the layer visibility for each layer explicitly (one by one). This is fine with this example file that contains only a few layers and states.
But this means that I can not use the states on “parenting” layers with a layer hierarchy?
In my production files I need to import for example multiple DWGs from different sources that come with hundrets of layers each. I usually structure them with a layer hierarchy because otherwise this is not manageable.
Setting it up the way your file works means I have to switch off hundrets of sublayers each time I want to save or update a layer state, I have to remeber their states before I switched them so I can turn them back into their original state to continue work.
This is not a practical solution and the workaround would cost me more time then the benefit of the layer states itself.
Hi @toromanovic,
Something doesn’t seem right with the Model On column restoration. I’m looking into it.
The global On column seems to work correctly. AutoCAD doesn’t have an equivalent to Model On, so maybe this is option until this issue is resolved.
– Dale
Thank you for the reply, good to know that global on/off works. I usually never use the global on/off as it affects also my paper layouts.
But in this case it will work as I have no paper layouts. I use the layer states to organize the renderings I have to create.
By the way: In my opinion the global on/off can be removed entirely, having 2 different switches just complicates everything. Paper layouts allways need to be independant from the model space so thats why the model on/off is the right one to use, but thats an other topic 
Do you consider this bahaviour here with the model on/off as a bug? Shall I report a bug?
Thank you for your help.
Keep in mind the model on feature is new in Rhino 8, and its only useful for those using layouts. If you find the number of icons confusing, you can always turn off the global on column - click the Columns button on the panel toolbar.
I already have - see the link in my previous reply.
– Dale
Thank you very much for your help!
RH-92648 is fixed in Rhino 8 Service Release 30
Thank you very much!