Jump to content

woodenduck

Members
  • Content count

    341
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won

    2

woodenduck last won the day on June 16 2019

woodenduck had the most liked content!

Community Reputation

48 Excellent

1 Follower

About woodenduck

  • Rank
    Illusionist

Personal Information

  • Name
    Joe
  • Location
    Vancouver
  1. No dop object specified ?

    Just need to change your expression from opinput() to opinputpath(). The first returns just the name of the operator. The second returns the path to that operator. This particular parameter requires a path.
  2. No dop object specified ?

    Can you post a hip file or screen shot?
  3. No dop object specified ?

    DOP network - can be a path. Object Mask - Should be just the name of the dopobject. Not a path.
  4. pop wrangle plugged in to "particle velocity" on the flip solver... v@v *= fit(@Frame, 1, 24, 0, 1); This will multiply your velocity on a ramp from 0-1 between frames 1 and 24.
  5. Maya to Houdini Camera wrong?

    if you attach a null to the camera at obj level and scale it to 0.1, does that line up?
  6. RBD concave thin wall collisions not detected

    So you cached the abc then you read it back in to render? Is the geometry packed? Do you have the same problem if you unpack followed by normal sop?
  7. RBD concave thin wall collisions not detected

    Glad you got it working, and of course whatever gets the job done is great. However, I would encourage you to investigate using convex hulls for all collisions. You will see vast improvements in speed and stability. They can be a little trickier to set up, but the rewards more than worth it.
  8. RBD concave thin wall collisions not detected

    The blue collision object you are visualising... is that created using a static object dop? If so, are you visualising the "Collisions/RBD solver/Volume" tab rather than "Collisions/Bullet Data" tab??? I think you may not be seeing what the solver is seeing.
  9. If 'v' exists on the incoming points, the flip object should pick that up automatically. So however you set 'v' in sops, should be what you see in dops. Otherwise, you can grab the 'v' and plug it in to the 'particle velocity' (inout 2) on the flip solver. pop wrangle. Inputs tab. Input1 = First context geometry. v@v = point(0, "v", @ptnum);
  10. Vex course

    I usually point anyone looking to get started with VEX at Matt Estela's excellent wiki... http://www.tokeru.com/cgwiki/index.php?title=HoudiniVex
  11. in a wrangle. Plug static points in to input1 and animated points in to input2 @P = point(1, "P", @ptnum);
  12. For Each attribute

    If you post a hip file, I'm sure someone will help you out.
  13. For Each attribute

    You can assign any attribute, id's or anything you like inside a foreach with any of the usual tools. Wrangle, attribute sop, vop sop etc... What exactly are you trying to do? Do you have an example of it not working? Cheers, WD
  14. Packed RBD from Pop Sim

    You can treat your packed rbds the same way you would a particle system. Setup your rbd network and plug your pop nodes in to the post solve (3rd input) of the Rigid Body Solver.
  15. RBD doesn't take all geometry only the first one

    You sim is only generating geo on the first frame. You can set "creation frame" on you rbdPackedObject node to $FF to get it to keep adding more spheres, however, it won't just add the new spheres, it will add a new instance of every sphere on each frame. At Sop level you will need to delete the spheres that have already been added to the sim at each timestep.
×