Multilingual DCC reference tool

DCC Scene Transforms & Coordinates Multilingual Reference

Use this page to diagnose transform handoff problems: units, scale, up-axis, pivot placement, frozen transforms, parent hierarchy, negative scale, rotation order, and origin alignment. The compact glossary below preserves exact Chinese, English, and Japanese term coverage for search, filter, and copy workflows.

12 terms3 languagesP1 + P2 coverage

Intent-driven production guide

Direct answer for scene transforms, pivots, and coordinates

Direct answer: Use this page to diagnose transform handoff problems: units, scale, up-axis, pivot placement, frozen transforms, parent hierarchy, negative scale, rotation order, and origin alignment.

When to use it

Use when assets import rotated, offset, tiny/huge, mirrored, mis-parented, or with pivots that break animation, snapping, assembly, or engine placement.

Decision rule

Approve only when units, up-axis, forward axis, pivot/origin policy, transform freeze/reset state, hierarchy root, and target import proof are documented.

Cluster-specific workflow

Record source and target conventions: centimeters/meters, Y-up/Z-up, forward axis, left/right handedness, and engine scale multiplier.
Set pivot/origin by use case: door hinge, wheel axle, character root, modular snap corner, prop center, or world origin.
Reset/freeze transforms safely, remove negative scale, apply transforms before export when required, and preserve animated transforms when not.
Check parent-child hierarchy, instance links, constraints, and naming so assembly survives import.
Import to target app, measure bounding box, verify orientation and pivot behavior, then attach before/after transform evidence.

Decision and review checks

Ready

Unit scale and up/forward axis are explicitly named.
Pivot policy matches the asset function.
Transforms are frozen/applied or intentionally preserved.
Target import shows correct size, orientation, origin, and hierarchy.

Needs revision

Asset imports at 0.01x/100x scale or rotated 90 degrees.
Pivot is at world origin when hinge/snap/animation pivot is required.
Negative scale or unapplied transforms flip normals or animation.
Nested hierarchy changes naming or breaks engine prefab assembly.

Failure modes and fixes

Scale mismatch

Set units and export scale multiplier, then prove target bounding-box dimensions match the brief.

Wrong pivot behavior

Move origin to hinge/axle/root/snap point, re-export, and attach target rotation or snapping proof.

Mirrored or flipped asset

Apply transforms, remove negative scale, recalculate normals, and confirm handedness/up-axis settings.

Practical handoff and related tools

Hand off source file, export preset, unit/axis note, pivot screenshot, transform-freeze policy, hierarchy outline, and target import screenshot with measured dimensions and orientation.

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

Frequently asked questions

Which transform fields must be documented?

Units, up-axis, forward axis, pivot/origin policy, transform freeze state, hierarchy root, and export scale.

How do I prove pivot placement is correct?

Show the asset rotating, snapping, or assembling in the target app from the intended hinge, axle, root, or snap point.

What causes 90-degree or 100x import errors?

Mismatched up-axis, forward axis, unit scale, export multiplier, or unapplied transform settings.

Does this page fix scene transforms automatically?

No. It provides multilingual terms and QA checks for transform handoff.

Search termsPriorityLanguage field

Compact searchable glossary

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

Term 16P1_content