how can I link more than one cluster with vray geo inside?
Cluster issue.gh (9.6 KB)
Hi,
It won’t work this way. The second cluster contains a reference of the VGeo component from the first cluster, thus the instance ID is the same. V-Ray uses the component instance ids to generate the object names, that must be unique. In your case you have two different cluster components that yield with the same VGeo ID and hence the same name. The second one will simply be skipped by the exporter, since it thinks it has already been exported.
You can hide V-Ray components in clusters, but you must have unique V-Ray components in every cluster. e.g. it is not OK to copy and use clusters with V-Ray components in them.
It could be nice if Chaos group solve this limitation in some way…it’s an important feature in my opinion
it is not a simple problem. We use the component ids for a lot of things. Primarily tracking objects that are deleted during interactive rendering. The usual “Grasshopper way” is to regenerate everything when it changes. This means we need to reexport the entire geometry tree on every scene mutation and restart the renderer all over. This is very suboptimal and will make interactive rendering very very slow.
I would argue if that is an important issue, since this is the first time I see such a request in 6 years, and you have very simple workaround - just put only GH stuff in clusters.
I’m using Grasshopper and Vray to create architectural projects without the need to bake and this is not a so common use, the power of this pipeline is relatively new, so it’s normal that in the last 6 years you haven’t received requests like this one. The power of this way of work is that is very speed and the files in grasshopper are very small (i link the materials from external) so I think this use will grow up in the near future. Anyway, I can understand that if I’m the only one with this problem now, you can’t solve it for me.
Quite the contrary - I’d be glad to solve it. However it is important to understand the tradeoff. Traditionally Grasshopper doesn’t care about object uniqueness, that is its power. However making the rendering, and in particular interactive rendering sane in this workflow is not possible. It is simply not an option to reexport the entire definition if something changes.
It is either fast and responsive interactive renderer, smaller files for cloud rendering and larger .gh files, or the exact contrary. First two cost time and money (and time is money too). And for the third, you can still use clusters to optimize the definition, simply don’t put V-Ray components in them.