wick3dParticle

Your particle ID's are unique. Just like a social security number, they should not be switching when a particle dies. Check your system again. ~Ilan

Thanks Rayman. Yes, that's what I have been using. ~Ilan

Ah, got it. I think I misread the original post. Thanks Pradeep! ~Ilan

Hi Haggi, I was wondering if you could share that file with us. I was under the impression that you can't run Houdini expression language in wrangle nodes, and that you were limited only to VEX. I would love to learn how you got that to work. I have tried using expressions like centroid() in the past, but remember getting errors due to that. Thanks, Ilan

I just wanted to add that in order to visualize your entire area of influence, you can visualize it as smoke or uncheck the 'use plane' option in the visualization tab below. The size of the area of influence depends on sample distance of your stamp points, in the tab next to visualization. Here's another example, ~Ilan IGtangVel2.hipnc

Since I don't know what your setup is, I am going to assume based off of your description that you did something like this: create a curve, add normals with a point sop, convert to volume using fluid source, using 'N' to drive the Vel volume. One way to get a velocity volume to flow with a curve is to create normals that follow the curve's tangents. A quick and easy way to do this is drop a polyframe sop, and set it normal name to something like 'normal', and tangent name to 'N'. Now when you source your Vel volume from 'N', it will follow the tangent normals that you created. I'll attach an example, Ilan IGtangVel.hipnc

Good Call Tomas! ~Ilan

Not sure I understand the question. Seems like you are looking to copy/paste your dopnet, but that sounds too easy of a solution for you to be posting here. ~Ilan

Hi Sonppw, To my knowledge there is no voxel expression. With that being said, you can generate a volume from attributes. Look at the Volume From Attrib sop node. ~Ilan

Hi PatW, I think you can just set a dop field as one of the vop inputs using the op: expression. From the help: You can now use the op: path syntax to refer to DOP data. For example op:/obj/AutoDopNetwork:0/Geometry references the Geometry data in the first DOP object in the AutoDopNetwork object. The second : (colon) character separates the node path from the DOP data path. Hope this is what you were looking for, ~Ilan

Hi Frez, A simple way to go about instancing lights is using the object level 'instance' node. Just object-merge your curve inside the instance node or create it directly inside the node. Make sure you point to your light under the instance tab. You can vary your instance attributes such as intensity or color using the instancepoint() expression. I'll attach an example. ~Ilan IGinstanceLights.hipnc

Hello world; It's fairly straight forward. If you create a pyro sim from a shelf tool, just select the geometry network that imports your pyro fields back to sops, and use the volume light shelf tool. It uses a volume shader and a geometry object (your pyro geometry) and renders light using the two. Hope that helps, Ilan

Hi Harima, This last Siggraph, I participated in a talk with some of my colleagues about directable fluids - Directable fluids in the world of epic At Blue Sky we have a proprietary procedural trajectory rig that we use in conjunction with a flip tank to create directable crown splashes. While I can't share with you the trajectory aspect of the setup, I can show you how to integrate something like a POP sim that mimics a crown splash in to your Flip sim. The end result is something more controllable. Keep in mind, this is a quick low-res example, but it will get the idea across. Best of luck, Ilan IGcrownSplash.hipnc

Wow, came out really nice!

Thanks Guys. Kim - I tried plugging in an empty dop object and pointing to the geo I wanted to tear in the cloth configure. I set up fracturing, but it appears that there is just no integration for tearing cloth in the finite element solver. Thanks, Ilan