VrayCryptoMatte, doesn't work with Xref Materials.

[Vizioen]

Ah yeah that's what I thought at first but didn't see in the screenshot you used XrefScene.

vladimir_krastev thank you, would be awesome and save us a lot of time.

[garipodelu]

Hi garipodelu you are using x-ref scene that is why it works in your case. We are testing x-ref object setup and it does not work in none of the versions I tested. I will talk to the developers about the VRayCryptomatte for x-ref object.

Thanks for clarifying that. Indeed we always use x-ref scene in our workflow.
Vizioen maybe you can switch from xref objects to xref scenes as a workaround and if you need to move objects just attach them to a dummy object.

[Vizioen]

Thanks for clarifying that. Indeed we always use x-ref scene in our workflow.
Vizioen maybe you can switch from xref objects to xref scenes as a workaround and if you need to move objects just attach them to a dummy object.

Well that would impair my workflow to mock-up scenes fast. I have a lot of landscaping to do, sometimes with very specific trees, and a lot of different kinds. I have most of these in my library (Connecter). I just drag them in my Max import as Xref object and I'm good to go, if I need to change something about the tree I'm still flexible with an Xref Object. Not so much with XrefScenes and VrayProxies. Once I'm done I can still convert to proxies, but most of the time that doesn't happen as there's no need.

[vladimir_krastev]

The issue is reported under VMAX-13406 in our bug tracking system.

[Vizioen]

Hi, vladimir_krastev, any update on this? Thank you.

[vladimir_krastev]

Hi, Vizioen Sorry to say but no, there is no movement on this issue for now.

What about the idea of using x-ref scenes?

I just drag them in my Max import as X-ref object

You can drag and import as x-ref scene as well but I am not sure how your library is built. I personally avoid using x-ref objects. They seem to be more prone to issues compared to x-ref scene.
I do not have any data to back this though, just sharing my experience.

[Vizioen]

I never had any issues with Xref Objects, they work perfectly as intended.

Xref scenes aren't usable for what I'm after and not flexible at all. If you want to move an XrefScene you'd have to bind it to something too. If I want to change something I'd have to open another Max, fiddle in there, save, reload and see if it's ok in the other scene.

Even when using VrayProxies, there's still the issue of trees or plants with the same names (as happens a lot, cfr leaf, trunk,...) being selected all the same.

[Vizioen]

The issue is reported under VMAX-13406 in our bug tracking system.

Hi,

Has there been any changes on this, it seems this issue hasn't been fixed in 6.2 update, as well as with cryptomatte material differentiation between materials with same names (whether or not belonging to different multisub mats).

[vladimir_krastev]

Hi, this issue is not fixed with the 6.2 update. It is not very common to hit this bug and probably other more urgent issues took the lead for fixing. We will notify you when we have something ready.

[Vizioen]

Hi Thanks for the answer. Just wondering: using Xref Objects isn't a workflow that is common? Or in combination with Cryptomatte specifically? Or cryptomatte isn't widely adapted yet for this problem to arise often?

[vladimir_krastev]

Hi, I personally avoid using X-Ref Object when I build a project. X-ref Scene gives you the same functionality and works better from my experience.
Also there are other factors that need to align for the issue to reproduce.
As far as I can see the issue is only for VRayCryptomatte with ID type "Node material name" if used for x-ref objects with MultiSubObject materials.