Jump to content

Recommended Posts

Hi guys!


Did anyone understand how does the cryptomatte works with redshift?

Until now, I found how to make it work with materials, with different obj... but i would love to know if its posible to make it work with an attribute for example, or groups.

For example, if I drop a copy to points with spheres, how would you guys give a different crypto id for each sphere? I dont mind if its either groups or attribute, but its been a 1 year fight and i coudlnt never make it work.

I attach this example just in case there is a genius around with a good workaround about this subject!

Thanks you very much!

MAC_crypto_example.hiplc

  • Like 1

Share this post


Link to post
Share on other sites

Saul Espinosa did some tutorials a couple years ago discussing Cryptomattes and Redshift, and the options for generating Cryptomattes.  I believe these were in Maya, but the controls for Redshift are basically the same between the packages.

Share this post


Link to post
Share on other sites

Yeah, i watched that several times, in maya is quite straight forward because all the objects are "separate", but in houdini, when you do for example a copy to points, all the spheres are considered the same object, so the crypto doesnt make a proper id per sphere.

That's why i opened this thread, crypto is super straight forward in all softwares but here, i would love to have a crypto for each different parts of a car for example, not having to assing a different shader or split it in different geometries at obj level.

Thanks!

Share this post


Link to post
Share on other sites

I was searching redshift forum regarding another cryptomatte related issue (namely gargantuan increase in render time when outputting cryptomatte which seems to be another insurmountable problem for redshift devs) when I stumbled upon someone being very angry when learning that is not possible at all. What he wanted was partitioning by primitive attribute such as @name.

While extremely useful and fast to set up cryptomatte is pretty much useless as it is in redshift. I reverted to using puzzle mates; it's a ballache but at least it won't take a millennia to render.

Share this post


Link to post
Share on other sites

I'm having issues with cryptomatte with Redshift, both in Houdini and Maya. I think there might be a bug with the current version of Redshift and Cryptomattes.

We are in the middle of production so upgrading Redshift is out of the question.

I'm going to try Mantra to render out a cryptomatte pass.

 

Share this post


Link to post
Share on other sites

Thanks Librarian, ok I foound that there is a reported bug with RS 3.0.30 which causes all other AOVs to be blacked out when Cryptomatted is enabled.

I have updated to latesr RS which is 3.0.50 and Houdini 18.5.596.

So far so good, but getting an error about OCIO profile not loading and failing the render.

Will do some more digging around.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×