Blender Simulation Workflow

Read the shared execution guidance once per task for autonomous decisions, evidence cadence, and long-task continuity.

Simulation is a cache-producing build step. Preserve the setup and cache provenance; a visually plausible single frame is not proof that it is stable.

Define the simulation contract

Record the simulation type, solver, timeline, scale, gravity/forces, collision objects, emitters, domain bounds, desired behavior, cache location, resolution or substeps, and deliverable format. State the frames that establish onset, peak interaction, and settle. For fluids, explicitly distinguish liquid from gas/fire/smoke and whether a mesh, particles, or volume is the deliverable.

Use a project-local cache directory outside source control. Never overwrite an existing approved bake without creating a new output location or explicit user approval.