VA3 BETA: Rhino 8 Content Cache

[Czaja (Jakub Czajczynski)]

Thank you!
Indeed it look like it’s working now. It is a bit limited still.
However, I would like to keep / specify the Rhino Model Object Attributes while using the Content Cache, and for that VA Elements must be accepted as a Geometry input in the Model Object component and not only as an Object.

Please see this thread:

Model Objects GH workflow and VA Elements

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). @kike @enric [image] [image] [image]