Declare active/passive roles, collision shapes, physical parameters, frame range and approved cache location. Verify object scale and collision proxies before simulation.
Use blender-background-jobs with BAKE_POINT_CACHES for expensive baking. Query the terminal receipt, reopen the baked project, and check physical measurements plus visual behavior. Cache paths must stay inside the job directory.
Free or invalidate caches before parameter changes. Never auto-retry an interrupted bake, and do not require cross-device byte identity. Low-resolution fixtures prove the workflow, not film-quality fluid or cloth.
When to Use
Use when configuring rigid bodies, collisions, cloth, soft bodies, smoke, point caches, or fluid caches and requiring recoverable baking.
Prerequisites
- Clarify active/passive roles, collision shapes, physics parameters, frame range, units, proxies, and the approved cache directory.
- Apply or record object scale before baking, and confirm the cache space budget.
Workflow
Step 1. Check object roles, transforms, collision proxies, and dependency order.
Step 2. Validate parameters and direction with a low-resolution short interval.
Step 3. For expensive bakes, submit BAKE_POINT_CACHES background jobs and poll for terminal state.
Step 4. Release or invalidate old caches before parameter changes; mixing old results is prohibited.
Step 5. Reopen the bake project and complete physical measurements and visual review.
Validation and Delivery Evidence
Report simulation type, object roles, parameters, frame range, cache paths, job receipts, collision/penetration measurements, and first/middle/last previews.
Rules and Capability Boundaries (Inapplicable Scenarios)
Do not automatically retry interrupted bakes, and do not require byte consistency across devices; low-resolution fixtures only prove the workflow and do not represent cinematic-grade results.
Gotchas (Common Issues and Recovery)
- Penetration or explosion: check scale, collision margin, step count, and initial overlap.
- Stale cache: explicitly release before re-baking; do not overwrite caches of unknown origin.
- Background interruption: preserve terminal state and logs, and wait for an explicit resume.