Project Structure

GitHub: project structure

Structure Types

task based
For specialist teams where tasks are strictly divided so the artist has an easy "everything in one place" structure.
Shows just assets and shots related to the task. (ASSET/RIG/mike)

shot & asset based
Easier to switch if the artist is working on more tasks at once. Generalist approach for smaller projects. (ASSET/mike/RIG)

Directory

• 0_pipeline - custom settings, plugins & scripts for the show

• 1_sandbox - private space to save junk and tests

  • arichter

• 2_preproduction

  • festival
  • meetings
  • presentation
  • promotion
  • making_of
  • reference
  • rnd
  • screenplay
  • concept
  • storyboard
  • animatic

• 3_footage - common assets, shaders & textures

  • hdri
  • texture
  • shader
  • scene

• 4_assets - assets

  • (optional: char, prop, set, location)
  • asset_name
    • GEO, RIG, SHD(, TEX)
      • WORK, PUBLISH

• 4_shots (s010, s020 ...) - working scenes

  • s010
    • ANIM, FX, LGT, COMP
      • WORK, PUBLISH

• 5_post

  • edit
    • cut
    • sound
    • music
  • grade
  • mov
  • deliver - every format of the final product

Status

WORK

Work in progress files.

name_TASK_version.extension mother_RIG_v001.mb

shotNr_AOVs_version.####.extension s010_diffuse_v001.1001.exr

PUBLISH

Files shared with others. Often these files referenced in other tasks (RIG references GEO).
Will be overwritten since they are referenced but a history is saved of the published files.

name_TASK.extension mother_RIG.mb

shotNr_AOVs.####.extension s010_diffuse.1001.exr