![](https://media.sidefx.com/accounts/avatars/1498/resized/160/160/blob.png)
rafal
rafal
About Me
Connect
LOCATION
Not Specified
WEBSITE
Houdini Skills
Availability
Not Specified
Recent Forum Posts
Mtlx Hda questions June 27, 2024, 2:52 p.m.
This popped up again recently so I re-did the example using an HDA as jsmack suggested.
MtlX Signature prefixes May 16, 2024, 2:59 p.m.
It's probably because you used "-n switch_20" on the command line. I think the MaterialX shader name is derived from the HDA name.
You can change the shader name in the HDA Op Type Properties in Houdini (RMB > Edit Operator Type). In the inputs/outputs there is a shader name for each signature. You can change that to an arbitrary shader name.
You can change the shader name in the HDA Op Type Properties in Houdini (RMB > Edit Operator Type). In the inputs/outputs there is a shader name for each signature. You can change that to an arbitrary shader name.
Vop2mtlx: UI with no input connections - Ordered Menu April 29, 2024, 11:09 a.m.
MaterailX shader nodes have only inputs, thus only VOP node inputs get translated to materialx. However, your channel reference approach (to the 'blend_mode' top parameter) should work, since ultimately you are setting a value on a MaterialX shader input.
As for the color-space value, in MaterialX, they are authored as an attribute of the input element. But `vop2mtlx.py` might not be handling them properly. It, it may be a bug/limitation of that script.
As for the color-space value, in MaterialX, they are authored as an attribute of the input element. But `vop2mtlx.py` might not be handling them properly. It, it may be a bug/limitation of that script.