Chris Rydalch

No, this input doesn't actually do anything, and there are conversations on the MaterialX side to remove it because of that. If you need to transform the viewdirection, you can plug it into a mtlxtransformvector node.

nicholasralabate
Bump for question about light linker -- is it possible to use Light Linker on geometry lights? I am trying to light link an emissive volume, but it's not showing up at all on the "lights" panel of the light linker...

Not yet, but in a future release this will be possible, as Geometry Lights in USD are now decorated with an ApiSchema, so USD/Hydra recognize them as actual lights.

It's not always the case that layers == nodes, but where possible, LOPs will record a node's id to the "HoudiniPrimEditorNodes". This custom data is set per-primitive, and you can see it in the Scene Graph Details.

You can get at the nodes with a help function we have in loputils, by passing a lop node and prim path to loputils.getEditorNodes(). It just helps get node paths from the node ids stored as customdata.

This is used in the Scene Graph Tree's "Jump to Existing Editor Nodes" option, when you RMB on a prim.

Hope this helps!