Baking Simulation Zone State in Blender Geometry Nodes for Reliable Renders

Problem: Simulation zones reset on file reload

When you build a Geometry Nodes tree that includes a Simulation Zone, the solver runs each frame and stores its internal state only while the current Blender session is alive. Close the file, reopen it, or send the scene to a render farm and the simulation starts from frame 0 again. This makes any animation that depends on accumulated motion—like falling particles, growing vines, or custom physics—unreliable unless you take an extra step.

How simulation zones store state

A Simulation Zone behaves like a tiny time‑stepping loop inside the node graph. Each iteration writes to attributes that are marked as “simulation attributes” (for example, velocity or age). Those attributes live in the zone’s internal cache, not in the regular attribute domain of the mesh. Because the cache is not part of the .blend file, it disappears when the file is saved and reloaded.

Worked example: baking a falling‑particle system

We’ll create a simple particle emitter, let the particles fall under gravity inside a Simulation Zone, and then bake the zone so the motion persists across sessions.

1. Add a UV Sphere, shift‑right‑click → Add → Geometry Nodes Modifier and click New to create a node tree.
2. In the node editor, add a Point Distribute node (domain = Point) to scatter 10 000 points over the sphere.
3. Add a Simulation Zone node. Connect the Geometry output of Point Distribute to the zone’s Geometry input.
4. Inside the zone, add an Attribute Statistic node set to Average on the position attribute to get the centre (optional).
5. Add a Vector Math node (operation = Subtract) to compute position - centre, then a Vector Math node (operation = Scale) multiplying by a small delta time value to get velocity.
6. Add an Attribute Store node to write the resulting vector to a new attribute called velocity (domain = Point).
7. Add another Vector Math node (operation = Add) to update position with velocity * delta time, storing back to position.
8. Add a Float Math node (operation = Add) to increment an age attribute each frame.
9. Leave the Simulation Zone and connect its Geometry output to a Point Instance node that installs a small ico‑sphere as the particle visual.
10. Connect the Point Instance output to the Group Output node.
11. Play the animation; you should see particles drifting outward from the sphere.
12. To bake, select the Geometry Nodes modifier, click the Bake button that appears in the modifier panel when a Simulation Zone is present. Choose a cache folder, set the frame range (e.g., 1‑250), and click Bake Simulation. Blender will write binary cache files to disk.
13. Save the .blend file, close it, and reopen. The particles now follow the baked trajectories without recomputing the simulation each frame.

Trade‑off: bake time vs. reproducibility

Baking a Simulation Zone turns a cheap, on‑the‑fly evaluation into a pre‑computed cache. The upside is deterministic output that works identically on any machine or render farm. The downside is the extra disk space and the time required to run the bake before you can render. For quick look‑development you may keep the zone unbaked; for final assets or shots that must be reproducible, baking is the safer engineering choice.

Actionable checklist

• When a Geometry Nodes tree contains a Simulation Zone, always verify whether you need baked state.
• Use the modifier’s Bake button (or bpy.ops.object.geometry_nodes_bake via Python) to cache the simulation to disk.
• Store the cache path relative to the blend file so the project stays portable.
• After baking, disable the Simulation Zone’s live evaluation (uncheck Enable Simulation) to avoid double work.
• Check the Statistics overlay (Window → Toggle System Console or the overlay in the 3D View) to confirm that the triangle count matches the baked cache and not the live solver.
• If you cannot bake (e.g., you need real‑time interaction), store critical simulation data as named attributes with the Store Named Attribute node and read them back after the zone.