Jump to content
  1. General

    1. 26.4k
      posts
    2. 2.2k
      posts
    3. 1.6k
      posts
    4. Marketplace

      For all commercial tools, HDA's etc.

      438
      posts
  2. Houdini

    1. 65.8k
      posts
    2. 49.1k
      posts
    3. 12.3k
      posts
    4. 5k
      posts
    5. 15.2k
      posts
    6. 1.1k
      posts
    7. 698
      posts
    8. 708
      posts
  3. Coders Corner

    1. 6.3k
      posts
    2. 13.2k
      posts
    3. 4.8k
      posts
  4. Art and Challenges

    1. 3.5k
      posts
    2. 9.8k
      posts
    3. 572
      posts
    4. Effects Challenge Archive

      This is where the cool unofficial challenges live on!

      297
      posts
  5. Systems and Other Applications

    1. Other 3d Packages

      Maya,XSI,Blender,etc

      1.6k
      posts
    2. 1.5k
      posts
    3. Hardware

      Graphics cards etc.

      2.1k
      posts
    4. 422
      posts
  6. od|force

    1. 1.5k
      posts
  • Posts

    • Right, got it. Yep that's right! The reference goes twice over and under, I'll see if I can figure it out Thanks man
    • Sure, just sweep might be even better, then reference distance to ribbon width. But again, distance depends on angle and amount of twists, I would like not to overcomplicate this and just adjust based on look.  More fun is to make a next step in the pattern, as your reference has a bit more complex stitch with 2 shifts, not simple cross as I did.
    • Hey man! Trying to wrap my head around this, got a question for when you've got time. Why exactly do you go through all of that stuff before sweeping? Like measuring the distance between each point, calculating the cross product of the tangent and N, then reference that distance on the length of a line and use that as the cross section of a sweep node. To me it seems like just sweeping the lines and using the normals to orient them seem to do the same thing? I'm sure I'm missing something here but just trying to learn and understand your thinking
    • Getting a zoom blur or spin blur in a COP network means writing the same wrangle: work out the aspect-corrected @P coordinate space, build the radial sampling loop, use volumesamplep so alpha doesn’t drop. It’s 30 lines of boilerplate for a basic result. Zoom / Radial Blur COP is that node. Connect an image, pick a mode, done. Blur modes: Zoom Blur (radial scale streaks from center) or Radial Blur (spin/arc smear at constant radius) Center control: Screen Space (−1..1, 0 = image center) or Pixels (absolute coordinates, Y=0 at bottom-left) Samples: 1–256, slider with strict minimum — raise for finals, lower for layout speed Both modes share the same center controls. Switching modes hides the irrelevant parameter (Blur Pixels vs. Blur Angle). Alpha is preserved throughout via volumesamplep. docs and download: https://kleer001.github.io/funkworks/zoom_blur_cop [kleer001.github.io] Houdini 20.5+, any edition. FX users: a build script is included to compile the HDA clean under your own license. More free tools at FunkWorks Home [kleer001.github.io].
    • Damn that's beautiful, thank you so much Paul. Was still working on a few other methods but wasn't really able to figure it out still. Definitely going to study this setup :) Thanks again for taking the time
  • Topics

×
×
  • Create New...