Time-Based Setups with Blender Geometry Nodes Simulation Zone

What will you learn in this guide?

Simulation Zone in Blender Geometry Nodes lets you carry a result calculated in one frame into the next. This makes it possible to create procedural setups that retain and change their state as time progresses. In this guide, we’ll look at the simulation zone’s input and output logic, nodes that are evaluated again on every frame, the time step, and the difference between caching and baking. It’s aimed at users who want to experiment with repeating or moving geometry in architectural and interior visualization projects.

The key point is that Simulation Zone does not, by itself, produce a specific physical effect. It provides a zone that lets a previous state affect the next frame, along with a node setup that runs inside it. The Geometry Nodes manual also lists simulation nodes such as XPBD Solver and Cloth Dynamics, but this guide focuses on the general Simulation Zone workflow.

Requirements and things to know

• You need a Blender setup where you can work with Geometry Nodes, as well as an object to work on.

• Simulation Zone can only be used in the Modifier context; it cannot be used in the Tool context.

• Simulation is linked to the animation system. Evaluation occurs when the animation frame changes.

• The source manual does not specify a particular Blender version, account type, or hardware requirement. This guide therefore makes no assumptions about versions or system requirements.

Setting up Simulation Zone

1. Plan the simulation’s input and result. First, decide which geometry to use at the start and what data you want to change as the frames progress. In an architectural scene, this could be an experiment with geometry that moves through a space or changes position over time. This example does not mean that a specific physical behavior will occur automatically; that behavior is determined by your Geometry Nodes setup.

2. Create Simulation Zone. When you add a simulation zone to your Geometry Nodes setup, Blender creates Simulation Input and Simulation Output nodes to define its boundaries. The simulation result can only be accessed through Simulation Output. Arrange the calculations inside the zone so they lead to the output node.

3. Connect the starting data to the input. Inputs connected to Simulation Input are evaluated only at the beginning of the simulation; they are then carried into the next simulation state. Provide the starting geometry and initial state through this input. Some nodes outside the zone can be connected into it; these nodes are reevaluated at each step based on their values for that frame. However, because connections cannot be made out of the simulation zone, you must use Simulation Output to get the result.

4. Choose which elements to store in the simulation state. Geometry is the standard input available by default. When you need additional bake items, you can add sockets by dragging them into the empty socket area or the Simulation State panel. You can rename items by Ctrl-clicking the socket name with the left mouse button, or through the node’s Properties panel. Choose which data needs to be preserved for subsequent steps based on your setup’s requirements.

5. Place the per-frame nodes inside the zone. Nodes in the simulation zone run at every step and produce new results based on the values for each frame. This lets you build a processing chain between the starting geometry and subsequent states. This chain determines what the simulation does; adding the zone alone does not define a particular movement or physical effect.

6. Keep Delta Time in mind. Delta Time expresses the duration between frames in seconds. According to the manual, this value is essentially the inverse of the render Frame Rate and can be used to drive speed-dependent node setups. This helps keep simulation playback consistent when the frame rate changes. If your setup depends on the time step, use this input in your node setup.

7. Consider the Skip behavior if needed. The Skip option bypasses the nodes inside the zone and passes the Simulation Input output directly to Simulation Output. Whether to use this option depends on whether the simulation should be active in your setup; keep this behavior in mind when comparing it with the normal result.

Preview, cache, and bake

The simulation is cached automatically during playback. The current cache is shown as a distinct purple line in the Timeline Editor. This makes it possible to review previous frames quickly. If only the result of the current frame matters, you can disable the Cache option; the manual notes that this choice is intended to reduce memory usage.

Baking the simulation to disk when preparing a render allows frames to be processed in a non-sequential order. This matters for render processes that do not calculate frames sequentially. There’s also an important scope detail to keep in mind: baking applies to all simulations in all modifiers on the selected objects. Check the selected objects and relevant modifiers before starting the operation.

What changes in an architecture and visualization workflow?

Simulation Zone is a tool for architects, interior designers, and archviz artists who want to add procedural results that change over time to a scene. For example, it can be used to test a geometry setup that continues across frames in a presentation scene with a sense of motion. But the result depends on the node network inside the zone, not on the zone’s name. That’s why you should review both the initial state and the results at different frames before production.

For jobs going to a render farm, consider baking to disk; the need to process frames in a non-sequential order is one case where this option is useful. If memory usage is a concern, consider disabling Cache when only the current frame’s result is needed. The manual does not provide specific hardware, compatibility, or licensing requirements, so no definitive requirements can be inferred on those points. Previewing with your Blender setup and scene is the safest way to check before production.

Common mistakes

• Trying to use Simulation Zone in the Tool context: According to the manual, the node cannot be used in the Tool context; it works in the Modifier context.

• Confusing the starting input with nodes that run on every frame: Inputs connected to Input are evaluated at the start and carried into the simulation state; other nodes inside the zone are reevaluated at every step.

• Trying to get the result from outside the zone: The simulation result is available through Simulation Output; the inability to connect out of the zone makes this output especially important.

• Assuming anonymous attributes will be preserved automatically: Simulation nodes do not carry anonymous attributes unless they are explicitly stored in the simulation state. Explicitly store any data you need to retain.

• Overlooking the scope of baking: Baking includes simulations in all modifiers on the selected objects. Check your selection before starting.

Next steps

Start with a small setup that’s easy to review. Watch the purple cache line in the Timeline Editor during playback; then try disabling Cache or baking to disk only when needed. Before moving on to a more complex procedural simulation, verify the roles of the starting input, nodes reevaluated on each frame, and Simulation Output separately.

Sources and license

This guide has been translated and adapted from the “Simulation Zone” and “Geometry Nodes” pages of the Blender Manual. Both sources are published under the CC BY-SA 4.0 license.