Jump to content

nadmai

Members
  • Content count

    4
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About nadmai

  • Rank
    Peon

Personal Information

  • Name
    Dan M
  1. nprimsgroup equivalent in Python

    Thanks for the advice, much appreciated. That is a shame, since the path forward for houdini I suspect is to remove hscript at some point. The original python sop i wrote had too much looping. Thanks to 3dome I adjusted it and with low poly pieces in a for each sop its equivalent speed to the switch expression if len( geo.findPrimGroup( "outside" ).prims() ) > 0: geo.deletePrims( geo.prims() )
  2. Hi all, Is there any equivalent to nprimsgroup in python? I use this hscript expression in a switch, inside a for each SOP, to delete any prims connected to the outside group of a voronoi fracture: if( nprimsgroup( 0,"outside" ) !=0, 1, 0 ) Wondered what the python equivalent would be, because the Python SOP I wrote in its place is much slower to evaluate.
  3. Ahhh, many thanks. I was confused because when you set a foreach to single pass the point num will always be shown as 0 so I thought the loop would always treat each new point in the loop as 0, but I didn't reference from the right place. Over complication!
  4. Hi, I'm a bit stuck on how to get point attributes working per point in a creep sop inside a foreach SOP. In the attached file I created 10 points at world origin, gave them an x_pos attribute that is the same for every point. I gave them a y_pos attribute that varies per point. I hooked in the attributes via a spare input on the creep sop (same behaviour observed via spare input or direct reference). The x_pos will work making all the points travel around the object but the y_pos does not. If I modify x_pos so that it is a unique value per point it stops working. Could someone help me to see what I'm missing please? creep_point_attrs.hipnc
×