Render Layer / Material Override fail on some objects

#1

Hi guys, I’m not very familiar with the new system for managing render layers in Maya. I have a problem and I don’t know what I am doing wrong. So please help me :slight_smile:

My goal is to have an override for all objects applying my occlusion shader.

As you can see I have created a new layer called “occlusion” and in it I have a collection containing “References_Assets” witch is a group containing all my objects.
Over it I have added a material override, it’s working like a charm except for some objects. You can see 2 books under the tv have not the material override but they are in the same group…
What have I done wrong ?

#2

i assume you use nested layers on those…
if you use the collection filter “shapes” it does ignore shader hirarchies…

set the collection filter to “all” and test again…

#3

I am stuck with this too…
I’ve made a collection with the filter set to ALL (in fact changing that doesn’t make any difference) and with a name code like “Objects*” which selects the group in which I have the objects grouped.
It’s strange that it selects also some objects’ shapes that are NOT in that group O_o
But the real issue is that it doesn’t take the material override into account (either material or shader override).
So, how the hell can I assign a different material to the objects in a group?.
The legacy render layers were super easy to make these things, damn it.

#4

the legacy render layers are garbage, but they’re still better than the new tool?! I’d be shocked, but this is AD - so I really expect nothing else.

But do you realize you can switch back to the legacy layers? I just started working at a studio that was willing to go past 2015, ( Method studios ; Digital Domain still uses 2015 ) and they only use the legacy layers ( but with a huge in-house plugin that makes them somewhat useable ).

#5

Yes, I know I can swith to legacy. But man, they make the render setup in order to force you to not using legacy ones. When using legacy with Mental Ray, there are errors everywhere and go unstable. Legacy in 2013 were perfectly fine though.

#6

omg that sucks

you could try this
https://www.highend3d.com/maya/script/tiamat-for-may

written by an old co-worker of mine, it’s inspired by the lighting tool that Digital Domain built in 2007 and still uses. It’s kinda complicated to get it up and running though.