
π¨ 3D Rendering & VFX Β· Data Flow
How assets move through a 3D animation or VFX pipeline: modelling, texturing, rigging, animation, lighting, rendering and compositing, with review in between.
Opening a template is free and never counts toward your daily diagrams. Asking the AI to change it counts as one.
Drawing diagramβ¦
Data flow for a 3D production pipeline: concept art goes to modelling, models go to texturing and rigging, rigged characters go to animation, animated scenes go to lighting, lit scenes are rendered into passes (beauty, shadows, reflections), passes are composited into the final shot. Every department publishes versions to an asset management system (ShotGrid) and supervisors review them in dailies; notes flow back to the department.
flowchart LR
subgraph EXT ["External entities"]
art["Concept Artists"]
sup["Supervisors"]
edit["Editorial and Delivery"]
end
subgraph PROC ["Processes"]
p1("1.0 Model assets")
p2("2.0 Texture and rig")
p3("3.0 Animate scenes")
p4("4.0 Light scenes")
p5("5.0 Render passes")
p6("6.0 Composite shots")
p7("7.0 Review in dailies")
end
subgraph STORE ["Data stores"]
d1[("D1 Asset Manager (ShotGrid)")]
d2[("D2 Render Pass Storage")]
end
art -->|"Concept designs"| p1
p1 -->|"Meshes"| p2
p2 -->|"Rigged characters"| p3
p2 -->|"Materials and textures"| p4
p3 -->|"Animated scenes"| p4
p4 -->|"Lit scenes"| p5
p5 -->|"Beauty, shadow and reflection passes"| d2
d2 -->|"Render passes"| p6
p6 -->|"Final frames"| edit
p1 -->|"Published model versions"| d1
p3 -->|"Published animation versions"| d1
p6 -->|"Published comp versions"| d1
d1 -->|"Versions for review"| p7
p7 -->|"Dailies playlist"| sup
sup -->|"Notes"| p7
p7 -->|"Animation notes"| p3
p7 -->|"Lighting notes"| p4A data flow diagram with 10 processes and outside parties, 2 data stores and 17 data flows.
Describe your own system in plain English and CloudSketch AI draws it in seconds. See all AI diagram generators.
Where each part of a cloud render farm runs: artists' workstations, the render queue manager, autoscaling GPU render nodes and shared storage.
A schema for managing 3D assets in a studio: projects, assets, versions, dependencies (textures, rigs), shots and reviews.
The states of a render job on a render farm: submitted, queued, rendering frame by frame, failures and retries, and completion.
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.