O yeah duhh that makes total sense! I've been lucky enough that I haven't had to deal with other DCC's in a while.

Saw this video before rafal explained those steps, might clear things up: https://www.youtube.com/watch?v=QOUYP7My80M [www.youtube.com]

Example with full paths inlc flags:

"c:\Program Files\Side Effects Software\Houdini 20.0.660\bin\hython.exe" "c:\Program Files\Side Effects Software\Houdini 20.0.660\houdini\python3.10libs\vop2mtlx.py" -f D:\circlepattern.hda -n circlepattern2 -o D:\mtlx\circlepattern.mtlx


"c:\Program Files\Side Effects Software\Houdini 20.0.660\bin\hython.exe" "c:\Program Files\Side Effects Software\Houdini 20.0.660\houdini\python3.10libs\mtlx2hda.py" -o D:\mtlx\circlepattern_converted.hda -p D:\mtlx\


"c:\Program Files\Side Effects Software\Houdini 20.0.660\bin\hython.exe" "c:\Program Files\Side Effects Software\Houdini 20.0.660\houdini\python3.10libs\mtlx2karma.py" -o D:\mtlx\karmaNodeGraphs.json -p D:\mtlx\

Edit (easierpaths)

mbeaud
So the idea would be, from one materialX graph (that could be created anywhere, Houdini, MaterialxGraphEditor, ...), get multiple "black boxes" with only the chosen inputs available for each DCC

@mbeaud where you able to figure this out? I'm stumbling through the exact same setup right now. One issue I have, is that unless I write the mtlx file by hand (in text) there is no way to define a node def where only a smaller set of specific inputs are exposed to the DCCs.