Jump to content

Leaderboard


Popular Content

Showing most liked content on 10/31/2018 in all areas

  1. 1 point
  2. 1 point
    Be careful calling this method, on hires geometry, you can waste a lot of memory allocating a large tuple of Prim data.
  3. 1 point
    @ejr32123 Amazing. Thanks so much. I did get it to work but was using the old nodes today...! I really appreciate your time.
  4. 1 point
    I just had a chance to take a look. It's almost identical to how you would do it in h16, just with new sourcing nodes. They have the same presets. I literally just followed Atom's tutorial just changing the for the new sourcing nodes that h17 has. I hope this is helpful, GL flip_fill.hiplc
  5. 1 point
    haha, no worries! Well, it might seem like magic for you now - but with a few years using Houdini processes like this become as standard as creating a sphere But back to topic: why the timeshift? Some of the following stuff you might already know, but anyway.. The SOP solver is actually a dopnet => simulation, as you probably know or have guessed from the 'reset Simulation' button. Simulations depend on the data from the previous Frame (or more general: previous timestep). So if you feed the solver a geometry with changing pointcount (as in my file), the Solver just takes what he gets from the first input on the first frame of the simulation. It has no idea that on the next frame there are more points in the first input because on that frame it works only with the data it already has (which is what it got on the start frame). This is why I'm using the timeshift. The idea is to set it to the frame where all the data is available (if you dont kill any particles that would be the last frame of your sim). For demonstration I just decided to take frame 50 and have that as my data that the solver should operate on. (so frame 1000 should work..) Let's call it static data - so input 1 wants to have static data or it will take 'a copy' of the dynamic data on the start frame of the sim and by making 'a copy' of that data on that frame is becomes static. To get the actual motion of the particles back, I update the static data from 'previous frame' with dynamic data fetched from input 2. Oh and my coffe is currently Puro Fairtrade Coffee
  6. 1 point
    Sure. Not sure how well it can be recreated in H17.
  7. 1 point
    Inflation based on normals - don't know how well it will play with more complicated geo. Inflation_Normals_V1.hip
  8. 1 point
    Nice work. I'm just a bit suprised that you are charging $150 for 101 minutes (6+4+12+21+10+9+15+4)? I have a free talk that i gave at siggraph you may wanna check it out.
  9. 1 point
    In the dop i/o sop, you can check out "Compute Min/Max Values", which will create a couple of extra primitive attributes. Alternatively, you can see the same values in the intrinsics of each field. volumeavgvalue, volumemaxvalue, volumeminvalue are all good ones.
×