Hello, here’s how any locked block looks like with “locked objects appear tranparent” set on.
In earlier versions (e.g. v5) everything behind was visible. Am i doing smth wrong?
1 Like
Hi -
I see that Rhino 8, Rhino 7, and Rhino 6 all behave the same way. That leads me to think this might have been a deliberate change, but I’ve created a YT item so that this can get checked.
→ RH-83645 Display: Locked Blocks Occlude When Set to be Transparent
-wim
2 Likes
RH-83645 is fixed in Rhino 8 Service Release 13
“Vincent, we not happy”
I made some testing, seems to have some instancing issues - copied items’ lock state affects parents’ one.
Hi -
I have no idea what you are doing in that video. Please post a 3dm file and/or step-by-step instructions to reproduce an issue.
-wim
I’m sorry.
The right box (labelled Block) is a block made in-place from the box, the left one is a regular polysurf. As you can see, it gets transparent when locked, as expected.
Secondly, i make a copy of it and lock the copy instance. Having a child object, the parent block gets transparent in an “old” way. But locking child block removes occlusion from parent object.
Locking only child block alters parent’s shading, which i did not expect at all.
I was playing with boxes, becuse i was not sure if the issue belongs only to gems’ blocks (they are generated in Gemvision Matrix software). As you can see, gems also depend from instancing.
Hope that helps.