# Import from Blender, Maya, or Houdini Pure prompt tools can't ingest a 3D file. The brief came with a client CAD asset; the prompt tool has no way to use it. The agency's existing pipeline lives in Maya or Blender; the AI tool acts like the pipeline doesn't exist. Workflows fork, time gets lost on rebuilding what already exists. Intangible's Smart Import takes the common 3D exchange formats from any DCC – FBX, OBJ, USD, GLB, DXF – and lands them in the scene. Smart Import does the cleanup work that usually eats an hour: scale correction, axis alignment, category metadata, sometimes light unwrapping. The asset is ready to compose against in minutes, not after a day of cleanup. ## Steps 1. **Export from your DCC in a supported format.** FBX is the most common. OBJ for static geometry, USD for layered scenes, GLB for web-aligned exports, DXF for CAD interoperability. 2. **Open Build mode in the target Intangible project.** Smart Import is a Build-mode action. 3. **Drag the file into the viewport, or use Import Asset.** The Asset Library's footer has an **Import Asset** button. Drop or pick the file. 4. **Smart Import opens an editing environment.** A new view shows the imported geometry in isolation, with controls for: * **Scale** – auto-detected, but adjustable. A Maya export at 1 cm and a Blender export at 1 m need different scale corrections. * **Orientation / Up axis** – Y-up vs Z-up handled here. Maya defaults Y-up; Blender defaults Z-up; Houdini defaults Y-up. * **Category** – tag the asset (Vehicle, Character, Furniture, Set Piece). Used by populators and the asset library's filters. 5. **Confirm and import.** The asset lands in the scene at the cursor or center, and is added to **My Assets** in the Asset Library for reuse in this project and others. 6. **Optionally attach an Image Reference.** Open Object Details on the imported asset and attach a hero photograph. The geometry provides the shape; the reference provides the surface. Together they're the brand-true workflow. 7. **Compose and render.** Treat the imported asset like any other library asset. Position, frame, render in Visualize. ## DCC-specific notes * **Blender** – use **File → Export → FBX** with default settings. Z-up needs to be flagged on import. Materials don't carry through reliably; assume you'll attach an Image Reference for surface. * **Maya** – **File → Export Selection → FBX**. Y-up by default. Bake transforms before export to avoid scale surprises. * **Houdini** – **File → Export → ROP FBX Output**. Multi-asset exports work, but consolidating to a single FBX simplifies the import. * **Cinema 4D** – **File → Export → FBX**. Watch for axis flipping; the Smart Import editing environment lets you correct. * **Unreal Engine** – exports via Datasmith or FBX. For Unreal-bound work specifically, think about whether you're going Intangible → Unreal (USD export from Intangible) or Unreal → Intangible (FBX import here). Both directions work. ## Why this works Smart Import does the boring half of asset onboarding so you can spend time on the brief instead of the import. Scale correction, axis alignment, category metadata – work that used to live in a hidden cleanup pass is exposed and quick. The imported asset becomes part of the structured scene the visualizer reads. Geometry, position, scale, orientation – all passed to the model as input alongside the prompt. The render reflects the actual asset's shape, not a generic interpretation. ## Tips * **Bake transforms in your DCC before export.** Especially for animated assets or rigs. Frozen transforms import cleaner than world-space matrices. * **Strip what you don't need.** A 5-million-poly architecture model imports slowly and renders slowly. Decimate or LOD-down in your DCC if the brief doesn't need every triangle. * **Group sensibly.** A vehicle as a single FBX with body / wheels / interior as nested groups imports cleanly. The same vehicle as a hundred unparented meshes is harder to work with. * **USD when scenes layer.** For multi-asset, multi-take production work, USD's layering preserves more structure than FBX. Intangible reads USD; use it for complex scenes. ## Limits * **No animation import yet.** Smart Import handles geometry and basic transforms, not skeletal animation or simulation cache. Animate inside Intangible's Compose mode for shot-bound animation. * **Materials and shaders don't carry through reliably.** Assume the imported asset will need an Image Reference for surface fidelity. The geometry is reliable; the surface is what the AI render fills in. * **Rigs don't import.** The mesh imports; the rig and weights don't. For animated character work, generate stills with a posed mesh or animate in the source DCC and bring in the baked alembic / FBX once supported. * **Very large files (over 1 GB) may stress import.** Decimate first. ## Related * [Import your own models (reference)](/build/import-your-own-models.md) * [Generate a 3D model from an image](/overview/how-to/ai-3d-model-from-image.md) – when you don't have a CAD file, generate one from a photograph instead. * [Match a client's product exactly](/overview/how-to/brand-true-ai-render.md) – the full agency workflow. * [Supported file formats](/overview/reference/supported-file-formats.md) * [Image reference](/overview/concepts/image-reference.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.intangible.ai/overview/how-to/import-from-blender-maya-or-houdini.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.