Inspect the current scene and units first. Use stable object IDs for continued work while retaining names for human readability. Put functional groups and helper geometry in named collections; distinguish independent duplicates from linked-data instances. When parenting an already placed object, use world-preserving parenting unless local-space relocation is intentional.
Import or link only from approved asset roots. Choose append when the project must own editable data, and link when provenance and shared updates matter. Record source paths, imported object receipts and any missing dependency. Do not download assets, install import extensions, or infer third-party license rights.
Before delivery, verify collection membership, local/world transforms, visibility in viewport and render, stable IDs after rename, linked versus copied data, and successful save/reopen. A successful simple fixture import does not guarantee compatibility with every external FBX, OBJ or glTF producer; disclose untested format features.
When to Use
Use when you need to organize scenes, collections, object identity, parent-child relationships, visibility, or import authorized reusable assets.
Prerequisites
- Clarify scene units, naming conventions, functional grouping, asset root directories, authorization sources, and the append/link strategy.
- Distinguish independent copies from shared data instances, and record objects that must preserve their world transforms.
Workflow
Step 1. Check existing collections, object IDs, transforms, and conflicting names. Step 2. Create collections by function and move objects; for already placed objects, use parenting that preserves world transforms by default. Step 3. Append or link from approved root directories, recording sources, dependencies, and import receipts. Step 4. Check viewport/render visibility, local/world transforms, instance semantics, and stable IDs. Step 5. Save and reopen, then verify that renames and references are still preserved.
Validation
Submit the collection tree, object stable IDs, transforms, visibility, linked/copied status, asset sources, missing dependencies, and reopen results.
Rules and capability boundaries (when not applicable)
Do not download assets, install import extensions, or infer third-party licenses; a simple fixture succeeding does not mean all FBX/OBJ/glTF producers are compatible.
Gotchas (common problems and recovery)
- Jumping position after parenting: restore the original matrix and redo it using a method that preserves world transforms.
- Linked assets cannot be edited: confirm whether append should be used, and do not silently break provenance.
- Missing dependencies: report the original paths and affected objects, and wait for authorized replacements.