Material Override Exclude

[Dave_Wortley]

As soon as you have materials which have multi-subs or VrayBlend materials, SSS etc anything like this starts to get complicated.

I started looking at a Node-based approach for creating material override rules, it gets pretty dirty quite quickly. Really powerful but you need to understand the class system for it to work. Never got beyond the concept stage but it could do some very clever things if I finished it.

I really think you guys should just look at my script solution, it works well. I know there's a few small issues, keep bugging me and I'll find a moment to fix them, I think it's mainly just ForestPro and their weird way of dealing with materials.

[^Lele^]

Save a scene state (materials only) called "Production" or similar.
Run the code here.

(    for m in (getclassinstances vraymtl) do
    (
        m.texmap_diffuse_on=off
        m.diffuse=white
    )
)

save a scene state called "Override", materials only.

Now you're free to switch between them.
Of course, it's quite trivial to change the above code to match whatever it is you want the custom overrider to do.

[3LP]

I hate scene state! It's bugged, when you import new geo it bugs as well, and in conjunction with RPM, I'm not sure it's the best idea.
That's why I like to have it as a global switch or a material, or even a plug that can be used as a map would work as well if that shouldn't make it in regular Vray or any other way to get this working but coded by Chaos because I'm not trustworthy for Autodesk anymore, specially with the kind of "features" they release that never make the debug and stay haunting 3ds for generations IE : containers. It took like 9 versions of max to get the xrefs stable, and now the groups are unstable in max 2016. Sum up how AD works and you quickly get why in production, we want to rely on Vray

But anyways, thanks for script, might be useful one day.

Stan