Often in our practice, an artist delivers an FBX file created in Maya or Blender. You import it into Unity or Unreal Engine. The model is rotated by 90 degrees, the scale is 100 times larger than needed, normals are inverted on half the polygons, and the skeleton contains 8 extra bones from helper objects in the Maya scene. This is the standard situation without a clear asset delivery pipeline, resulting in wasted time on manual fixes and increased risk of errors during integration.
Integrating 3D assets is not just "drag file into Project Window." It involves aligning coordinate systems, scales, skeleton formats, UV channels, naming conventions for materials, and correctly configuring Import Settings for the specific engine and platform. We reduce integration time by up to 60% through automation and clear guidelines. Savings on integrating each subsequent batch of assets amount to 30–50% compared to a manual pipeline.
How to properly set up a 3D asset integration pipeline?
Mismatched coordinate systems
Maya and 3ds Max use Y-up, Blender defaults to Z-up, Unity uses Y-up, Unreal uses Z-up. When exporting FBX from Blender without proper Export Axis Convention, the model will be rotated in Unity. For an animated skeleton, this means Animation Clips will not play correctly.
Extra transforms and pivot issues
The artist delivers a character with pivot at the feet, a prop with pivot at the geometric center. In Unreal this is more critical: Static Mesh Pivot affects alignment when placing in the level. Rule: pivot point is determined in advance in the asset tech spec.
Materials and named slots
When importing FBX, Unity creates Material Slots based on names in the file. If the artist names materials Material.001, it is hard to sort out later. Before export, all materials must have semantic names: M_Char_Body, M_Char_Face. This convention is documented in the Asset Naming Convention document.
UV channels for Lightmap
Unity requires a second UV channel for baking lightmaps. If the asset arrives without UV2, Unity auto-generates it, and the result is often suboptimal: overlapping UV islands. For serious projects, UV2 is created manually in DCC (Maya/Blender).
Configuring Import Settings for the task
In Unity Import Settings for Mesh:
- Scale Factor — standard 0.01 for Maya/3ds Max (they work in centimeters, Unity in meters). Blender — 1.0 with correct export.
- Read/Write Enabled — disable for static meshes, enable only if runtime mesh modification is needed.
- Optimize Mesh — enable for final assets (regroups triangles for better GPU cache coherency).
- Generate Colliders — only for simple convex meshes. For complex collision, create a separate low-poly collider mesh.
For skinned characters: Rig → Animation Type = Humanoid (if Avatar and retargeting are needed) or Generic (if custom skeleton without retargeting). Humanoid has strict requirements for bone hierarchy — all 15 mandatory bones must be mapped.
Why glTF 2.0 is better than FBX for new projects?
Format comparison:
| Format | Material accuracy | Coordinate issues | Support |
|---|---|---|---|
| FBX | Low (requires manual conversion) | Frequent (scale, axes) | Universal |
| glTF 2.0 | High (PBR transmits natively) | Minimal | Unity, Unreal 5.1+ |
| USD | Depends on pipeline | Low with correct export | Unreal, Omniverse, AR |
glTF 2.0 is a modern open standard, natively supported in Unreal 5.1+ and Unity via the com.unity.formats.gltf package. PBR materials (metallic/roughness workflow) transmit without conversion. Issues with scale and coordinates are significantly fewer than with FBX. We recommend glTF for new projects — it reduces manual fixes by 70%.
USD (Universal Scene Description) is relevant for Unreal Engine with USDZ, pipelines with Omniverse, and AR (Apple Reality Composer). It supports references to other USD files, which is convenient for assembling scenes from modular assets.
FBX is a legacy standard, but still the most universal. Its problems are known and solvable with proper workflow. For automation of fixes, we use FBX SDK.
The process of working on asset integration
- Asset audit — check provided files for compliance with requirements (vertex count, UV2 presence, material names, coordinates).
- Develop Asset Delivery Guide — a document for artists: export settings, naming conventions, material and polycount requirements.
- Configure automatic import — write an AssetPostprocessor for Unity or Editor Utility Blueprint for Unreal to automatically assign Import Settings.
- Validate and fix problems — batch scripts to fix inverted normals, rename materials, align pivots.
- Test in scene — check asset in engine: LOD, collision, animations, lighting.
- Deliver and document — fix settings, train the team, hand over the finished pipeline.
Timelines and cost
| Task scale | Estimated timeline |
|---|---|
| Configure Import Settings for a ready asset package | 2–5 days |
| Develop Asset Pipeline + documentation | 1–2 weeks |
| Fix problematic assets + integration (20–50 objects) | 2–4 weeks |
| Full DCC → Engine pipeline with automation | 3–6 weeks |
Exact cost is calculated after an audit of your assets and selected engine. Contact us for a project assessment. Order an audit — we will estimate the savings for your project.
What is included in the work
- Audit of existing assets and identification of issues.
- Development and implementation of an Asset Delivery Guide.
- Configuration of automated import via AssetPostprocessor or Editor Utility Blueprint.
- Writing batch scripts to fix common errors (inverted normals, pivot, naming).
- Pipeline testing on a pilot batch of assets.
- Documentation and team training.
- Post-release support (2 months).
Our competencies
Our team has 10+ years of experience in game development, with over 50 projects in asset integration for Unity and Unreal Engine. We guarantee seamless integration of assets of any complexity level. This experience is backed by Unity and Unreal certifications. We reduce artifact correction costs by 30–50%.
Get a consultation on pipeline setup — write to us, we will evaluate your project for free.