Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won


j00ey last won the day on December 18 2017

j00ey had the most liked content!

Community Reputation

22 Excellent

1 Follower

About j00ey

  • Rank

Personal Information

  • Name
  • Location

Recent Profile Visitors

3,237 profile views
  1. If you specifically want to do it inside a for each, this will work (metadata must be plugged into second input): setpointgroup(0, sprintf("group_%i", int(detail(1, "iteration", 0))), @ptnum, 1, "set"); *edit : presuming you're using class as your piece attribute
  2. *Oops sorry, double post, mods - please delete
  3. Rotation per point.

    Ah, no you have to compute them. You can also do that with the PolyFrame SOP, I'm just in the habit of using a wrangle.
  4. Rotation per point.

    like this? copy_normalOrient_edit.hipnc
  5. Rotation per point.

    Here's one way - the switch toggles between using a normal pointing up and using the tangent of the path. Press play and you'll see they rotate around the normal. The offset parameter is just there to give you a way of rotating them differently along the length of the path. The curveu attribute that it's using for the offset is output by the second resample SOP. orient.hiplc
  6. Ps from what I can gather, chsetattr sets metadata attributes - I don't know what that means in depth but it's clearly not the same as normal channel data. In the attached file I write the channel data to an attribute called 'testval', then read it back. Perhaps there might be a way of storing all the sample data as a clip level attribute as an array, then manipulating it in a second wrangle..? From what I gather if you run a wrangle over channels or samples and input 0 only has 1 channel and 1 sample, that would be like running a SOP level wrangle in detail mode. I'm just thinking aloud, I'll give it a go when I get chance set_get_attrib.hiplc
  7. Do you specifically want to do this with a wrangle or do you just want to do it? Attached is a file that does what you're after but it's not done in a wrangle. I did try but they're still a bit of a dark art to me too, I will have another try when I get chance peaks and troughs.hiplc peaks and troughs.hiplc <-- updated
  8. New Year / New Showreel

    ...like I just got my hands on MS paint 3D! I'm re-rendering one of the clips atm, maybe I'll tone down the flickering a bit on the next version
  9. New Year / New Showreel

    @acey195 I took your advice and changed the beginning - probably more 80s looking than 90s now in fact but hopefully a bit more engaging. Thanks for the input, much appreciated.
  10. New Year / New Showreel

    Thanks for the comments - I did wonder about those bars actually, perhaps I should at least fade the video in under them a bit sooner. I'll have a think, don't want people to not watch it because of that...
  11. Distance from center in shops

    Does this do it? I got rid of the fit inside the shader so it's just outputting directly the distance from the centroid. I added a couple of image planes so you can check the result against an attribute calculated in SOPs. ShaderExample_edit.hip
  12. I've put a couple of examples of how to do this in the attached file. First way is using a solver SOP - that way is literally appending values to an array every n frames. The other method isn't technically appending values, it's just generating an array that gets longer every n frames. The advantage of doing it like that is that you can scrub the time line without having to cook the whole frame range. optical_with_circles_edit.hipnc
  13. HDA - Rope Maker

    Let me know if there's anything that doesn't work as it should..
  14. HDA - Rope Maker

    In case it's useful to anyone, here's an asset I made a little while ago and finally got round to documenting. It takes one or m ore curves and generates 3 levels of braided curves - first level coiled around the input, second coiled around the first and the third around the second. Additionally it can make a final level of 'hairs'. It supports animated inputs, and will transfer velocity onto the output but in many cases it's probably better to use a timeshift to generate the rope on 1 frame and use a point deform or similar. This also avoids texture jumping problems if using the supplied 'pattern' colour method. There's a fairly comprehensive help card with it and below is a demo video. If anyone finds bugs or problems, please let me know and I'll try and fix them when I have time... I'd be very interested to see anything anyone makes with it... TB__RopeMaker_1_0.hda
  15. New Year / New Showreel

    I wanted to share my new reel - mainly Houdini but there's are also a couple of older Maya clips on there too. Any feedback very welcome...