KURE Animation Production: File Naming Conventions
Outline:
1. Introduction
This document outlines the naming conventions for all files within the KURE production.
For specific file naming conventions related to insider of Blender, please refer to the Blender Naming Conventions document.
2. General Rules
- camelCase & underScores: Use camelCase letters for all components. Use underscores (
_) as the primary separator between components. - No Spaces: Avoid spaces in all filenames and folder names. Use underscores instead.
- Versioning Work Files: Use a consistent versioning system for work files.
- Versioning Published Files: Overwrite published files for minor fixes or tweaks. Create a new version when making substantial changes or updating link-dependent elements.
3. Key Components & Abbreviations
The following table defines the standard components used in naming files:
3.1. Shot Files
Example file: kure_layout_sq0010_sh0010_v001_nb_fixCamAnimation.blend
| Component | Format / Abbreviation |
|---|---|
| Project Name | kure |
| Stage | previz, layout, anim, bgArt, bgSet, cloth, efx, render, comp |
| Sequence Number | sq0000 |
| Production Shot Number | sh0000 |
| Version | v001 |
| Artist Initials | nb |
| Note | fixCamAnimation |
| File Extension | .blend |
3.2. Asset Files
Example file: kure_mld_anton_v001_nb_topologyFix.blend
| Component | Format / Abbreviation |
|---|---|
| Project Name | kure |
| Department | chr, set, prp, lib, mtl, efx, aud, gfx |
| Asset Name | anton |
| Asset Type | mdl, sclpt, rig, sha, tex, groom, clothes |
| Version | v001 |
| Artist Initials | nb |
| Note | topologyFix |
| File Extension | .blend |
4. published files
for published file you remove name and note from the file name.
- Asset Published File:
- Example file:
kure_mld_anton_v001.blend
- Example file:
- Shot Published File:
- Example:
kure_layout_sq0010_sh0010_v003.blend
- Example:
- Exported Component Published File:
- Example:
kure_anim_sq0010_sh0010_anton_v001.abc
- Example:
This document should serve as a foundation. It can be adapted and expanded as the KURE project evolves and new needs arise. Clear communication within the team is paramount to successfully implementing these conventions.