I am working on a project where I have 4 files linked in, but it feels like I have hacked a system instead of having a system that was built for this. Here’s why:
Remember my preferences
I always use the “linked” block definition type and I always use the “Reference” layer style too.
But when ever I attach a new file Rhino reverts back to it’s own default instead of presenting me with what I used last. Please add a sticky feature to this setting, and add some more describing text because it is difficult to understand what they mean.
The “Layer style” description isn’t intuitive so I always have to explain what these means as “Active” and “Reference” doesn’t communicate that objects will merge into the “mother” file or have their own (for my use preferred) layer hierarky.
Remember layer states
So when the files are linked then stuff work. BUT I usually turn those files visibility off as they are fore reference use and I don’t want to see them all the time. And here’s the thing when ever I reopen the Rhino file then all those files visibility is turned back on… So I have to go and turn them off again. Not a huge deal, but why can’t Rhino remember those layer states? I guess we all would be annoyed if other layers or block objects suddenly decided to be on whenever I reopened Rhino, so linked files should follow the same logic and remember layer states.
And the old wish: REMEMBER the dwg settings, so if a DWG is attached and the Rhino file is saved, then it doesn’t ask what units system to use every time the rhino file is reopened.
Option have a linked file NOT attaced to an layer, just have it by it’s own, controlled by it’s own masterlayer.