Welcome to od|forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

  • Days Won


Pazuzu last won the day on May 4

Pazuzu had the most liked content!

Community Reputation

167 Excellent

About Pazuzu

  • Rank
  • Birthday 02/25/1981

Contact Methods

  • Skype

Personal Information

  • Name
    Alejandro Echeverry
  • Location
    Bogota - Colombia

Recent Profile Visitors

9,390 profile views
  1. I think doing this is not correct @Cd.x *= decay_val * @TimeInc; Do the math and you will have almost no value to work with; Its better that you subtract and apply a maximum or a clamp after the decay.
  2. Hey Alvaro, Here is a bit over-complicated setup using a vector field to define the id masks, but you can use also scalar fields directly. In this setup I'm using the id masks ( aka source A, sourceB ) to affect dissipation and turbulence for each source, please look into those "shapers" in the pyro solver. I hope this helps you! Cheers! Alejandro multi.pyro.v1a.hiplc
  3. You can use an id mask, so this mask should be advected / transported exactly the same as density, this way you can use it to mask whatever filter/effect you want.
  4. You are using a custom expression in the group parameter of the delete sop to filter each piece; So you must edit that expression using spare inputs for the dependencies to work correctly in a compile block. Cheers, Alejandro
  5. Hey, For this to work, you need to fix the expression dependencies in the group parameter for the delete SOP with spare inputs for the compile block to work correctly Cheers, Alejandro
  6. Hey Alvaro! You need to reset each piece xform first before the copy! Cheers Alejandro copy.fragments.to.particles.v2_FIX.hiplc
  7. Nice to hear that!! Cheers! Alejandro
  8. Hey Michel! Is this what you are looking for? Cheers!! Alejandro colli_ig_fail_1.hip
  9. Unfortunately that's one of the limitations of the FLIP method, the volume loss. As Andrew said a particle separation can help to cont-rarest the volume loss on the system. You can try also to apply some drag forces as soon as the fluid start to settle with some speed or pressure conditions, but that can kill a bit the nice momentum. For this kind of FX I really miss SPH, but its so slow; So in my case I come around to this problem using a mix between PBD and FLIP/PIC in my microtension tools, this way the volume loss is less noticeable, but still not as good as the SPH method, I really hope that SESI update some of the SPH microsolvers some day!. I hope that this helps you! Cheers! Alejandro
  10. Hi, Here is an approach to accumulate scatter using a for block, I know that is a bit cumbersome, but maybe there is a much better way. Cheers! Alejandro scatterAcum.hip
  11. Yes, its just a static mask, because the field is overridden on every timestep as the relationship is active, but you can use that mask to source into a dynamic field (Density, Divergence, Temperature, Fuel, etc). Cheers! Alejandro
  12. If you want to find even more details of the amazing surfacepressure implementation in the FLIP solver, look at the second edition of the "Fluid Simulation For Computer Graphics" book!! Is amazing!!! Cheers! Alejandro
  13. The Smoke object is just the container of data (In DOPs is very important that you have a container where all the data will be for DOPs to process) that contains all the necessary fields that the smoke/pyro solver will use to make the sim evolve by the DOPs engine. In the file you will find two main colors to identify the relationship type, there are two in this case, a source relationship (green) and a sink relationship (red). So all the colored nodes makes each relationship works, for example for the source one, you need a merge DOP that will define the type or relationship as a source, then you need the object to generate the mask from (sphere) and finally the microsolver that will generate the mask field for your relationship (gasbuildrelationship__source). Regards the "reference field density", is a parameter of the node to generate the mask as a "fog" field, by default the node creates SDF representations. Cheers! Alejandro
  14. This microsolver helps you to define a field mask using standard DOPs relationships (using the merge DOP for example). You can define for example a source object mask to emit fuel or density using just relationships, so if you have many objects and connect those besides the smoke solver with a merge using source relationship mode, the gasbuildrelationshipmask will create a field representing the objects as a fog or SDF representation. Attached is an example file (one hip is better that a thousand words ) Cheers Alejandro gasbuildrelationshipmask.hip
  15. Ohhh Man I don't think so!! So much to learn still! DOP context is like a black Hole full of Chaos and Alternate Possibilities! Cheers!!