Bug - Grasshopper Rhino components problem with inserted blocks

[martinsiegrist]

Query Model Block Definitions detect inserted blocks which in my case are just linked and not embedded.

EleFront 4.2.2 was able to deconstruct such an inserted block and I’m convinced Rhino 8 BETA was also capable of doing that?

Anyway, I hope this can be implemented again asap

PS: I think linked blocks help to keep the file size low and a link to an original file like a 3D scan export remains in the Rhino document.

A test file to insert can be found in this topic / post:

Rhino 8 Feature: Selective Clipping

Hi @BrianJ, I just opened this file again and something seems wrong with the PBR material. [image] selective_clipping_issues.3dm (3.7 MB) I’m also adding a new file with the mesh of an apple inserted and imported. Note how the clipping plane clipps the apple no matter if it is inserted without embedding or imported. But the trick with the color does not work when the content is inserted. Something with the texture is also not so nice when the clipping plane is moved. I deleted …

Thanks everyone for Rhino 8

[tay.othman (tay.0)]

Elefront is a fantastic enhancement to the Grasshopper ecosystem. I had anticipated that Rhino’s native tools would be compatible with it, particularly the new set of tools from Rhino that incorporate materials and display mode functionality.
What is missing is the items you mentioned above, as well as the quick query using the Value list component.

[martinsiegrist]

In the meantime I’m importing the blocks completely in Grasshopper.

[kike (Kike Garcia)]

Hi @martinsiegrist,

I think it never worked before, and if it worked was by mistake.
The intention was to enable features step by step and in theory linked blocks was still unimplemented like worksessions.

Linked blocks will be available in 8.1.