Jump to content

kev2

Members
  • Content count

    190
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

Community Reputation

33 Excellent

About kev2

  • Rank
    Initiate

Personal Information

  • Name
    Kevin
  • Location
    Seattle

Recent Profile Visitors

3,608 profile views
  1. Normal Direction

    In yours, the normals are being calculated by subtracting the center of the object from the point position (@N=@P - (0,0,0)). Instead, you want to attach a Polyframe node, set the Style to First Edge, uncheck Normal Name and Tangent Name, check Bitangent Name and set to N. This will calculate the tangent as you expect. That will cause unexpected results with your end points so clean those up with a wrangle with the end point numbers in the group field: @N=normalize(@P-(0,0,0)); Since they're just vectors, you can also directly manipulate Normals in fun ways. Attached script has a simple example of the ever helpful lerp function and another one using the point function. It's a bit more involved as you'd need to loop that over an array of points to do multiple ponts. Hope it helps, Kevin Normals.hiplc
  2. New eGPU for Macs

    Yeah, it doesn't work out. The Apple tax is strong in this one.
  3. New eGPU for Macs

    At $700, I think I'll add one to my aged trash can Mac Pro and make it a home machine when the mythical upgradeable Mac Pro arrives.
  4. New eGPU for Macs

    https://www.theverge.com/circuitbreaker/2018/7/12/17563646/apple-blackmagic-external-gpu-price-release-date $699. No comment on the aesthetic
  5. LIDAR to Heightfields

    VolumeFromAttrib works pretty well. Thanks Illusionist. I also tried VDB route and tiaingulate2d (which I had forgotten about). VDB required a decent amount of fiddling but did a great job and roughly the same memory / time to process as VFA. Trianglate2D became unhappy after a couple millionish points so I didn't get anywhere with it.
  6. The help docs for the Terrains say that "Lidar Import can load LIDAR formats (for example e57) as height fields" but there's no option to convert to a HF that I can find? Am I missing something? http://www.sidefx.com/docs/houdini/model/heightfields.html Thanks, Kevin
  7. Re number of replies, your question isn't tips and tricks, it broadly covers entire departments and careers of CG artists. Integration is largely the domain of compositors but upstream a small army of people are dedicated to making it happen, from the on-set sup to the texture and materials artist to 3D artist to the compositor. Take a look at The Art and Science of Digital Compositing by Brinkmann and the VES Handbook of Visual Effects by VES. Great references. And there's a British Film Industry Visual Effects Foundations ebook running around that has a concise descriptioin of the skills involved.
  8. Houdini 17 Wishlist

    Oh, right, I remember that now, there was a guessing game about what they could be on odforce too I think. Thanks.
  9. Houdini 17 Wishlist

    I must have missed a news cycle. Where did you read this?
  10. Time Machine compositing node example?

    Thanks, Mark. I like the tattered effect you achieved. It might make a nice decaying effect. Did you mean first input or second above for the animated sequence? Using an animated noise etc in the second with small frame values works pretty well. Attached an example if anyone needs a starting point. heartOverlayhip.hiplc
  11. Anyone have a simple Time Machine node example? i think its a basic time warp but can't get it to work (also, I'm a newbie with Houdini's comp tools).
  12. Houdini 17 Wishlist

    Two buttons on each help page: Typo and Inaccurate, similar to the ❤️ button. You click the button and can highlight the text that is a typo or incorrect. Click the button again and the page submits it to the Docs team, effectively making all of us proofreaders. You could go all out and have a little comment box pop up too. Being too lazy to file a bug report unless things are crashing, I never do for typos or inaccuracies in the docs, which aren’t often in Houdini’s docs, but sometimes things change over versions and a line or two of a doc is made inaccurate, but would if it were just a click or two.
  13. What's kiling my particles?

    Thanks Jinguang, much appreciated.
  14. Houdini 17 Wishlist

    Nice tip. I never found copy stamping to be all that confusing but to be sure, the old for loop subnet business was really strange. The new For Loop blocks are powerful and I'm sure I'll get used to them but using fairly high level labels such as "metadata" and "feedback" to describe "Loop Information" and "Iterate On Top the Result of the Last Loop" might be concise but are so abstract as to be confusing.
×