Bad AA on vray proxy cryptomattes. Fine on vrscene or native geo

[brobins]

vray build 4.04.02.28695

we have noticed on a current project that the AA on cryptomattes is very bad when the source object is a vray proxy. vrscene assets or native geo alias' fine.

we've tried upping min samples to 4 but has no effect on the aliasing

[nikolay.kusht]

Could you send us some test files so we could investigate this further?

[brobins]

Of course. Please find simple maya scene attached which show the issue. The first scene has 6 objects with unique materials assigned, the cryptomatte renders with correct AA. The second scene contains 1 vrmesh file of the same 6 objects & shaders and the cryptomatte renders without AA.

Here are a few examples of how they look inside of Nuke..

Looking closely at the images now, it looks as though the issue is specific to areas of overlapping geo.

Is there anything I can do try remedy this issue?

Thanks

[yolov]

This is a known issue. The 'material name' mode of the cryptomatte doesn't produce correct AA with proxies. In fact, the whole problem is that the individual objects inside a proxy don't work well with cryptomatte at all. It's high on our list of things to fix, though, we hope to have some progress soon.

[brobins]

Ok thanks. Keep us posted

[GoodbyeKansas]

Any update on this?

-- Erik

[yolov]

This should be fixed in Update 1 (a.k.a 4.12.01). What version are you on?

[GoodbyeKansas]

We are using that version

[2019/Jun/25|13:42:24] V-Ray: V-Ray Next for Maya, update 1 version 4.12.01.00001 from May 8 2019, 19:15:51
[2019/Jun/25|13:42:24] V-Ray: V-Ray core version is 4.12.01

Can send example exr over email.

-- Erik

[yolov]

please do - alexander.yolov@chaosgroup.com
We have some more internal changes that we'll include in another small release, but it would be good to make sure it all works in advance.