You're viewing help content for version:

AEM-6.2-DynamicMedia-3D version 1.1.0 (September 23, 2016)

This feature pack enables support for 3D content in AEM Assets. It provides capabilities to upload, manage, preview, and render 3D assets.

Also included are server-side integrations with Autodesk® Maya® (Windows only). When you install and configure Maya on the same server as AEM you enable support for native Maya file formats, including high-quality rendering with the NVIDIA® mental ray® Standalone plug-in for Maya.

See Integrating with Autodesk Maya.

See also Installing and configuring AEM 3D Assets and Advanced configuration settings.

See also Working with 3D assets.

System requirements


  • AEM 6.2.0, Author node
  • cq-6.2.0-hotfix-12785 (required for Service Pack 1)
  • Service Pack 1 (AEM-6.2-Service-Pack-1)
  • Assets Dynamic Media Feature Pack 2 (cq-6.2.0-featurepack-12692)
  • Autodesk® FBX® SDK 2016.1.2

This Feature Pack is supported for AEM Author nodes only; AEM Publish nodes of 3D assets are not currently available.

Supported operating systems

  • Microsoft Windows 2012 Server.
  • Apple OS X El Capitan version 10.6 or later.

Linux is currently not supported.

Supported web browsers

  • Google Chrome 53 or later (recommended).
  • Apple Safari 9.1 or later.
  • Firefox 48 or later.
  • Microsoft Edge 25.10586 or later.

Other browsers may not support interactive viewing of 3D content in AEM. Only Google Chrome supports cast shadows in Preview.

Hardware requirements and recommendations

  • CPU - 3D processing and rendering is very demanding on a computer's CPU. As such, a contemporary server with a minimum of eight CPU cores is recommended.
  • Memory - A minimum of 64GB is recommended.
  • Mass storage - High bandwidth SSD storage is recommended.
    On upload, 3D assets are converted to a proprietary format for fast, interactive viewing in AEM. Besides the proprietary format, native Autodesk Maya files are converted to FBX. Depending on the type of 3D asset, storage space of 2-3x the size of the uploaded 3D asset is required.

Installing and configuring AEM 3D

Restrictions and known issues


  • Running as a Windows service is not supported (Windows only) - This may work but it has not been tested.


  • Resolve Dependencies shortcut - This shortcut is available in the Card View on 3D assets. Asset cards in the Card View show the "Unresolved Dependencies" banner. The shortcut opens the Basic Properties tab instead of the Dependencies tab. Workaround: manually navigate to the Dependencies tab.
  • Stage selector not available - 3D assets that include lights are automatically tagged by AEM as 3D stages. No Stages selector is available for stages in the Detail view. To mark a 3D asset as a 3D object, navigate to Basic Properties, change Asset Class to 3D Object, then click Save.
  • Downloading 3D assets with dependents and renditions - When downloading 3D assets from AEM with both Dependencies and Rendition(s) checked, the download includes not only the renditions of the primary 3D asset, but also the renditions of all dependents.

File type restrictions

  • 3ds Max (.max) files - The Feature Pack includes a preliminary integration hook for Autodesk® 3ds Max®. Uploading a .max file results in an error banner shown on the asset, even though the 3ds Max integration is disabled.
  • Mathematica (.ma) files - Mathematica files use the same file suffix as native Maya files. It is likely that Mathematica assets would display an error banner in Card View, but otherwise be functional.
  • Targa (.tga) image files - 3D files may include references to TGA files. This format is not supported by AEM. Adobe recommends that you convert such files to a different format before you upload them into AEM.
  • HDR images - HDR images are used for stages with image-based lighting (IBL). Currently, only 32-bit TIFF images are supported for this purpose.
  • 32-bit TIFF images - 32-bit TIFF images are used for stages with image-based lighting. Blank thumbnails are displayed for such assets in AEM and, therefore, cannot be previewed. The asset still functions correctly when used with an IBL stage.

Automatic dependency resolution

  • Unresolved file dependencies after upload - When 3D assets and their dependents are uploaded with the same upload operation, it is possible that some dependents are not resolved automatically. This issue is more likely to occur if the dependent files are large. To correct this issue, access the Properties/Dependencies page of the asset that shows unresolved dependents after upload. The previously unresolved dependents should now be shown. Click Save to finalize the asset. To prevent this issue in the future, you can upload all dependents in a separate transaction before you upload the 3D objects.
  • Case-sensitivity - Automatic dependency resolution attempts to match file names in a case-sensitive fashion. For example, if the original dependency found in the 3D asset is image.jpg, but the uploaded file is named Image.jpg or image.JPG, the dependency is not resolved automatically.
  • Non-deterministic matching - The algorithm by which dependents are selected from the available choices is currently not deterministic. For example, a dependent file may be located in the same folder, but the auto-dependency algorithm may instead resolve to a dependent located in a peer folder. To minimize such issues, Adobe recommends that you avoid having multiple assets with the same name.
  • Limited search range - The search scope for file dependents starts in the parent folder of the folder in which the 3D asset is located. If the dependent file is located elsewhere in the repository, it is not found.

3D stages

  • Thumbnails for stages - The auto-generated thumbnails for stages may not represent the stage accurately.
  • Viewing of stages - Similarly, previewing stages may not provide the expected experience. To accurately view the appearance of a stage, open a 3D object in Detail view, then select the stage to be inspected using the Stages drop-down list.
  • Stage geometry for non-IBL stages - The Rapid Refine renderer does not render geometry from stages with non-IBL lighting, including backgrounds and ground planes.
  • FBX stages with IBL lighting - You can upload FBX stages with IBL lighting. However, the FBX format does not have provisions to transfer the IBL image name. As such, file dependency resolution fails. The IBL image must be assigned manually to the stage after upload. You can assign the same TIFF image to the three dependencies which are Diffuse Lighting Environment Image, Reflection Envrionment Image, and Background Envrionment Image.
  • Background image of IBL stages - For some IBL scenes, the background image may have poor quality such as being too bright or too blurry. To maximize the visual quality of the image background of IBL stages, Adobe recommends that you prepare a separate high-resolution 8-bit JPEG image and attach it to the IBL stage as the Background Environment Image.
  • Black image when rendering with Maya using an IBL stage - This problem is likely caused by Maya not finding the IBL image dependency because the original IBL image referenced by the stage was replaced by an image with a different name. To avoid this issue, make sure that at least one of the three dependencies referenced by the Maya IBL stage has the same name as the original dependency.
  • Reversed background image for IBL stage - The images for IBL stages are intentionally flipped horizontally to match the behavior of the NVIDIA mental ray renderer provided with Autodesk Maya. Workaround: Flip the IBL image in Photoshop prior to uploading.
  • Brightness of IBL stages - The automatic analysis of the IBL image may result in a scene that is too dark or too bright. To adjust the lighting brightness of IBL stages, navigate to Basic Properties and adjust the bright value of Environment Lighting as needed.