Jump to content

j00ey

Members
  • Content count

    205
  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by j00ey

  1. a sharing system in Houdini??

    I had a quick look at your scene, looks like it's more or less there. In terms of adding the energy transfer itself I'd do it as a post process - eg in the SOP solver you could group the points that are emitting and store the frame number when the transfer begins as an attribute, eg 'emit_start', then after the solver, for each point in the group add a point every frame for say 5 frames after emit_start and lerp the position between P and your tarpos attribute. over another 5 frames. That's probably a bit garbled. Basically I think it's easier not to add the points inside the solver, do it afterwards.
  2. 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
  3. *Oops sorry, double post, mods - please delete
  4. 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.
  5. Rotation per point.

    like this? copy_normalOrient_edit.hipnc
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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...
  11. 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.
  12. 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...
  13. 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
  14. 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
  15. HDA - Rope Maker

    Let me know if there's anything that doesn't work as it should..
  16. 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
  17. Some DOPs RnD

    Here's another experiment from a while ago, never got round to putting it up at the time. It never quite worked as I hoped it would - maybe I'll revisit it some time and somethihg better will come of it. It's quite a simple idea - run a flip sim of whatever sort and sample the velocity of a 2D slice onto a grid of points. Then in COPs, starting with an image consisting of 0 to 1 horizontal & vertical gradients in the red and green channels [representing u and v], look up the velocities and advect the uv. On the next frame, read in the advected image and repeat. This image sequence is then read back onto a grid and used as its uv. I started with an image of some pebbles, I wanted to smear them around with the velocity of the FLIP sim but the shapes were already quite blobby and amorphous so the effect was too subtle. Had I run the sim for many more frames they it might have worked btter but I decided to switch to some more geometric shapes. As I said it never really went anywhere but in case anyone's interested in the technique I thought I'd put it up...
  18. Some DOPs RnD

    I thought I'd make a topic here to share some RnD I've been doing in spare time in case it's helpful to anyone, as I've been able to learn so much useful knowledge from others on here. I have a couple of other scenes underway that I'll put up once they're ready. They're not for any particular shot, more just the result of one thing leading to another... The first one is essentially a simple cloth sim a driven by an RBD sim, where some balls are attracted to a wandering point. I used a technique similar to generating a wet map to transfer some colour between the balls while they're touching which sort-of worked but ended up producing a lot more blue than anything else. Also for each point on the surface I calculate the difference between the average distance to neighbouring points during the animation and at the beginning, a sort of compression or stretch attribute and I'm using that to displace the surface first in SOPs, then also in the shader.
  19. 16.5 drums

    Oh great, I kept meaning to put persistent quickmarks on the H17 wishlist... someone must have done it for me
  20. 16.5 drums

    It appears to be out...
  21. Some DOPs RnD

    Thanks! I love the stuff you've been posting on here too - fantastic work!
  22. I figured this out, i guess I must have figured it out last time and just forgotten... I made a scene file in case it's useful to anyone. The pc file needs to go in a 'cache' subdirectory of wherever you download the scene to, ie $HIP/cache/butterfly_pts.pc butterfly_pts.pc displacement_pcLookup.hip
  23. Has something changed with the new H16 mat way of doing displacement that would cause problems with point cloud lookups? I have a shader [a modified classic shader] in which I'm looking up a point cloud to get some wetness and colour attributes and it works fine without displacement. As soon as I switch that part on though, all the wetness etc vanishes. I'm sure when I've done this before it just worked but I'm clearly missing something. I'm transforming global P from current to object space to do the pc lookup, I don't recall having to do any compensation there for the fact that the geo is displaced. Does anyone have any pointers..?
  24. Hi I'm having a problem with a cone twist constraint network. I'm setting all the axes per constraint in SOPs (goal_twist_axis, constrained_twist_axis etc) and I wanted to set the motor_target values inside a SOP solver in my DOP network but it's just not doing anything. I can set motor_enabled and that works fine. I've tried v@motor_target, v@motor_targetr, f@motor_targetry, nothing gets picked up. I can't find anything in the docs or online... Any ideas?
  25. Ah yes thanks! I was looking at the Geometry but of course until you set a value manually, there's nothing there. Much appreciated.
×