JuhaT
It is obvious that transform node is calculating something more complex than I could ever imagine.
yeah, lighting
JuhaT
It is obvious that transform node is calculating something more complex than I could ever imagine.
ajz3d
What's so special about those parameters that referencing anything from them is impossible? Is there a workaround for that?
am_wilkins
Still new to Karma, isn't Dicing separate to whether something has displacement or not?
rafal
1) Build a subnet VOP containing the implementation of your custom shader. There are some annoyances with defining subnet inputs and naming them. Pretty much the input name is imposed by the Subnet VOP, and will need to be hand-edited in step 3.
mbeaud
Althought, it only works in houdini CPU, not in Houdini XPU nor in the viewport (HoudiniGL). Do you know if there is a similar script (to mtlx2karma) to "register" or create the renderer specific node for the Materialx for HoudiniGL and Karma XPU ?
mzigaibthe material library is not only for "storing nodes" its primary purpose is to translate shader nodes to USD. Since the lens shader is not translated to USD, the material library is not needed. The generic matnet will suffice.
Thanks for the feedback and help!
I found it inside the cvex context inside material library, is that not recommended?
janjansen
is there an easy, layman friendly way of either converting this existing config to ociov2, or to weave in the TCAMv2 transform into the built-in one?
janjansen
- houdini creates its own (ocio v2.1) config and places it in C:\Users\<my_user>\Documents\houdini20.0\ocio after editing it in OCIO editor, correct?
janjansen
thank you, can you elaborate a bit please?
the default seems the standard (un-tonemapped), I'd like to use TCAMv2. so the drop down is set to standard (without being able to have houdini recall changes to it) (all intended view transforms are available in the drop down)
where should I add this line to?
edit2: default_view_transform: TCAMv2
^ this line actually got added by the OCIO editor, houdini just doesn't take it into account
timjan
Wonderful news! Does that mean the next production build? Thanks :