That’s what i thought but i can’t see the layer structure anywhere.
Yeah, colorizing by layer could be useful, but more importantly being able to hide/show select objects by layer is key since rhino realise so heavily on layers.
Can you send me a screenshot of layer tree in the viewer ?
Yes indeed ! thanks =) but it’s not possible to filter by layer using object properties right (this idea is to colorize objects according to layers for example, just like you said above)?
This is a very legitimate request, but unfortunately no
The why:
we’re structuring data by default in one way (that’s what you see in the scene explorer). for rhino it’s by layers!
filters operate on individual object metadata - basically “orthogonal”/independent of the main structure
we could store on each object it’s layer’s name as a property and that would allow for that behaviour, but it’s a dangerous hack and we’ll not get it out for you in time!
Cc @benjavo and @alex for visibility on this one. What the legit solution could be, which we can properly implement via DUI3 (mind you, fast thought dump):
Each layer will come with its own display properties (material and/or colour). Within the viewer, we could have some initial display fallback rules that mimic what host apps do, which would be:
object material, if none then
layer material, if none then
layer color, if none then
white
We should also think of this potentially in terms of the upcoming viewer display modes. E.g., rhino uses layer colors exclusively in “shaded” mode, and only uses materials in any of the “rendered” modes. This might be an unnecessary complication though.
Sorry @Raouf_Djema for the long answer saying basically “sorry we can’t do this yet” - but your feedback helps us improve, hence the wider team involvement on this one