Ethan Estrada

tamte
add vm_matteshader to the properties shader of your material and point it to shader that should be used as a custom matte shader instead of default one

Genius! I tried it out at the geometry level and attached some quick and dirty renders to this post. Thanks a million tamte.

Is there anyway to attach a matte shader at the geometry level? One pretty common workflow at my studio is to attach most materials at the geometry level. This is great until you need to matte out an object that has a bunch of difference shaders with different transparencies on each shader. Is there some primitive attribute I can attach? I have tried “shop_vm_matte” and “shop_vm_matteshader” (similar to the “shop_vm_surface” attribute), but mantra does not recognize them as anything useful.

Another related question (which may solve the issue more cleanly), is there anyway to automatically force the surface shader to be attached as the matte shader as well? I already wrote some VEX code to automatically turn a surface shader into a matte shader based on if the object has been marked as matte. The only thing is I want the matter shader to automatically default to using the main material/surface shader instead of whatever global matte shader gets attached. Does mantra support something like this? In the past I have simply linked the matte shader parameter to the surface shader parameter with a relative channel reference at the object level, but that won't work with the workflow adopted here of attaching shaders at geometry level.

From what I can tell, there hasn't be a new post in over two years. Are there plans to add more to the old school blog or has it more or less been shelved and archived? I always learn so much from Jeff's posts on the Old School blog. I would hate to see it never be updated again.