Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

rich_lord

Members
  • Content count

    177
  • Joined

  • Last visited

  • Days Won

    8

Community Reputation

112 Excellent

6 Followers

About rich_lord

  • Rank
    Initiate

Contact Methods

  • Website URL http://richardlord.tumblr.com/

Personal Information

  • Name Richard
  • Location Seattle
  1. Very Pain! I assumed creating constraints at the position of the impact would be easy. NOPE! You have to transform each impact point into the rest position(Easy) AND the rest orientation(NOPE!). Luckily i'd done this about 100 years ago and I vaguely remembered how. Here's how to do it. You can get the file here
  2. Recently I wanted to make constraints based on impacts. I finally managed it. Here's the basics of the system. It uses a couple of ForeEach SOPs to step through and delete any constraint between the same two rbd's. Phew! This one was really tricky to work out. The hip file is available here
  3. Ok, Just 2 days to figure this out! I tried so many things, but ended up just using a foreach SOP to step through each constraint and compare it. Its not the fastest...... I also do the same thing on the initial impact points too, which seemed to be a little faster as I cull some points before I even build the constraint. The constraints are currently just made at the center of each rbd, but its easy to shift it to the exact point by using the info in the DOP Impacts. Get the hip here - http://richardlord.tumblr.com/post/158126297816/hipfile-making-collisions-based-on-impacts-is-way
  4. Im making constraints based on impacts in DOP's. I've got it all worked out except for the fact that I get so many impacts, i'm making way too many constraints. I can see that i'm getting sometimes 6 impact points that represent one collision, 3 for one of the objects and 3 for the other. All the impacts are exactly the same except for the impulse attribute. So, I need to find a good way to filter this. I'd like to end up with just one point representing each collision, but I'm not sure how to achieve this. I tried writing a complex nested set of for loops to test for similar collisions, but it got complex and slow. The DOP Impact Analysis doesn't do what I want as I don't want to use a threshold to filter the impacts, I just always want the strongest impact. I'd really appreciate any tricks to deal with this.
  5. Getting servos working has been bugging me for a long time. I want to set exact rotation values for them rather than just setting motor forces. I finally got them working for both packed and unpacked geo. you can get the hip from here :- http://richardlord.tumblr.com/post/157323581986/hipfile-got-servos-working-using-both-normal-geo
  6. I missed the attribute reorient SOP. That works perfectly! Thanks Szymon!
  7. Thanks for the tip, but I'm not sure I understand this node and there are no example files in the help card. In this scene, I've created an attribute on a point, vector_to_transform. But when I update the pos in the deformation wrangle it doesn't change by the same amount. Also I'd have no idea how to compute rotation in this node. transform_attributes.hiplc
  8. Is there a way to transform other attributes in the way that the @P and @N attributes get transformed when I use the Transform or copy SOPS? I have a bunch of user attribs that i'd like to be transformed through the copy SOP. I can find hacky ways to update them, but i'm hoping there's a way I can make them just work. Thanks!
  9. Hmmm. Ok, you got me there. That does indeed do what I wanted! I missed it I think as the Transform SOP does it differently, and the Edit SOP's user page doesn't mention it at all. Nor do the quick start videos on editing points. The right click menus don't have the ' shortcut on it either, despite having all the other handle stuff (that I know of) Thanks for the tip! I'll try again and see if I can model as fast in Houdini as elsewhere. I would love to never have to leave. (edit - Oh dear. I just found that its a checkbox called attach to geometry..... Well, that was obscure to me at least.)
  10. I've been trying to model in Houdini and am finding its still not quite there. (unless I'm missing something of course.) All the new tools are excellent, but the inability to manipulate the pivot in the edit SOP like you can in the Transform SOP, make fast alignment a pain, and slow modelling down too much to make it viable just yet.
  11. Heres an example. This stuff is tricky to do in Houdini, but is really amazing once you wrap your head around it. I create a sphere in SOPS. Pack it and give it a unique name and velocity(v) Then, in DOPS, in a SOP Sover, I bring a new sphere in every so often using an Object Merge. In the same SOP Solver I build a constraint, name each point correctly and set all the attribs up correctly. They go out the OUT_CON null. Then I read that into the Constraint Network There's a million ways to do this, this is the method that works well for me, and has proved most flexible so far. 17_02_27_spawning_constraints_b.hiplc
  12. Oh, maybe you meant you want it to delete 5% each frame. If you want that, you just add in an @Frame attribute like this. rand(@ptnum) < @Frame * 0.05 delete_points_time.hiplc
  13. Yes, just write rand(@ptnum) < 0.05 in the expression field of a delete sop. Heres it is set up. delete_points.hiplc
  14. Atoms tip is great, works really well for packed geo. Also, you can set the PopSteerSeek's attraction type to Points, and pipe in a bunch of points with matching ids to your geo. Really powerful!
  15. Yes its working in H15. I'm not sure that I should share the file though as its partially built from a paid tutorial. I did a simpler version here though, one which doesn't use solvers. Because of that it updates realtime as you drag the bug around. It looks closer to the one you originally posted. It's less elegant than the solver based one, but it works not too bad. If you move the purple transform node - MOVE CREATURE, everything should update reasonably well. Adjust the values in the red node -CTRL, to get different leg lengths, strides, etc. 17_02_05_simple_walk_without_solver.hip