I’m using the geometry pipeline to reference block instances on large models and I find 2 main issues :
-First, I think it lacks an optional trigger because, since it’s the only “Human” way to reference InstanceObjects in Grasshopper, it would be practical to make it look for blocks only when needed.
-Second, I find that the component runs three times… No idea why, but this causes a lot of downstream components to run multiple times uselessly.
this doesn’t work because when disabled, there is no more output, and the definition can’t run without that data.
I’m trying to work my way around the problem using the Elefront component “Reference Block By Name” which I find is is extremely useful, although it outputs a special class of objects.
I get the GUIDs and from that, extract useful data :
If you wanted to persevere with Human and Metahopper, you might be able to use a data recorder. Instead of the built in one, I think the one they include with the fologram plugin might be a bit easier to incorporate into program flow.
I checked out the Fologram plugin page on Food4Rhino.
It’s a Rhino plugin and GH plugin ; I’m not sure I want to make my loading times longer just to get one improved component…
How does their Data Dam improve over Gh’s ?