29-01-2020, 10:09 AM
(29-01-2020, 09:48 AM)josemendez Wrote: There's no notion of "lava", "water", or any specific material labels in Obi. It does not make sense to have those for fluids. Unlike granular materials, fluids are not discrete, but continuous materials that just happen to be approximated in a discrete way. Do not think of fluid particles as "drops", but "windows" into a continuous field: fluid properties are not only defined in the particles, but at any point in between them.
All material properties are copied to particles when they are emitted, and evolved during simulation. You can read fluid data (density, vorticity, or diffusion data) at any place and moment and act accordingly. Take for instance the ObiFoamGenerator component: it spawns diffuse particles in places where fluid density is low and vorticity is high. It doesn't use collisions to determine when particles "touch" each other.
In your case, you could give your particles a "temperature": there's four custom diffusion channels for each material, that you can use in any way you want. Make lava hot and water cool, and generate rocks when temperature is medium.
See the Raclette demo scene for an example of this: temperature is mapped to viscosity: hot->viscous, cool->inviscid. The fluid is initially cold, it falls on a hot plate, gets hot, melts, slides down and then touches a cold plate where it gets viscous again.
The FluidMixing demo also shows how to use the custom diffusion channels, this time mapped to particle color using the ObiFluidPropertyColorizer component.
Allocating memory at runtime (specially for large amounts of particles) is not recommended. Use a blueprint with the maximum amount of particles you expect to have in your scene. Blueprints act as particle pools, so only the particles actually emitted have any impact on performance.
Thank you, I understand, I worked in Houdini for several years, I just needed to know more details.