Hi all, who’s been helping with suggestions to my matte output issue.
txo: Thanks for the note about compositor passes renaming in File Output. That I’ve actually done already and works as needed.
I conclude with my last post for the matte topic that although there isn’t an existing Cycles option to do this directly, I have enough possibilities to cover my needs. But wouldn’t hurt adding RGB matte AOVs directly in Cycles also.
Below are 2 best options in my opinion at the moment.
1) Cryptomatte: This is technically best if using compositing software that supports it. Cryptomatte passes needs to be saved as a separate 32bit file output unless main render output is also 32bit. For my productions this works.
2) Create a separate matte pass with override material and pre-defined AOVs. This will do separate render for matte, but it is fast to render anyway. Can be included (connected to) in main File Output in compositor regardless of bit depth or saved separately with additional File Output. This will work for most compositing and image processing software. Attached image shows 4 steps to prepare for startup file. Example image has 5 matte AOV setups with 7 mattes each to work for object indexes of 1-35.
Additional note about AOVs: These could be prepared directly in main renderpass also, which wouldn’t require separate render with override material. But in that case to be able to use Object Index values AOV setup is needed to copy to each material in scene instead of in just one override material.
Extra: Actually World Position AOV is missing also in Cycles. In my previous production that was rendered pretty much with the 2nd option method as a manually created World Position shader render pass, because there is no existing pass for that.
