Couple of months ago in May 2021, I used to have my grasshopper definition reference elements inside linked files in the Rhino 7 document. For example, test-file-2.3dm has a linked copy of test-file-1.3dm (block definition type: linked, Layer style: Reference), and the grasshopper definition is able to reference individual elements in test-file-1.3dm by referencing the linked file’s layers using the Human plugin’s Dynamic Geometry pipeline or the default Geometry Pipeline component. Elefront’s Reference by Layer component works too. I’ve done this for about 20 of my definitions.
Fast forward to Jan 2022, and a few updates to Rhino 7 later - I opened up a few of the old rhino files and grasshopper definitions to find that this no longer works. Human, Elefront, and default Grasshopper now seem to be unable to recognise individual elements in Linked Files. What appears in place, are InstanceObjects/Referenced Blocks.
Does anyone face the same issue, and are there any solutions? I’ve been able to replicate it on a fresh install of the latest Rhino 7 on a fresh install of Windows. Have also attached the files I used to test this.
I would expect that as well, except that it worked previously. I could simply insert an external 3dm file as a linked block, and Grasshopper would be able to recognise individual breps inside the linked block. This was my workflow for the whole of 2020.
Would it be able to add this as a feature request?
Just want to give an update to this thread.
I’ve tried using the older versions of Rhino, uninstalled and reinstall all plugins, ran it on a different machine… Nothing allowed me to replicate the old workflow of directly referencing individual breps inside a linked block.
I’ve chalked it up to a bug probably only present on my machine due to some freak installation error, considering circumstances at that time.