Skip to main content

Wire solver and wire deformer.

Just playing around with the wire solver and deforming wires onto wires...



rendered as tube primitives, 2 area lights and an env light, took about an hour to render 2K :/

hipnc is here

Comments

  1. Dan WillsSeptember 5, 2009 at 9:28 PM

    That looks totally flipping wicked Sam! :) very useful indeed!

    ReplyDelete
  2. SamSeptember 6, 2009 at 12:00 AM

    The wire deformer is great!

    ReplyDelete
  3. UnknownSeptember 6, 2009 at 5:18 PM

    where's the vimeo?
    :D
    looking wicked.

    ReplyDelete
  4. samiamSeptember 30, 2009 at 6:27 PM

    I like this more than a lot!

    noice one sam

    ReplyDelete
  5. sardoAugust 31, 2012 at 5:13 PM

    hey sam i am having problems opening this file am i doing something wrong ?

    ReplyDelete
  6. SamAugust 31, 2012 at 5:23 PM

    It is quite an old file, I have opened it in H12 but there are a lot of warnings.

    I don't have a PC at the moment, so I can't update it to H12 yet :/

    ReplyDelete
  7. sardoSeptember 2, 2012 at 5:31 AM

    oh ok sorry to hear that, well i hope to see more post from you wen u do i really enjoy ur work ..maybe u might be able to upload it some other time :-)

    ReplyDelete
  8. Milos PejakSeptember 2, 2012 at 2:51 PM

    Hi Sam

    I opened your hip and have a question. how are you getting the tappered/funnel shape for your vortexforce? did you touch anything in the vortexforcreatatrib? I typed bezier() in radius but nothing has changed.

    ReplyDelete
  9. SamSeptember 2, 2012 at 3:28 PM

    Bezier() in an expression means the parm is key framed, shift-RMB on the parm to open the channel editor... I think the radius parm has time mapped along the length of the curve so frame 1 is the start of the line and frame 100 is the end ... maybe!

    ReplyDelete
  10. Milos PejakSeptember 2, 2012 at 5:54 PM

    haahaha thanks man ive been messing with it all day. thanks for clearing that up. Its actually frame 10.

    impressive after 3 years this post is acquiring a bit of traffic.

    Thank you again.

    ReplyDelete

Post a Comment

Popular posts from this blog

Cloth tear geometry and shading detail

Been adding geo detail to the torn cloth and shading the additional geo. Shading sure is fun! :) Thickness added to the cloth geo Extrude sides are extruded out again  The second extrusion is done twice, once for the U direction, and once for the V direction. Polyframe is used to get the UV gradient to extrude along, vopsops are used to move the extrudeFront points after extrusion as you can't control the extrusion per point with just a polyExtrude node... The extrusion is done twice so that the two different surfaces represent the opposing thread directions. since my geometry (and therefore tears) are in line with the U and V direction, the effect is not obvious in this case. The extra geo after shading The .hip file below has a slightly newer shader than in the video and the image above, I removed the part of the shader that created the soft ramp for the alpha edge and used just the thread noise instead; it now looks more like: Slightly newer shader than...
6 comments
Read more

Wire to RBD feedback in DOPs

Normally if a wire is constrained to an RBD, the rbd isn't affected by the wire at all. Which is annoying ... but I had an idea to get it to work. the wire solver can store the internal forces on the geometry. In DOPs I made a point force, the position is set to the position of the constraint and the force is the wire's internal (linear) force. I have put a sopnet in the dopnet to get the wire and the constrained point so I can reference them in the point force. It could be simpler with a python expression to get the position and force directly without going through the sopnet, but this is just a little test... For multiple attachment points, I think a copy data node could be used to copy the point force data for each constrained point ... hip file here Wire to RBD feedback forces from Sam Hancock on Vimeo .
5 comments
Read more

Worm locomotion with FEM

I have always wanted to do a dynamic locomotion setup, I have tried in the past with wire and sop solver with .... interesting results ;) With FEM in Houdini 13, the rest attribute is stored on vertices which allows a tetra to change its rest state independently of the surrounding tetras. With this, parts can be expanded and shrunk to get a muscle type action. I have started with a worm since it is quite simple, the contractions and expansions move back along the worm in a wave, opposing the travel direction. It took quite a bit of tweaking to get him moving at all. One major element of a real worm's action that's missing is the little hairs that grip the ground. I couldn't find a way to change the friction per point so I have gone a bit hacky and multed down v wherever I didn't want the worm to move. I would love to hear if there is a per point friction control! Here is the video Houdini 13 FEM Worm locomotion from Sam Hancock on Vimeo . ...and the .hip is...
12 comments
Read more