
🎨 3D Rendering & VFX · State Machine
The states of a render job on a render farm: submitted, queued, rendering frame by frame, failures and retries, and completion.
Drawing diagram…
State machine for a render job: Submitted, Queued by priority, Rendering (frames distributed to nodes), Suspended by the artist and Resumed, Frames Failed triggering automatic retry up to 3 times, then Failed if still failing. When all frames finish it goes to Completed, then Delivered after output checks (missing or black frames).
stateDiagram-v2 [*] --> Submitted Submitted --> Queued: By priority Queued --> Rendering: Nodes available Rendering --> Suspended: Artist pauses Suspended --> Queued: Resume Rendering --> FramesFailed: Frame errors FramesFailed --> Rendering: Auto-retry (max 3) FramesFailed --> Failed: Still failing Failed --> Queued: Artist requeues Rendering --> Completed: All frames done Completed --> OutputCheck OutputCheck --> Delivered: No missing or black frames OutputCheck --> Queued: Re-render bad frames Delivered --> [*]
Where each part of a cloud render farm runs: artists' workstations, the render queue manager, autoscaling GPU render nodes and shared storage.
How assets move through a 3D animation or VFX pipeline: modelling, texturing, rigging, animation, lighting, rendering and compositing, with review in between.
A schema for managing 3D assets in a studio: projects, assets, versions, dependencies (textures, rigs), shots and reviews.
How a VFX shot is reviewed: the artist submits a version, the supervisor reviews in dailies, the client approves, and notes flow back.
The studio systems that tie a VFX pipeline together: production tracking, asset management, render farm, storage and client review.
The steps a VFX shot goes through from plates to final delivery: matchmove, modelling, animation, FX, lighting and comp.