CryptoMatte not included in vrscene export?

[hypotheticalinc]

It looks like the Cryptomatte element isn't getting exported when I send out a vrscene file for rendering on standalone - is this a known limitation?

[vlado]

It will be implemented in a patch release a little later on.

Best regards,
Vlado

[hypotheticalinc]

Wonderful, thanks Vlado

[hypotheticalinc]

Any news on when this will land? Hopefully pretty soon now that 3.6 for Maya is out?

[hypotheticalinc]

Is there a workaround for this in the meantime? I tried adding a CryptoMatte render element to a simple .vrscene manually and it didn't work right, but not sure if it was a problem with the .vrscene edit or lack of support in the standalone renderer.

[vlado]

We don't export the object names into the .vrscene file yet, so if you add a Cryptomatte element it should generate the masks but you won't be able to pick by name.

Best regards,
Vlado

[hypotheticalinc]

Not having objects names would be fine for now, I usually use the color picker anyhow.

I tried simply adding the CryptoMatte elements like this:

RenderChannelCryptomatte VRayCryptoMatteMat@RE_1 {
  id_type=1;
  name="CryptoMaterial";
}

RenderChannelCryptomatte VRayCryptoMatteObj@RE_2 {
  id_type=0;
  name="CryptoObject";
}

For both the material matte and the object matte I got everything on one matte only, despite different materials on the objects. Do I need to change the alias parameter? (I tried it with and without and got the same results)

Is there a parameter I need to set on each object or material?