8 Comments

  1. Ha! This is great! I was just working on something like this. Perfect timing! I was trying to do the remesh in the same network stream as the vellum solve. Thanks for showing how to split up the data into multiple streams.

    One thing I added was to subdivide the edge more with “adaptive” remesh. Just reverse the “growth” attribute with a min of 0.1 to “targetmeshsize” and then pipe that in to an adaptive remesh. Ends up giving you much more resolution on the edges where you need it. 🙂

    Wish I could post images.

    Thanks again!

    • Hey Scott, yes, this technique works quite fine! Especially if you only want to grow your geo up to a specific point and no further. You can add all your edge detail before simming and don’t have to worry about remeshing mid sim!

  2. … when you attribute transfer in sopsolver1 there is no ‘force’ attribute to transfer as far as I can see — am I missing something? Let me know – C

    • Hey Chris, this is more or less just for completionists sake. The setup I built in the tutorial has no force attrib since no external force is acting on the object. If you’re adding for example a gravity force to the sim, you get a force attrib as well.

  3. yes — would love to know how to run the solver “lightly” without the jumps…

  4. Yes! I would love to see a follow up with the adaptive subdivision. Bring on the vex!

  5. When I’m creating the vellumobject inside of the DOPNet the defualt path isn’t set to the input 1 and input 2. I’m in 19.0.455 if that has an impact. Is that some configuration that I need to change? Also I’m curious why u have to type in `opinputpath(“..”, 0)` with the apostrophes, looking in the Houdini documentation I can’t see any references to this https://www.sidefx.com/docs/houdini/expressions/opinputpath.html

    • Just confirmed that these presets are indeed missing in 19.0.455. Very odd choice by sidefx…
      In any case, the scene files are still working though, so if you’re having trouble, you can just copy this expression from there.
      The apostrophes are actually backticks and it’s the houdini way of saying “I want to write an expression inside a string field.” It’s used here not because of the expression itself, but because of the type of parameter field it’s written in.
      Cheers,
      Chris

Leave a Reply