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.