Yeah, I would expect that to work too. I can check with @AndyPayne to see what is happening.
ahh i see the issue - I have to pass an object through to the model object component. It can’t be the block instance component. If this is to remain the case, it would be great if the query model components also had a type filter as well name, layer, group.
Once you got a wire hooked up to the Block Instances output of the Query Objects component, you can right click on it again to Hide Unused Parameters and it will make it into a much more compact component.
is there anything in the pipeline to add texture mapping into the “keys” section fo the filters? - it would be great to be able to pull this info out of model objects to allow for it to be copied to other objects.
We do have plans to support UVW mapping as a “type” in Grasshopper. When we do, you will have access to the properties of that type, but I do not have a timeline as to when this feature will be implemented.
It would be an awesome addition! we do a lot of non destructive work in gh deconstructing blocks- running booleans on them and then reblocking them uniquely, and it would be amazing to be able to retain the same texture mapping on all booleaned objects that existed on the intial blocks, as we then use these models for rendering.
Hi Giovanni, Here is a way using Rhino 8 components.
I believe you need to extract the block geometry. Can you share the GH definition?
Yes, taking a look at the file and definition would be great.
Block definitions tend to be a bit more complicated in that the instance holds only a reference to the definition and a transformation. The geometry exists in the block definition itself.
