Home Creators Posts Import Register Favorites Logout
haven't archived this post yet. have a subscription? use the importer!

Videos

Downloads

  • Volumes_101_Pt_25_Turbulize_Mushroom.zip

Missing 1 full-res photo, 1 file, as this post has not yet been imported.

Content

When this neat video popped up on Discord ( https://vimeo.com/255293329 ), I decided to give this technique a go. But this time relying purely on volumes.

What's happening in the original is this: In order to break up the symmetry of a basic smoke sim, points are scattered in the sim's high pressure areas. These points are then used to mask turbulence which is added to the simulation.

In this video we'll build a similar setup but without having to scatter points and using volumes only.

Files

Previews only

Volumes 101 pt. 25: Addendum - Smoke Sims: Controlling Turbulence To Add Detail

Comments

Alaadeen

why sometimes some nodes disappear like sourcevolume node I can't find it anywhere .

Dim Baidachnyi

Thanks! Really interesting and usefull technique! P.S. Fix the link please :)

Charles Vidaud

Thanks, nice technique, I never thought about using the Pressure Field actually, so far I was using the Velocity or the Temperature with a Gas Analysis in order to extract data like Curvature or Gradient to generate a mask for the Turbulence or the Disturbance.

entagma

Hi Saulo, yes that should absolutely be possible. Cheers, Mo

arian

hi thank you so much for your helpful tutorials. I wonder is there anyway to export the lines out of dopnet? I would really appreciate your help. Thank you.

entagma

Hi Arian, which lines exactly do you mean? Cheers, Mo

arian

Hi, Thank you for reply, In minute 12, the visualization turbulence shows some lines, inside the dopnet. in the gasturbulence node. is there any way to pipe these lines or import them out of dopnet? Thank you again.

arian

it used pyro simulation and then creating lines with volumetrail, but i cannot get the lines out of nodedop. and volumetrail does not exist in the nodedop. I would really appreciate your help and thank you so much.

entagma

Cool, really nice project to wrap your head around volumes and advection! Cheers, Mo

entagma

To access a field from a pyro sim in SOPs, use the dopimportfield-SOP. Select which field you'd like to import, then pipe that into a volumetrail-SOP. Cheers, Mo

arian

thank you so much for your help. I really appreciate it. Also can I ask what field should i use to get similar result as the dopnet? because i am importing Vel and Density and the end result is completly different from Dopnet. Thank you again and sorry for this many questions. Really appreciate your help.

entagma

Hi Arian, what you're visualizing there is an internal turbulence field which is created using noise, with its amplitude driven by the field you entered as control field. So you could create a noise field or a curl noise field in SOPs whose amplitude is driven by your turbmask field. You also might want to have a look at our free tut about creating a curl noise flow here: https://www.entagma.com/houdini-curl-noise-flow/ Cheers, Mo

arian

Thank you so much for your help. And really appreciate it. Finally I understood why they are different. Thank you.

Luis B

Hello Mo, after dealing with hundreds of sims in X-Particles / Turbulence FD, I'm enthusiastic by Houdini's speed and computing efficiency at simulating... nevertheless, it's super frustrating that each Houdini Version just redefine some nodes completely. The Volume Source Node from this Tut has nothing to do with the one you get in 18... It's simpler now, but The SOP to DOP Bindings are gone, and nothing shows up in the sim after binding the Isooffset node. Sometimes it's easy to understand how to overcome these version issues, but this got me stucked... Is there any change-tracker resource, where you can understand the changes and design decisions Side FX makes on every release?

entagma

Hi Luis, typically that'd be the release notes as well as the changelog: https://www.sidefx.com/changelog/ At least that's where we look when we're stumped by reworked/new nodes. On the upside we haven't yet come across a single reworked node that hasn't improved :) Wish I could tell you something else, but IMHO that's the advantage of Houdini's philosophy: Trust users to cope with node updates for the sake of being able to regularly update your underlying tech and getting rid of legacy workflows. (Although to be fair most older nodes are still there under the hood...) Cheers, Mo

Eric Sanderson

Did you find an answer to your particular SOP to DOP Bindings question? Im stuck on the same thing, the change log provided is a bit too dense to navigate, and searching for volume source keywords didnt yield what we're looking for. Update: Ah i see i was just hitting that volumesource node bug where you need to select out of source smoke and then back into it.