eetu

There must be many many ways of doing this, but one is creating your v attribute in the parented sphere, and then bringing it into your source with an Object Merge set to Transform Into This Object. This transforms the v attribute, which then gets sourced into the sim. Otherwise this is just the basic billowy smoke shelf setup. ee_local_emit_direction.hiplc

What an inspirational thread! Great work, thanks for sharing

Oh wow, cool! Best of luck on your endeavor!

Hi! it's been a while since I did it, now looking at the hip I don't really seem to match the IDs, that is correct As it is, it works when new particles are added, but not if some particles are deleted. If you delete particles you would indeed need to to enable the Attribute to Match in Attribute Copy SOP. Although, as the system uses the last frame to copy attributes from, if you are deleting particles along the way, they will not exist in the last frame and their state is in that way undefined earlier in the animation..

Just a minor side note, instead of projecting/gluing/sliding points onto curves with uvs, I often just use an animated Carve SOP in extract mode to get a point out of the curve. Quicker for simple setups, but might end up needing some looping so can be less efficient for larger setups.

One übershader I built quite some time ago had the major photoshop blend modes between layers. At some point I extracted the combine block for someone, I'm not in front of Houdini but it should be in the attached file ee_combineblock.hip

Check this out

Here's another example with variable viscosity flip,

Up to and including, depending on the renderer

More and more studios write their own pathtracer. Vectorization is key these days. Pretty much everybody also has/uses a denoiser. Time to have one for Mantra? Dark beer is the next big thing after IPA. edit: Oh, and of course deep learning is making all sorts of inroads into the 3d world.

Hey folks, I suppose many of you will be attending Siggraph in a couple of days. Any suggestions for extra-curricular activities? Party invites? I know there is the LA Houdini User Group party, where I expect to run into some of you fine people - anything else one should not miss?

Well, yes and no. It's a field in the flip solver so you can vary it by voxel, like Dave/Pazuzu did above. Conceptually I would regard it to be closer to an attribute than a parameter, even though you would need a spoonful of extra noodle soup to source it from a point attribute. The name is surfacepressure not surfacetension, but don't let it fool ya ;)

You can always copy the detail attribute to each point/prim for visualization..

Just make a parameter for the value, and link the parameter to the chop outside the shader itself.

Also for a bit of a shorthand: http://www.sidefx.com/docs/houdini/vex/functions/ow_space http://www.sidefx.com/docs/houdini/vex/functions/wo_space