Jump to content


Popular Content

Showing most liked content on 06/03/2018 in all areas

  1. 2 points
    I found the solution. 1) Create a number of points equal to the number of total packed prims you have in your sim (not the number of unique pieces. for my building it was around 18,000.) I used the points generate sop for this. Each point corresponds to a packed prim. Drop down a wrangle and plug your points into the first input. Attach your simulated packed prims to the second input. For each point, you will create 3 new attributes: v@pivot, 3@transform, and s@name. The pivot and the transform are primintrinsics and you can copy them from the current packed prim attached to the second input (current meaning the one indexed at @ptnum). Also copy the packed prims positions and piece string attribute (@name_orig in the tutorial) onto your point. You can use the @name to create a new attribute called s@instancefile that points to wherever that particular piece's .rs proxy file is located on disk (this of course could have been done in one step but I like to break it up). Now you have all the attributes on your points that Redshift needs to find and instance your proxies. 2) Make sure to add the RS obj parameters to whichever object contains your new instancing points, and BE SURE to untick the box under instancing that says 'Ignore Pivot Point Attribute'. Anddd your done!
  2. 1 point
    Wow. You are a genious for figuring this out - thank you very much! I definitely have to try this out soon.
  3. 1 point
    Hi mark, I have done similar test long back. There is a target(parent point) and points(child) coming towards the target(both have the same point count). When a child point acquires a target point the other child point doesn't query the same point. have attached the file.runs pretty fast. make sure the active distance is less. Since i have used array it is pretty heavy when there are more points to query at that instant(when active distance is more).Also you can disable attract in sop solver and get the positionId(posid) and use pop attract. nearbyattract.hipnc FX TD Dneg
  4. 1 point
    Multi-context Bend.
  5. 1 point
    I had a go with python..and for good measure, I sabotaged the nicely ordered ID sequence by randomizing the order 0,0,0,1,1,344,344,344,344,999,999. beside needing an extra partition node, the python code is actually quite succinct. node = hou.pwd() geo = node.geometry() i = 0 for group in geo.pointGroups(): # loop for each group for point in group.points(): point.setAttribValue("id",i) # reset id to sequential counter i += 1 sort_id_python.hipnc
  6. 1 point
    If you are talking to do it with an attribute transfer I guess you are trying to change the result of the simulation, outside of a dopnet. In this case what you need to change is the position and not the velocity of the particles. Or are you doing it inside of dops? If this video shows something similiar to what you are trying to do, maybe it can be helpful
  7. 1 point
    Very pretty! Similar things have been covered here before, here's a rebuild of one of those techniques. Dunno how the c4d stuff is working, but this setup isn't controlling the paths by the dots, its the other way around; generate a volume of curl noise, scatter points, trace lines in the volume from those points, do stuff. trails_thing.hipnc