OutWit.Controller.Render.Model 1.4.0

Distributed rendering via Blender CLI and ffmpeg for .blend scene blobs, bootstrap typed-scene inputs, stills, tiled stills with overlap-aware tile options, runtime diagnostics, unified/frame/video/tiled preflight validation, frame sequences, and MP4 output. Persistent-batch frame distribution renders a node's whole contiguous frame chunk in a single Blender process via the command-line animation render (scene loaded once, GUI-free / macOS-safe) with per-engine chunk sizing; tiled stills render per-tile. Render nodes now materialize external scene dependencies (linked libraries, caches, volumes, …) from per-task attachment refs carried by Render.Split* (from the BuildBlendFromRefs sidecar) before rendering, so non-self-contained scenes render correctly across distributed nodes instead of only host-side. Per-frame baked-simulation caches (e.g. fluid/smoke OpenVDB sequences) are sliced per chunk so each node downloads only its frames' cache, and the validator admits a baked+attached fluid domain. Render.BakeSimulation bakes an unbaked Mantaflow fluid/smoke sim into a per-frame OpenVDB cache on a single node selected by Grid.Delegate (the fastest node by the same render-throughput benchmark used for distribution); the BakeAndRender{Still,Frames,Video}Cycles scripts then feed that baked scene through the proven build→slice→distribute→collect path so unbaked simulations render distributed end-to-end. The bake collects every produced cache file (gas/smoke OpenVDB density grids and liquid surface meshes alike), so both gas and liquid Mantaflow domains are supported. Non-fluid point-cache simulations (cloth, soft body, dynamic particles, dynamic paint, rigid body) are baked to memory and embedded in the baked .blend, so they travel self-contained to every render node. GPU device selection uses a smart fallback: if the auto-selected GPU backend crashes it tries the next available backend (OptiX→CUDA→HIP→Metal) before dropping to CPU, goes straight to CPU on a GPU out-of-memory failure (other backends share the same VRAM), and memoizes the node's known-good/bad backends so it does not re-crash on every frame.

Shared DCC scene-ref and validation data types used by the OutWit.Controller.Render.Dcc controller — host-side in adapters and consumed by the downstream Render controller.