Blender Geometry Nodes Simulation Zone: A Step-by-Step Guide

What will you learn in this guide?

The Simulation Zone in Blender Geometry Nodes lets the state calculated in a previous animation frame carry over to the next step. This makes it possible to create procedural setups that change over time. Rather than prescribing a specific physical effect, this guide explains the boundaries of a simulation zone, how data moves through it, and what to check when preparing the result for production.

You’ll learn the roles of the Simulation Input and Simulation Output nodes, the difference between data supplied at the start and connections updated at each step, and how caching works during playback. The final section considers how to use these features in architectural visualization and animation workflows.

Requirements and scope

The source is the current Simulation Zone documentation in the Blender Manual. This guide doesn’t depend on a specific Blender version number, paid account, or hardware requirement; the source doesn’t specify requirements for these. If feature names or interface details differ in your version, check the documentation for that version.

Simulation Zone can be used in the Modifier context of Geometry Nodes; it isn’t supported in the Tool context. Since simulation works with the animation system, it’s evaluated when the animation frame changes. To inspect results, move between frames on the timeline.

When a simulation is added, the Simulation Input and Simulation Output nodes mark the start and end of the zone. Calculations inside the zone are reevaluated at each step, while some connections supply the simulation’s initial data. This distinction makes it important to plan which data is a fixed starting input and which needs to update over time.

Step-by-step workflow

1. Set up a Modifier for the simulation. Use the Geometry Nodes node tree in the Modifier context. The simulation area is defined by two boundary nodes: Simulation Input represents the start, and Simulation Output represents the result. The simulation result comes from this output node.

2. Define the initial data. Connect inputs the simulation needs at the start, such as geometry, on the Simulation Input side. These initial inputs are evaluated at the first step and passed into the simulation state; they aren’t automatically recalculated from scratch on subsequent frames. Don’t confuse initial data with a connection that needs to track changing frame values.

3. Place the time-dependent setup inside the zone. Build calculations that need to update as the frame advances in the area between Simulation Input and Simulation Output. Connections can enter from outside the area, but direct connections from inside the simulation zone to the outside aren’t allowed. Use Simulation Output to pass the result to other operations.

4. Review the data to be stored in the simulation state. Geometry is available as a default input. Additional bake items can be added by dragging them to the appropriate socket or through the Simulation State panel. Sockets can be renamed, reordered, or removed. To edit a socket’s name, Ctrl-click it with the left mouse button; you can also rename it from the node’s Properties panel.

   Simulation nodes don’t automatically carry anonymous attributes into the next state. Anonymous attributes needed in later steps must be explicitly stored in the simulation state. Decide in advance whether data is only needed for the current calculation or also for subsequent frames.

5. Check the time step and playback behavior. Delta Time gives the duration between frames in seconds and is the inverse of the render Frame Rate. In a speed-dependent setup, using this input can help keep playback consistent when the frame rate changes. Then move through frames on the timeline to observe how the setup progresses.

6. Decide how to handle caching and baking. The simulation is cached automatically during playback. The current cache is shown as a distinct purple line in the Timeline Editor, making it easier to inspect previously calculated frames. If only the current frame matters, turning off the Cache option can help reduce memory use.

   For rendering, the simulation can be baked to disk. This can support render workflows where frames aren’t processed in order. However, baking isn’t limited to a single simulation: it bakes simulations in all modifiers on selected objects. Before baking, check the selection and the simulations it includes.

Common pitfalls

Expecting the simulation to progress without changing frames: The simulation is evaluated when the animation frame changes. If the result isn’t updating, move to different frames on the timeline to check its behavior.

Ignoring the zone boundaries: Direct connections from inside a Simulation Zone to the outside aren’t allowed. Use the Simulation Output node if operations outside the zone need the result.

Treating initial input as live data: Initial data on the Simulation Input side is evaluated at the first step. For connections that should be recalculated as the frame changes, use connections that are reevaluated at each step inside the zone.

Assuming anonymous attributes will carry over: Explicitly store any required anonymous attributes in the simulation state. Otherwise, information needed in later steps may not be available in the simulation state.

Not checking the bake scope: Baking covers all modifier simulations on selected objects. Before baking, review which objects are selected and which simulations they contain.

Use in architecture, interior design, and archviz workflows

Simulation Zone can be useful for architects, interior designers, and visualization artists exploring Geometry Nodes animations that require state changes between frames. For example, it can be used to experiment with an animation setup where repeated elements change over time; the result depends on the node tree you build, and the source doesn’t prescribe a ready-made facade or landscape effect.

Subframe interpolation is supported for motion blur. The option to bake to disk can also be considered for render workflows that require frames to be processed out of order. Memory use, bake scope, and how the render process handles frames should all be factored into project planning. The sources don’t specify a particular GPU, hardware, cost, or compatibility with other software, so these points require separate verification.

Next steps

Start by comparing initial data with connections reevaluated at each step in a small Geometry Nodes setup. Advance through frames on the timeline and observe the cache line; then consider what disabling the Cache option means for memory use. Finally, check the selected objects and modifiers before baking. This lets you test simulation data, caching, and render preparation before moving to a larger scene.

Source and license

This guide was translated and adapted from the “Simulation Zone” documentation in the Blender Manual. The source is published under the CC BY-SA 4.0 license.