Mastering Blender Fluid Simulations: Foam, Moving Objects, and Mantaflow Physics

The first time I got a fluid sim working in Blender, I rendered out a cube of water falling into a cup, and I watched that animation loop for probably twenty minutes. It wasn’t even good. The water looked like jelly, the cup was the default cube with a bevel, and the foam was nonexistent. But there it was - physics, doing its thing. It’s a genuinely magical moment when the simulation starts working, and if you’ve never experienced it, this tutorial from Titanic Animations is a fantastic way to get there. It walks you through building a complete fluid simulation with foam particles and a moving obstacle, which sounds simple until you realize how many ways it can go wrong.

Blender’s Mantaflow system has a learning curve that feels intentionally designed to punish the impatient. The interface presents you with a clean, friendly panel labeled “Fluid” and then asks you to make a series of seemingly arbitrary decisions that will determine whether your simulation runs in ten minutes or explodes into twelve hours of baking hell. This tutorial handles that complexity by building incrementally - you start with a basic pool of water, add a funnel, make it move, then layer in foam particles once the foundation works. It respects your time enough to explain why things fail rather than just showing the happy path.

Setting Up the Simulation Foundation

The workflow starts with the classic default cube, scaled up to serve as your fluid domain. This invisible box defines the boundaries of your simulation, and everything that happens inside it - water splashing, foam scattering, obstacles moving - gets calculated within these walls. The presenter then duplicates this cube, flattens it, and tags it as the actual fluid object, creating the initial pool of water that your funnel will disturb.

The funnel itself is just a cylinder with some extrusions and rotations, but the magic happens when you keyframe its movement. Here’s the critical detail that trips up half the people trying this: you must check “Animated Mesh” in the obstacle settings. Without this checkbox, Blender treats your funnel like a static decoration regardless of how much it moves. The water passes right through it, or worse, behaves as if the object never moved at all. It’s a single checkbox, buried in a panel most people scroll past, and forgetting it destroys hours of work.

The tutorial also emphasizes starting position. Drop your moving object from slightly above the fluid surface, not from inside it. Starting inside creates simulation artifacts that will haunt your renders - weird splashes, impossible velocities, water behaving like it’s been personally offended. The presenter mentions this casually but it’s worth underlining: the physics solver needs to “discover” the collision, not resolve an object already violating its constraints.

Cache Management and the Cost of Quality

Anyone who’s baked a fluid simulation and then lost the data to a Blender crash has learned this lesson the hard way. The presenter dedicates real time to cache management, and honestly, it’s the most valuable section for anyone planning to do this more than once. You need dedicated folders for each simulation. Blender’s default temp directory will overwrite previous bakes without warning, and if your domain and particle objects point to different cache locations, your foam will render in completely the wrong positions.

The resolution settings deserve special attention because they scale non-linearly. The tutorial demonstrates this by baking first at resolution 65, then re-baking at 150 to show the difference in foam detail. What doesn’t get mentioned explicitly - but matters enormously - is how subdivision multiplies your bake time. Subdivision level 1 is standard. Level 3-4 can balloon a one-hour bake into twelve or fifteen hours. The presenter recommends staying below 3-4, which is conservative wisdom. Your computer thanks you.

There’s also a critical performance tip about previewing particle simulations. After baking, especially with foam particles active, do not try to play the simulation in real-time immediately. The presenter suggests reducing the display percentage in particle properties down to 10-50%. Your viewport will show fewer particles, but the full count still renders. Without this precaution, you’re inviting crashes, especially on machines that don’t have “really fast computer” status. The presenter acknowledges their hardware privilege here, which is refreshing.

Materials, Lighting, and Making Water Look Like Water

The shading section covers Eevee specifically, and if you’ve ever maxed out transmission on a fluid material only to get something that looks like colored oil, this part fixes that. The key settings: transmission at 1.0, IOR at 1.33 (correct for water), roughness at 0, and - this is what everyone skips - blend mode set to Alpha Blend. Without alpha blending, transmission creates that weird opaque look that screams “beginner fluid sim.”

You also need to enable screen-space refraction and translucency in the Eevee render settings. These aren’t on by default, and without them, your water won’t refract light properly or show the subtle translucency that sells the effect. The tutorial walks through these toggles methodically, which matters because scattered across three different panels, they’re easy to miss.

The lighting setup is a straightforward three-point rig: white key light, blue fill, yellow rim. It’s simple but effective, and the presenter notes that fluid sims respond dramatically to lighting changes. The way light catches the meniscus of splashing water, the caustic patterns underneath - these details make the difference between “technical demonstration” and “actually beautiful.”

Particle Foam and the Icosphere Replacement

The foam system uses a separate small cube tagged as Fluid > Particle with Floats enabled. By default, Blender renders these as halo particles, which look like cheap sparkles from 2003. The tutorial shows you how to replace them with an actual mesh - an ico-sphere in this case - which gives the foam volume and shadow-casting capability.

The process involves changing the particle render type from “Halo” to “Object,” then using the eyedropper to select your ico-sphere. Scale matters here. The presenter tunes the ico-sphere size until the foam looks like actual bubbles rather than floating gravel. It’s a small detail that makes an enormous difference in the final render.

Recommended Gear for This Tutorial

Watch the Tutorial

Level Up Your Blender Setup

Fluid simulation isn’t something you master in a weekend. There’s a reason professional VFX houses have dedicated departments for this stuff. But Blender’s Mantaflow system puts production-quality fluid physics within reach of anyone patient enough to learn its quirks. The difference between someone who gives up after their first bake crashes and someone who builds compelling fluid scenes usually comes down to this: understanding that the tool is picky, not broken. This tutorial gives you that understanding.

Start with a simple falling funnel. Get the cache management right. Watch your water splash and scatter foam. Then iterate. Higher resolution. Better materials. More complex obstacles. The physics engine doesn’t care how many times you re-bake - it’s just math, waiting for you to feed it better parameters. That first working simulation is addictive for a reason. Physics, doing its thing.