Search the Community
Showing results for tags 'Mantrasurface'.
Found 1 result
-
Hello all. We need to expand the default Mantra Material with some custom functions and compile it. However, as time goes on, bugs are fixed and major/minor Houdini releases changes the shader internals, making it a hassle to continuously go back to the material, check it, fix connections if necessary and recompile. I'm wondering if there is a better way to do this? I have thought about rebuilding our customizations using a python script, but with potentially hundreds of new nodes, connections and unknown future changes by Sidefx, this too have the potential to generate unwanted labor. I have also thought about using DAs, but many of the connections are not easily contained within one or a few assets (in and out of the surface model for example). So, I ask: Is there a preferred way to maintain what sesi does and smoothly inject our own before compiling the material?
