DCC production guide
File Naming, USD, Alembic, and Asset Package Guide
Direct answer: A delivery package is production-safe when a new reviewer can identify the asset, version, cache type, and dependencies without guessing. Naming Convention and package structure are part of the asset itself, not afterthought documentation.
AlembicAsset PackageNaming ConventionUSDDependency ResolutionPublished Version
Naming is operational metadata
A good Naming Convention tells the receiver which asset they have, which variant or LOD it belongs to, and whether the file is a source scene, published cache, map, or engine-ready export. Ambiguous names waste review time and create version collisions.
USD versus Alembic use cases
USD is often chosen for scene composition, layered overrides, and richer data relationships. Alembic is commonly used for baked geometry caches or animation where the receiver does not need editable rig logic. They solve different handoff problems and should be labeled accordingly in the package.
Dependency resolution
Dependency Resolution means textures, references, payloads, caches, and variant files can be found from the package or repository location the team actually uses. A file that opens only on the author machine is not published, even if the geometry is correct.
Published version rules
A Published Version should freeze the intended review state: stable file path, known dependencies, preview image, and change note. Reviewers should know whether they are approving a work file, a cache, or the exact delivery payload.
Worked example
A crowd prop package may contain a USD assembly, Alembic motion cache for a simulation variant, texture folder, and engine export. Approval requires consistent names, a manifest, dependency check from a clean path, and a note explaining which file is the authoritative published delivery.
Multilingual production terms
Use this table when a file handoff must distinguish cache type, publish state, and naming policy across multilingual production teams.
| 中文 | English | 日本語 | Workflow usage note |
|---|---|---|---|
| Alembic | Alembic | Alembic | Baked geometry cache format for simulation results or animated mesh snapshots. |
| 资产包 | Asset Package | アセットパッケージ | Folder or archive containing all files needed to review and import the asset. |
| 命名规范 | Naming Convention | 命名規則 | Rule set encoding asset name, variant, version, map type, and LOD in the filename. |
| USD | USD | USD | Composable scene and asset format supporting layers, references, and variants. |
| 依赖解析 | Dependency Resolution | 依存関係解決 | Ability of the package to find all referenced files from a clean path. |
| 发布版本 | Published Version | パブリッシュバージョン | Frozen, reproducible delivery state with manifest and changelog. |
Related pages and next step
Open SEELE AI workspaceFAQ
Why is naming convention part of quality review?
Because broken naming leads directly to wrong imports, overwritten files, and failed dependency resolution even when the art itself is fine.
When should both USD and Alembic appear in one package?
When one file describes compositional scene structure and the other carries a baked simulation or geometry cache required by the receiver.
What makes a version truly published?
It must be reproducible from the package path, dependency-complete for review, and clearly separated from work-in-progress source files.
How do I test dependency resolution?
Open the package from a clean or relocated path and verify that all references, caches, and textures still resolve without the author’s local shortcuts.