galagast

Hi, apologies for resurrecting this. The current functions does allow me to grab the Houdini Global Variables. But is there a way to get a list of these? os.environ works, but I'm only after the Houdini Global Variables currently in my scene >_<

Is this something close to what you are after? I used the xyzdist vex function to read in closest point data, which was then fed in to an Attribute Interpolate to attach the points even on an animated geometry. H16.5.438 Apprentice move_along_surface.hipnc

Hi, I've attached a file where I added a point attribute called "angle", the computation is based on a forward direction. Is this what you were after? H16.5.438 Apprentice angle_v2.hipnc

Have you tried the "Clean Transform" option of a geometry at the Object Level? (You'll need to move your geometry first at the object level) After selecting that, the parameters will be zeroed out. The pre-transform information is now stored.

That 'presets' parameter is calling a callback python script. You could try this: theGeo = hou.node('/obj/geo1/dopio1') # Keyword argument needed by the internal invokePresetMenu function myArgs = {'node': theGeo, 'script_value0': 'pyro'} # The internal python function called by the presets parameter. theGeo.hm().invokePresetMenu(myArgs)

Always glad to be of help! Cheers!

The documentation is the first thing I look through. But I agree, it does kinda lack in the way of examples. Next I also google stuff, where the results are usually from this forum, or at Sidefx. For general python syntax and functions, I still use google. Lastly, if I have an issue and all of the above is still lacking.. I would try and post a thread to hopefully get some answers. As for examples, I try and check out built-in HDA's and peek inside the Scripts tab, sometimes it contains python code. Also if you explore the Shelf Tools, most of those uses a module in the form of 'tools' that you can find at $HFS\houdini\python2.7libs They have lots of functions there with descriptions. I'm also still just learning as I go with my day to day Houdini adventure. Wishing you the best of luck!

Hi, I've updated the file. It now includes a way to create a group for each connected geometry, and only for those that are open. I used the Connectivity SOP to create 'class' IDs for each connected primitive. Passed everything onto a Foreach by the 'class' attribute, then used the npointsgroup() to filter/switch out only the open geometries, where it then creates a unique group just for that using the Partition SOP. H16.5.268 Indie - open_closed_tag.rar

@Noobini Haha indeed! All the while I thought that you need to set the the group entity to Edges in order to have access to all the edge related options. So yeah, the Group Promote can be removed in this case, then just set the Group SOP to a Group Type of Points.

Closest I was able to do (that was related to this) was to modify the agent transforms in a wrangle. But it might not work if what you want are animated vertices. Maybe have a look at the agentcliptimes() function? I'll try and do a test later if I have time.

Hi, I'm not sure if this is what you're after: open_closed.rar (H16.5.268 Indie) I used a group SOP to detect unshared edges, converted that group to points, then used the npointsgroup() expression to count and detect if there are open edges or not.

Hi, I checked out your scene and updated it. I added two angle values for yaw and pitch, which were then used in a rotate() function sequentially. You still had the @orient attribute passing through the Sweep SOP. Simply delete that and let the sweep use the PolyFrame's tangentu as N. H16.5.268 Indie - water_flower_v005_upl_jeff.rar I hope this helps!

Hi, here's also another approach. Vex based. The only drawback as of now is that this will not work for non-uniformly scaled objects. H16.5.268 Indie - pc_match_jeff.rar

Hey Ben, some of these threads might lead you in the right direction: And just in case you plan to use particles as points to copy onto: I hope this helps!

Something like this? node = hou.pwd() geo = node.geometry() geo.addAttrib(hou.attribType.Point, "name", "") for point in geo.points(): point.setAttribValue("name", "piece" + str(point.number())) Then look at this post by Graham explaining why string types does not have a default value.