Sorry to be blunt, but the point of this thread is: Reference layers reset everytime reference is updated.
You suggested using linked, and I pointed two reasons (one probably a bug specific to ‘Linked’, the other likely a more general bug - see Bug - BlockEdit Linked block renames nested blocks - Rhino 7 - Rhino)
You do not address any of these points and suggested using Worksession, which I spent time try to remember and writing about it but, luckily, I did not spend any time retesting them because - later you mention (and I had forgot) - that layers will not be saved, which it is the point I was asking to get solved.
You then mention that going too deep into nesting getting problematic (also in other software [not true]). But again this is not about multiple generation nested blocks. It doesn’t and/or it shouldn’t get problematic, but this is not the point of this thread. This is about the layer status of linked files. Surely, this is something easily fixed.
The point is:
I cannot imagine a common situation where this is desired out come:
- You reference a group of models, turn layers on and off, set a scene.
- Someone updates one of the references.
- You update the scene and the reference is reloaded in whatever status the last person that worked on it left it.
- the scene needs to be reset… every time this happens.
Can you imagine if that would happen in AutoCad? It doesn’t and for good reason.
Risking stating the obvious but trying to really drive through the issue:
- different scenes will require different layer status, therefore the linked file can’t always be saved in the ‘correct’ status.
- different linked files may have common layers, when it appears/disappear for one it appears/disappears for all.
- when I change the material or the color of the layer in the scene, rhino already remembers does not change it back to the original when it updates. Rightly so!!!
Again, this should be easily fixed, it is fixed for the color and other characteristics of the layers!
Please put this on the road map…
N