SEELE AIOpen reference

Multilingual DCC reference tool

DCC File Formats USD & Pipeline Multilingual Reference

Use this page to decide and document interchange terms for USD, FBX, Alembic, glTF, OBJ, texture packages, variants, payloads, references, schema versions, and department handoff artifacts. The compact glossary below preserves exact Chinese, English, and Japanese term coverage for search, filter, and copy workflows.

30 terms3 languagesP0 + P1 + P2 coverage

Intent-driven production guide

Direct answer for file formats, USD, and pipeline exchange

Direct answer: Use this page to decide and document interchange terms for USD, FBX, Alembic, glTF, OBJ, texture packages, variants, payloads, references, schema versions, and department handoff artifacts.

When to use it

Use for export/import tickets, USD stage assembly, asset library publishing, vendor delivery specs, and engine ingestion where file format choice changes animation, materials, scale, or layering.

Decision rule

Approve only when target consumer, format version, unit scale, up-axis, animation scope, material support, payload/reference policy, and validation command are recorded.

Cluster-specific workflow

  1. Identify consumer: DCC scene, renderer, game engine, USD stage, asset library, or review viewer, then choose format by required data.
  2. For USD, define stage root, layer stack, payloads versus references, variants, purpose tags, metersPerUnit, upAxis, and schema/API version.
  3. For FBX/Alembic/glTF, record animation sampling, embedded/external textures, triangulation, normals/tangents, and material limitations.
  4. Run import/export round-trip in the target app and compare hierarchy, transforms, materials, animation, and file size.
  5. Publish with manifest, validator log, dependency list, texture paths, and fallback format when the primary exchange is unsupported.

Decision and review checks

Ready

  • USD layers, variants, payloads, references, units, and up-axis are documented.
  • FBX/Alembic/glTF export options match the target importer.
  • Texture dependency paths and package structure are reproducible.
  • Round-trip validation log and viewer screenshot are attached.

Needs revision

  • USD payloads resolve only on the author machine.
  • FBX scale or axis changes after engine import.
  • Alembic cache lacks frame range, sample rate, or topology-change note.
  • glTF material or texture compression settings are not documented.

Failure modes and fixes

Missing USD dependencies

Package sublayers, payloads, references, and texture paths with relative asset-root rules, then rerun usdchecker or viewer validation.

Scale/axis mismatch

Set metersPerUnit/upAxis or FBX unit conversion explicitly and attach target-import transform proof.

Material loss in exchange

Document unsupported shader nodes, bake texture fallback maps, and include target material reconstruction notes.

Practical handoff and related tools

Hand off the primary exchange file, dependency manifest, USD layer tree or export preset, validator log, target-app import screenshot, version/schema notes, and fallback files for departments that cannot consume the primary format.

Open SEELE AI workspace →Validate a 3D asset →Browse production tools →

Frequently asked questions

When should USD be preferred?

Use USD when layered assembly, variants, payloads, references, and non-destructive department composition matter more than a single baked file.

What should an FBX handoff specify?

Units, up-axis, animation sampling, embedded or external textures, normals/tangents, triangulation, and target importer version.

How do I prove a file exchange worked?

Attach target-app import screenshot, hierarchy/transform comparison, material preview, animation playback check, and validator log.

Does this reference convert files?

No. It defines multilingual pipeline terms and acceptance evidence for file-format handoff.

Compact searchable glossary

Showing 30 of 30 entries. Compare translations in context, then copy the approved wording into production briefs and QA notes.

Term 114P1_content

Dependency Resolution

中文依赖解析ENDependency Resolution日本語依存関係解決

该术语用于USD、管线、版本与数据交换相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 115P1_content

Published Version

中文发布版本ENPublished Version日本語パブリッシュバージョン

该术语用于USD、管线、版本与数据交换相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 188P1_content

Alembic

中文AlembicENAlembic日本語Alembic

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 189P1_content

Asset Package

中文资产包ENAsset Package日本語アセットパッケージ

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 190P1_content

Naming Convention

中文命名规范ENNaming Convention日本語命名規則

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 191P1_content

USD

中文USDENUSD日本語USD

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 308P2_supporting

Asset Resolver

中文资产解析器ENAsset Resolver日本語アセットリゾルバ

该术语用于USD、管线、版本与数据交换相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 309P2_supporting

Namespace

中文命名空间ENNamespace日本語名前空間

该术语用于USD、管线、版本与数据交换相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 310P2_supporting

Path Mapping

中文路径映射ENPath Mapping日本語パスマッピング

该术语用于USD、管线、版本与数据交换相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 311P2_supporting

Payload

中文载荷ENPayload日本語ペイロード

该术语用于USD、管线、版本与数据交换相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 312P2_supporting

Prim

中文PrimENPrim日本語Prim

该术语用于USD、管线、版本与数据交换相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 313P2_supporting

Scene Description

中文场景描述ENScene Description日本語シーン記述

该术语用于USD、管线、版本与数据交换相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 314P2_supporting

Shot Asset

中文镜头资产ENShot Asset日本語ショットアセット

该术语用于USD、管线、版本与数据交换相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 315P2_supporting

Variant Set

中文变体集ENVariant Set日本語バリアントセット

该术语用于USD、管线、版本与数据交换相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 356P2_supporting

Checklist

中文检查项ENChecklist日本語チェック項目

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 357P2_supporting

Dependency

中文依赖项ENDependency日本語依存関係

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 358P2_supporting

File Path

中文文件路径ENFile Path日本語ファイルパス

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 359P2_supporting

OpenEXR

中文EXRENOpenEXR日本語EXR

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 360P2_supporting

PNG

中文PNGENPNG日本語PNG

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 361P2_supporting

Project File

中文项目文件ENProject File日本語プロジェクトファイル

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 362P2_supporting

Proxy

中文代理ENProxy日本語プロキシ

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 363P2_supporting

Relative Path

中文相对路径ENRelative Path日本語相対パス

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 364P2_supporting

Source File

中文源文件ENSource File日本語ソースファイル

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 365P2_supporting

Targa

中文TGAENTarga日本語TGA

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

Term 366P2_supporting

TIFF

中文TIFFENTIFF日本語TIFF

该术语用于文件格式、管线与版本相关环节；制作团队可用这组三语对照统一任务说明、评审反馈与交付命名。

No matching term. Try another spelling or language.

Production-critical P0 terminology

Use these direct-intent terms to name concrete production checks, repair tasks, and delivery blockers across Chinese, English, and Japanese teams.

P0 Term 7P0_direct

Automated Validation

中文自动化检查ENAutomated Validation日本語自動チェック

用于自动验证交换数据、版本和依赖，帮助在发布前发现管线不兼容问题。

P0 Term 23P0_direct

FBX

中文FBXENFBX日本語FBX

用于明确资产交换格式及其交付检查，避免几何、材质或层级在软件间丢失。

P0 Term 24P0_direct

glTF

中文glTFENglTF日本語glTF

用于明确资产交换格式及其交付检查，避免几何、材质或层级在软件间丢失。

P0 Term 25P0_direct

OBJ

中文OBJENOBJ日本語OBJ

用于明确资产交换格式及其交付检查，避免几何、材质或层级在软件间丢失。

P0 Term 26P0_direct

STL

中文STLENSTL日本語STL

用于明确资产交换格式及其交付检查，避免几何、材质或层级在软件间丢失。

Related DCC references and tools

DCC Scene Transforms & Coordinates Multilingual Reference →DCC Software Workflow Multilingual Reference →DCC Rendering Shading & Output Multilingual Reference →3D Asset Validator & Model Checker →

P0 article and checklist coverage

FBX glTF OBJ STL Export Decision Guide →