Hi ,
I am trying out the latest nightly from 11.8.
Somehow I am not able to make the Cryptomatte nodename with hierarchy to work.
None of my groupings works:
I tried
- traditional grouping
- namespace grouping
- layer grouping
None of them has an effect on grouping the IDs together. That said, the other ID Type group by ‘nodename’ and ‘material’ works though.
Its just the hierarchy which is giving me a prob.
We will have an additional “Namespace” mode to handle namepaces. It is different from the full hierarchy mode. We have the layer mode in 3ds Max, will see how easy it is to port it for Maya.
Hi Guys, I hope its ok to add additional question on the topic of cryptomatte without making a seperate thread. Its somewhat releated to the initial point of “nodename with hierachy broken”
Ive been experimenting with it a bit these days, and it seems that vray-proxy(loading alembic files) are regarded as a single node, and as a single material within the crypomatte elements.
Is it possible to get it to expand things down into the contents of the proxy node, getting names based on the alembic hierachy, and perhaps also the full set of materials linked though VRayMeshMaterial.
And similar behavior for “vray-scene” nodes.
Pretty much all of the contents within our scenes are based on the vrayproxy (which I btw still hope can get some love/replacement in the future so we can handle displacements and the like as we do with materials).
Is it possible to get it to expand things down into the contents of the proxy node, getting names based on the alembic hierachy, and perhaps also the full set of materials linked though VRayMeshMaterial.It’s not impossible, certainly… will see how easy it will be. The object names are not too difficult maybe, but materials are more complicated right now.
So Am I correct to assume that the full hierarchy mode right now basically lists every shape as individual. That’s how it supposed to work and I assumed wrongly initially and thought it was supposed to follow name space.