AEM-6.3-DynamicMedia-3D version 2.1.0 (December 6, 2017)
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 and other file formats, including high-quality rendering with the NVIDIA® mental ray® Standalone plug-in for Maya.
See also Working with 3D assets.
See also Working with the 3D Sites component.
- AEM 6.3.0 with Service Pack 1
- Autodesk® FBX® SDK 2016.1.2
Supported operating systems
- Microsoft Windows 2012 Server.
- Apple OS X El Capitan 10.6 or later.
- RedHat Enterprise Linux 7.3
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 32GB 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.
See also Working with 3D assets.
|OBJ||Wavefront OBJ 3D interchange||all|
|FBX||Autodesk FBX (Kaydara Filmbox)||all||The Autodesk FBX SDK must be installed on the author node.|
|MA, MB||Native Autodesk Maya||Windows only||
Autodesk Maya is required on the author node to enable these file formats. See Integrating with Autodesk Maya
|JT||Siemens PLM Open CAD||Windows only|
|*||Additional 3D input formats supported by Autodesk Maya can be enabled. See Enabling Additional Formats Supported By Maya||Windows only|
- Added support for Linux deployment.
- Added support for additional 3D file formats (requires Maya, Windows only).
- Added support for publishing of 3D assets (replication to AEM publish servers).
- New AEM Sites 3D component which enables interactive 3D viewing experiences in published web pages.
- Various minor changes and bug fixes to improve stability, quality, and user experience.
- 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 dependencies 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 dependencies.
- Mathematica (.ma) files - Mathematica files use the same file suffix as native Maya files. When the feature pack is installed and the Maya .MA file format is enabled, AEM's attempt to ingest Mathematica files as Maya files will fail. The Mathematica assets will display an error banner in Card View, but otherwise be functional.
- Targa (.tga) image files - Older 3D model 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. AEM does not support the creation of renditions for these assets, resulting in blank thumbnails, and therefore, cannot be previewed. These assets still function correctly when used with IBL stages.
- 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 display. 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-insensitivity - Automatic dependency resolution attempts to match file names in a case-insensitive fashion. For example, if the original dependency found in the 3D asset is image.jpg, the dependency would resolve to an asset named Image.jpg or image.JPG or any other case variation.
- Thumbnails for stages - The auto-generated thumbnails for stages may not represent the stage accurately.
- 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. Such geometry should still display reasonably in asset detail view (3D preview).
- 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 Environment Image, and Background Environment Image.
- Background image of IBL stages - For some IBL scenes, the background image extracted automatically may have poor quality such as being too bright or too blurry. To optimize 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 before uploading to AEM.
- 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.
One 3D component per page. At this time, only one instance of the 3D component is allowed on each web page. If more than one 3D component is present in the same page, none of the components will function correctly.
Not compatible with require.js. This version of the 3D component is not compatible with pages that include require.js.
3D View missing when previewing in Sites. When using the Preview feature in Sites, the page must be reloaded in the browser to fully initialize the 3D viewer. This is not an issue when viewing the web page directly (that is, when edit.html has been removed from the path) either on author or publish nodes.
Full-Screen mode not available on iOS devices. The full-screen button is not available on iOS devices, regardless of the browser used.
3D Component configuration. The 3D feature pack must be installed on all active publish nodes and each node must be configured with CRXDElite to the same config options at /apps/cq-scene7-v3D/config/webGLSites.
Missing textures, background, or lighting after publishing. The Publish mechanism in AEM Sites automatically publishes the page's primary dependencies, including the 3D model and the 3D stage referenced by the 3D component. 3D stages and 3D models typically depend on secondary assets for IBL images and texture maps, which the Sites Publish mechanism does not publish automatically. Workaround: Publish all 3D assets from AEM Assets before publishing the web page from AEM Sites. This will ensure that all dependencies for 3D assets are available on the publish nodes.