esttri
you can always set this directly using:

xform.LookAt.v2_0(lookat_xform, lookup_xform)


There is however a way to automatically get the latest version of a given callback.

On your SOP node go to the Header folder. Turn the header toggle on and use the toggle add Version. Then a little function called HoudiniVersion() will be added to the beggining of you snippet. Based on your current houdini version we can now automatically deduce which version to use. meaning that

xform.LookAt(lookat_xform, lookup_xform)

should give the correct latest version.
Having said that. This is currently not supported for your own custom functions.

I hope this helps

esttri
You can use the AttribAjustArray SOP, it comes with a viewer state. if you set the Attribute Class to Points it should show your joint tags.

william_harley
Hi, Its not possible to set the defaults using the addAbstractControls at the moment. For this you will have to use updateNode().
To promote the inputs set the promote and parmnames on the addAbstactControl. To do this, enter the channel you want to promote separated by a space. Parmnames should also be separated by a space, and will name the ports in the order that they are promoted.

abs = graph.addAbstractControl(promote='x y', parmnames='one two', name='test')
abs.updateNode(parms={'x':1, 'y':1})

kodra

Image Not Found

You can do it by piping all these extra geo as dummy TransformObject and drive their position from the AbstractControl.

That's a bit complicate though. I don't know if there is a simpler, built-in way to do this.

tamte

NMVHS
I feel like this involves creating a SOP context in DOP, but now sure how to do that.

processing of any geometry data in DOPs can be handled using SOP Solver DOP node

npetit
Here's an example:
Create a sphere, a cube and a torus, plug a python LOP and set it to use this code:

from random import random, randint
import hou
from hou import hmath
from pxr import UsdGeom, Gf

node = hou.pwd()
stage = node.editableStage()

numinstances = 20

prim = stage.DefinePrim("/pointinstancer", 'PointInstancer')
pi = UsdGeom.PointInstancer(prim)
rel = pi.GetPrototypesRel()
rel.AddTarget("/cube1")
rel.AddTarget("/sphere1")
rel.AddTarget("/torus1")

protoindices = pi.GetProtoIndicesAttr()
protoindices.Set([randint(0,2) for x in range(numinstances)])

pos = pi.GetPositionsAttr()
pos.Set([[float(x * 5), 3.0, 0.0] for x in range(numinstances)])

rot = pi.GetOrientationsAttr()
rot.Set([Gf.Quath(*list(hou.Quaternion(hmath.buildRotate(random()*180, random()*360, random()*270)))) for x in range(numinstances)])

scl = pi.GetScalesAttr()
scl.Set([[random()*2+0.2]*3 for x in range(numinstances)])

BryanRay
The extra layer will be expressed in the Scene Graph as another descendant of the asset. For instance, if you had 'light1' in your extra layer, then your component output (assuming otherwise default configuration) should have descendants called 'geo', 'mtl', and 'light1'. You could control the light using a Prune, Light Edit, or Light Mixer, just like any other primitive.

Knowing the standard prim path outputs, you could build a primitive pattern to select the extra layers. For instance:
/componentoutput1/* ^(/componentoutput1/geo /componentoutput1/mtl)

That selects everything under /componentoutput1 except for 'geo' and 'mtl'.

Heileif

NMVHS

AhmedHindy

The solution to this problem is to use one ComponentMaterial node per geometry variant. You need to plug them between the ComponentGeometry nodes and the ComponentGeometryVariants node. You can hook them all to the same materialLibrary node.

this maybe works for this simple setup, but what about a for loop for the component geometry lop that feeds into the componentGeometryVariants lop?

I cant get the materials to apply to each variant except the last variant.

I'm exploring a similar setup with for each loop. I wonder how you set up the component output node in the end? I lost all the variants somehow after adding component output node.
Thanks!

I have the same problem :/

AhmedHindy

The solution to this problem is to use one ComponentMaterial node per geometry variant. You need to plug them between the ComponentGeometry nodes and the ComponentGeometryVariants node. You can hook them all to the same materialLibrary node.

this maybe works for this simple setup, but what about a for loop for the component geometry lop that feeds into the componentGeometryVariants lop?

I cant get the materials to apply to each variant except the last variant.

ghostpro
I think I have narrowed down that my client cannot seem to access the shared folder through Hqueue client. The client can see the files just fine through windows explorer. Does anyone have experience with the log on options for the Hqueue client service? I am only running a local account on the client machine. In order to map the shared network folder I had to use a username and password which is seperate from the local account.

goldleaf
The For Each LOP is not actually changing the variant, it's just cycling through the variant set's values (i.e. all of the "model" variants). Similarly, when iterating over primitives or numbers, those are just values filling out the context option values.

To see these values in this case, you could use a Set Variant LOP. Set the prim path to "/model" and variant set name to "model". Then you can use `@VARIANTNAME` set the variant. If you don't want to author the setting of this variant, append a Layer Break after the Set Variant node.

To edit the variants via For Each LOP, you'll also need an Add Variants LOP. You just need to make sure all of your additions/modifications are children of the variant primitive (i.e. "/test" in this case).

This is a workflow we want to improve in future releases. Hopefully this example helps in the meantime.