AEM 3D (Adobe Experience Manager 3D) lets you upload, manage, view, and render 3D content. Support for viewing and rendering is optimized for individual objects.
See also AEM 3D Release Notes.
See also Installing and configuring AEM 3D.
AEM 3D lets you view and render high-quality static, stand-alone 3D models in pre-defined environments called Stages. Basically, a stage provides “lighting” for the 3D scene and the settings for rendering in a native application such as Autodesk® Maya® or Autodesk 3ds Max®. In addition, the stage can optionally include pre-defined cameras, backgrounds, and ground plane geometry.
Uploaded 3D files that contain lights are assumed to be a stage. You can revert such assets to be simple 3D objects by opening the asset in the asset details page. Tap View Properties, then tap the Basic tab. Under the Metadata heading, from the Asset Class drop-down list, select 3D object.
When you create 3D models for use in AEM 3D, be aware of the following:
Your 3D model files should contain only one object, with no backgrounds, ground planes, scene lighting, or cameras.
Place the model above the ground plane. This positioning is especially important when you view or render with stages that provide a ground plane. A configuration setting is available (and enabled by default) that causes the object to be moved above the ground plane when previewing or rendering with Rapid Refine. This setting does not affect rendering with third-party renderers (for example, by way of Maya), and thus objects that are not located above the ground plane may be partially hidden.
Position the model so that it is reasonably centered laterally around the coordinate system origin (0,0,0). Doing so ensures a good interactive viewing experience for you.
Other than texture maps, external file references are supported. Therefore, you must embed any referenced content in the primary model file before you upload it into AEM.
The general scene lighting is provided by the stage. As such, Adobe does not recommend that you include lights with 3D model files. You can include lights in the model. However, they must be specific to the model only. For example, it may be necessary to include additional lighting to brighten a part of the object that is obscured by other parts. Therefore, it would not be sufficiently visible with just the stage lights.
A typical 3D asset has a primary model file and none or more referenced files. Referenced files include such things as texture maps or IBL (Image-Based Lighting) images.
The primary 3D model file contains the actual 3D model geometry and definitions for the (default) materials that are applied to the model surfaces. AEM 3D supports the following primary 3D model file formats:
Wavefront OBJ file format (
The OBJ format requires one or more separate, external MTL files (Material Template Library) (
Autodesk FBX (Filmbox) file format (
The Autodesk 3D file interchange format; both binary and ASCII formats.
When you create FBX files in third-party applications, Adobe recommends the following configuration settings (see table below). These settings can help you achieve the best results for 3D files that you intend to use in AEM. The option names are taken from the Autodesk Maya FBX Export Options dialog box.
|Option in Autodesk Maya FBX Export dialog box||Description|
AEM 3D currently does not support external references.
|Convert NURBS surfaces to||Software Render Mesh|
Select or deselect.
If you choose to select this option, AEM 3D ignores the animation information in the file.
Select for 3D stages.
Deselect for 3D models.
Select for 3D stages.
Deselect for 3D models.
|Units - Automatic||Select. AEM 3D converts on import.|
|Axis Conversion - Up Axis||
Y-up gives consistent results when you export from Maya and is the preferred coordinate system for FBX files in this AEM 3D release.
|Embed Media||Both options are supported. If embedded is selected, AEM 3D extracts the embedded media to an adjacent folder that has the same name as the model file with
|FBX File Format - Type||Both Binary or ASCII are supported.|
|FBX File Format - Version||FBX 2014/2015 is recommended. Other versions may also work fine.|
The following additional file formats are supported if Autodesk Maya is installed and configured on AEM authoring servers:
.ma and binary
Jupiter Tesselation (ISO 14306-1).jt.
An industry-standard CAD data exchange, collaboration, and product visualization format.
Material definitions in 3D model files can include references to external image files that provide texture maps. AEM 3D supports the following types of texture map files:
Materials in the primary 3D model file can reference other types of maps which are ignored by AEM 3D.
A 3D model file that defines a stage can reference a single IBL environment image. Currently, AEM 3D supports only 32-bit TIFF images in latitude/longitude format for diffuse IBL and for reflections. For the spherical scene background, 8-bit RGB images are also supported.
File references–other than those described above–that are present in the primary 3D model file are currently ignored. AEM 3D does not support references to secondary 3D model files.
Y-up is the preferred coordinate system for FBX files this release.
The original native model file can contain material definitions that are used with shaders such as Blinn, Lambert, or with procedural shaders. These potentially complex materials are supported only when you render using the corresponding native application (such as Autodesk Maya).
For viewing purposes or when you render using the default Rapid Refine™ renderer, all materials are either simplified, substituted, or both so they can be used with a Phong-like shader. This shader supports a limited set of attributes. Other attributes in the material definition are ignored.
See Viewing 3D assets.
See Rendering 3D assets.
A surface is defined as the surface area of a 3D model covered by the same material. This material also provides the name for the surface. As such, Adobe recommends that you name the materials included in primary 3D model files accordingly. For example, the use of specific names such as “Body”, “Windows”, “Tires”, or “Rims” is preferred to the use of vague names such as “Red”, “Glass”, “Rubber”, “Aluminum”.