Open Asset Import Library

Open Asset Import Library
Name	Open Asset Import Library
Developer	Assimp community
Released	2006
Programming language	C++
Operating system	Cross-platform
License	BSD-3-Clause

Open Asset Import Library

Open Asset Import Library is a portable C++ library that reads various 3D model formats and provides a unified scene representation for use by engines, tools, and applications. Initially created to bridge incompatibilities between formats used by Blender (software), Autodesk Maya, Autodesk 3ds Max, Unity (game engine), and Unreal Engine, it became a common import component for projects integrating assets from Adobe Substance, Pixar, Foundry, SideFX Houdini, and other digital content creation pipelines. The library is used in contexts ranging from computer graphics research labs associated with MIT, Stanford University, and ETH Zurich to industrial studios such as Weta Digital, Industrial Light & Magic, and independent developers contributing to Godot (game engine).

Overview

Open Asset Import Library provides converters and loaders that normalize disparate file structures from vendors like Autodesk, Dassault Systèmes, and Trimble Navigation into a single scene graph usable by renderers, physics engines, and viewers. The project surfaced as a response to interoperability issues similar to those tackled by initiatives from Khronos Group and by standards such as COLLADA and glTF. Maintained by an open-source community including contributors from organizations such as Intel Corporation, NVIDIA, AMD, and universities like University of Cambridge, it aims to simplify asset pipelines linking tools such as Modo, Cinema 4D, Houdini, ZBrush, and Mari.

Features

The library implements features for mesh processing, bone and animation handling, material and texture assignment, and scene hierarchy representation compatible with renderers like RenderMan, V-Ray, Arnold (renderer), and real-time engines including CryEngine. It exposes per-vertex attributes, normal and tangent generation, and supports skeletal animation formats used in productions at Pixar Animation Studios, DreamWorks Animation, and Blue Sky Studios. Tools and middleware leveraging the library include exporters for Autodesk FBX, converters between OBJ (file format), PLY (file format), and STL (file format), and integration with asset management systems used by studios such as Lucasfilm and Sony Pictures Imageworks.

Supported Formats

Supported import formats span legacy and modern standards: Wavefront (.obj), Autodesk FBX, COLLADA (.dae), glTF, Stanford PLY, Stereolithography (.stl), 3D Studio (.3ds), Alembic (.abc), DirectX X (.x), LightWave Object (.lwo), and game-centric formats associated with Valve Corporation, id Software, Epic Games, and Nintendo. The library also accommodates interchange with CAD-exported formats from Siemens PLM Software, PTC (company), and SolidWorks via exporters, and supports scenes generated in tools such as SketchUp and Rhino (software).

Architecture and Design

The architecture centers on a modular importer pipeline where individual format readers normalize into an intermediate scene structure with nodes, meshes, materials, lights, and cameras analogous to representations used by OpenGL, Vulkan, and Direct3D. Parsers for binary and ASCII formats are implemented with portable I/O and memory management influenced by practices from LLVM and Boost (C++ libraries). The design separates concerns between front-end loaders, post-processing steps inspired by algorithms from SIGGRAPH publications, and back-end bindings for languages and environments like Python (programming language), C#, and Java (programming language) used in projects at Google and Microsoft.

Usage and APIs

APIs are provided in C and C++ with utility bindings for scripting languages often employed at studios such as ILM and research groups at Caltech and Imperial College London. Consumers call import functions to obtain scene graphs, enumerate meshes and materials, and access animation channels compatible with middleware such as Bullet (physics engine), PhysX, and renderer pipelines used by Blender Foundation. Example integrations include asset loaders for Godot, plugins for Maya, and converters used in pipelines at post-production houses like Framestore and Double Negative.

Performance and Limitations

Performance varies by format complexity; binary formats like glTF and optimized FBX exports yield faster parse times than verbose COLLADA or ASCII OBJ variants. Memory overhead arises from full-scene normalization and intermediate copies required for post-processing steps like triangulation, smoothing, and vertex deduplication, a concern in large datasets produced in projects such as The Lord of the Rings (film series) and Avatar (film). Limitations include partial support for proprietary extensions from vendors like Autodesk and incomplete round-tripping for complex material networks exported from Substance Painter and Redshift. Performance tuning often relies on integrations with accelerated libraries from Intel and GPU-driven pipelines using CUDA or Vulkan.

Development and Community

Development is coordinated through a code hosting and issue-tracking platform frequented by contributors from GitHub, with governance reflecting practices from other open-source projects such as Linux kernel and Blender Development Fund initiatives. The community includes individual contributors, corporate sponsors, academic researchers, and pipeline engineers from studios like Framestore and MPC; discussion occurs on mailing lists, forums, and at conferences like SIGGRAPH, GDC, and Eurographics. Releases follow semantic versioning and are accompanied by changelogs used by integrators at Valve and Epic Games to plan compatibility updates.

Category:3D graphics software