A Guide to Time-Based Simulations with Blender Geometry Nodes Simulation Zone

What will you learn in this guide?

Simulation Zone in Blender Geometry Nodes lets you build systems that carry state between frames. This means the result in one frame can become an input to the next frame’s calculation. Simple rules can produce more complex results over time; physics simulations are a common example.

Rather than providing a ready-made node recipe for a specific physical effect, this guide explains how the simulation zone works and highlights important settings for production. You’ll learn how to think about the zone’s input and output, what the cache does during animation playback, and how to prepare the result for rendering frames out of order.

Requirements and limitations

You’ll need Blender’s Geometry Nodes system and simulation nodes. The Blender Manual states that these nodes can only be used in the Modifier context; they do not work in the Tool context. One of the source manuals is presented as the Blender 5.2 LTS manual, but the sources do not specify the minimum Blender version required for the documented functionality. Check version compatibility separately in the Blender installation you plan to use.

The sources do not explain any account requirements or hardware requirements for simulations. The basic setup for this guide is an object using Geometry Nodes and an animation context where you can change frames. The geometry and physics rules used in the simulation will vary by project; the sources do not provide a node recipe for a specific sample effect.

Setting up and editing a Simulation Zone

1. When you add a simulation in the Geometry Nodes editor, you get a zone made up of Simulation Input and Simulation Output nodes. The area between these two nodes is where the simulation steps are evaluated. The simulation result is passed outside the zone through Simulation Output.

2. Connect the starting geometry and initial values to Simulation Input. Values connected to this input are evaluated once at the beginning of the simulation and carried into the subsequent simulation state. This distinction helps you treat initial conditions separately from elements that are recalculated over time.

3. Place the node setup you want to change during the simulation steps inside the zone between the two nodes. Some elements connected from outside the zone to nodes within it are reevaluated at each step based on their values in that frame. Keep in mind, then, that data sampled once at the start behaves differently from data updated at every step.

4. Don’t try to pass connections inside the zone directly to the outside. The simulation result is accessed through Simulation Output. So explicitly handle the geometry or state data you need at the output using the zone’s input and output setup.

5. You can rename, reorder, or remove input sockets in the Geometry Nodes editor. To add new bake items, you can drag sockets to an empty socket or to the Simulation State panel. Rename sockets with Ctrl and a left-click, or through the node’s Properties panel.

Frames, Delta Time, and the cache

1. The simulation works with the animation system and is not evaluated unless the frame changes. To inspect the result, advance through frames on the timeline or play the animation. Like Blender’s existing physics simulations, it is cached during playback. The current cache is shown as a prominent purple line in the Timeline editor.

2. Treat the Delta Time input as the time in seconds between frames. According to the manual, this value corresponds to the inverse of the render frame rate. In setups that depend on frame rate, using Delta Time helps keep playback consistent if the frame rate changes. Not every node graph should be assumed to need Delta Time; this input is intended to drive node setups that depend on a rate of change.

3. The Skip option in the simulation zone disables the nodes inside it and passes the Simulation Input result directly to Simulation Output. This can be used when you want to skip the simulation calculation and pass the input through to the output. With Skip enabled, don’t expect operations inside the simulation to produce a result.

Baking for rendering

1. If only the result at the current frame matters, disabling the cache may reduce memory use. Consider this option when you don’t need to inspect previous frames or store the result for the entire animation. The sources do not specify what other performance characteristics of the simulation are affected when caching is disabled.

2. Bake the simulation to disk for a render farm job or any task where frames won’t be processed in order. Baking makes the simulation available for rendering out of order. However, note that baking for selected objects bakes all simulations in all modifiers on those objects; it is not limited to a single simulation zone.

Common mistakes

One of the most common misunderstandings is assuming that initial data connected to Simulation Input is refreshed every frame. Initial inputs are evaluated once, while some external connections within the zone are reevaluated at every step. Checking when a value is updated makes it easier to diagnose unexpected results.

Another mistake is trying to use simulation nodes in the Tool context or looking for the result somewhere other than Simulation Output. Also, anonymous attributes are not automatically carried through simulation nodes; anonymous attributes needed at a later stage must be explicitly stored in the simulation state. If you skip this requirement, the expected data may be missing in subsequent steps.

Finally, don’t expect the simulation to update without changing frames. It is evaluated as the animation advances. Before rendering, check the cache scope, other simulations on the selected objects, and whether you need to bake for rendering out of order.

Next steps

Start by inspecting the data flow between the input, the operations inside the zone, and the output in a simple test scene. Then advance through frames and observe which values remain fixed from the start and which are reevaluated at every step. If only the current frame matters, consider your cache settings; if different frames of the animation won’t be processed in order, bake to disk.

In architecture, interior design, and archviz workflows, this approach can help you test procedural simulation logic for changing geometry or moving systems. However, the sources do not provide specific architectural effect examples, performance measurements, or hardware requirements. Validate your scene’s needs with a small test, and check the cache, bake scope, and Blender version compatibility during production.

Sources and license

This guide has been adapted into Turkish from the “Simulation Zone” and “Simulation Nodes” pages in the Blender Manual. Both sources are licensed under CC BY-SA 4.0; the content has been adapted under the terms of this license.