I’ve gotten used to the Model Object and Block Instance workflow. It’s a very logical system and it’s a highlight of the Rhino 8. I don’t know what technically stands in the way, but it would be great if Grasshopper VA Elements behaved similarly to native Rhino Block Instances and it was possible to pass them in the same way (without dumbing them down to the regular Block Instances, but keeping their parametric nature of course).
Hi @Czaja,
Rhino Model Object is a special Grasshopper data object that contains geometry and additional data, such as attributes.
Unfortunately, as far as I know, it is not possible to embed non-native Grasshopper geometry (like VisualARQ elements) inside it. Again, @kike can correct me if I’m wrong.
We can implement conversion methods so that these objects can be converted between VisualARQ objects and Rhino Model Objects, but the conversion won’t always be implicit. This means that if you forget to use a conversion component in certain situations, you may end up with errors in the definition or with regular blocks added to the Rhino document.
However, until I try it, I won’t be completely sure. Give me a couple of days to run some tests, and I’ll get back to you with more information. Also, I’ll try to meet with @kike to see if we can find a viable solution.
Regards,
Enric
@Czaja we have added support between VisualARQ object components and the Model Object and Query Model object components in VisualARQ 3.4 RC2, available here: VisualARQ 3 - Version 3.4 RC2 released
1 Like
Great! Thanks a lot, this is an important update.
There are some issues, I saw similar a couple of VA versions ago. Hopefully they will be solved. Top part of the script with regular Rhino objects shows expected behavior.
Hi @Czaja, try it this way:
I don’t think it’s a viable solution. If we convert Object to the Element before baking we loose Model Object data (layer, name, etc.) which is the whole point.
I see… We will review this and get back to you when it works well.
Yeah I’m having the same issue here, my beams won’t bake. I hope it gets resolved quickly. @fsalla
Hi @attheeast18 do you mean that your beams don’t bake with the Content Cache component? then make sure you have the latest VisualARQ 3.4 version, which is the one that adds support to that component. You can find it here: VisualARQ 3 - Version 3.4 RC2 released
If you already have that version and the problem persists, please share a file we can test this issue with.
Hi, @fsalla
I’ve updated to the latest version 3.4 version. I put it inside a cluster, for some reason, when it’s inside the cluster it won’t bake unless I open the cluster.
Hi @fsalla , glad that VA objects can finally be pushed using the content cache. However, I am facing issues trying to pull the pushed objects back into grasshopper.
Hi @attheeast18 ok, we will review this.
@juliusayz999 The Pull action still doesn’t work with VisualARQ objects. We will review this as well.
Hey Francesc, this feature doesn’t seems to work with grasshopper player, I am trying to convert my brep into slabs and wall, but it only output as blocks instead of Slab or Wall.
It works just fine if i opened the script and reference the object manually in grasshopper.
Can you have a look into this?
Thanks in advance.
Cheers,
Ray
Hi Ray, do you have an example to test?
Hi Francesc,
Yes. please see attached for the example files.
Slab from Brep_Bake.gh (15.9 KB)
Slab from Brep_push.gh (14.4 KB)
Slab from Brep.3dm (101.7 KB)
Additionally, when using Grasshopper Player, I get different outcomes from the “Push” and “Bake” functions:
- Push updates the object as expected but overwrites the data each time the script is run on the same files (which aligns with Push’s intended behavior).
- Bake, however, unexpectedly creates four identical copies of the object.
Since I’d like to reuse the script as a command, Bake would be the preferred method.
However, neither option results in VA objects when used through Grasshopper Player.
Hi @Rui_Hang_Yong1 I’m not sure if the Bake/Push component is supported by the GrasshopperPlayer command. The two issues you describe here (Push and Bake) also happens without VisualARQ components.
You need to use the Context Bake component instead to bake geometry with the GrasshoppePlayer (it works also with VisualARQ objects):
Hey @fsalla, I also tried using Content Bake, but still no luck, it bakes as Block if it passes through Model Object (to assign layer), or it doesn’t bake if i try bake it as a SLAB.
Hi @Rui_Hang_Yong1 you are right! the slab turns into a block instance once it goes through the Model Object component and generated with the Grasshopper Player. We will revise this behavior and get back to you when we fix it.
Hi, @fsalla
Just wondering, would it be possible for VA parameters to be compatible with the content components such as User Text,Content Information & Identity?
