Hi Everyone!
I recently installed the cryptomatte package for 3ds max 2019.
After adding the AOV's, I proceeded to add the cryptomatte material, only to find that it did not exist; only a cryptomatte map appeard on the search.
Does anyone have any idea what is going on?
Supposedly, 3ds max 2019 should include cryptomatte in the first place, with no further actions needed from our part.
Cheers,
Adam.
Solved! Go to Solution.
Solved by Stephen.Blair. Go to Solution.
Cryptomatte is included with Arnold 5.2.0.0, so if you have MAXtoA 2.1.945 or later, you don't need to install the cryptomatte package.
In fact, if you have MAXtoA 2.1.945 or later, installing the separate cryptomatte package will break cryptomatte in 3ds Max (kinda like what you're seeing in your screenshot).
@Stephen Blair thank you for the reply.
So, it seems that I am already having the latest versions of Arnold and MaxtoA, is there something I can do to fix this "break" that you are talking about?
Best,
A.
I would reinstall maxtoa. And probably delete the old cryptomatte dlls, just to be suer
Hey @Stephen Blair,
I did reinstall maxtoa; also run a repair on the entire 3ds max app and still I get the same result.
My maxtoa folder looks like that. Is there something wrong here as well?
Thanks again.
A.
cryptomatte should be assigned as an AOV Shader, in the Maps group, not to individual objects. See
https://docs.arnoldrenderer.com/x/KQPfB
Hey @Nicola Jannuzzo hope you are well and thanks for answering.
Could you be a bit more specific? The post that you have linked does not really explain much.
is this the configuration you are talking about?