How to Transfer a 3ds Max Scene to Unreal Engine with Datasmith

What will you learn in this guide?

This guide covers what to check before transferring an architectural scene created in 3ds Max to Unreal Engine with Datasmith, and how to diagnose issues that may appear after import. The focus is not just on moving a scene into Unreal Engine, but on understanding how geometry, hierarchy, naming, surface orientation, and lightmaps affect the result.

Rather than transferring individual objects one by one, Datasmith is designed to carry an entire scene from a design application, including its objects, materials, pivots, scale, hierarchy, and metadata. That makes scene organization before transfer and validation afterward important parts of the workflow, particularly for large architectural projects.

Requirements and version compatibility

Autodesk 3ds Max versions 2016–2026 appear in Epic’s list of supported software. This workflow uses the Datasmith exporter plugin installed in the application. On the Unreal Engine side, the Datasmith importer plugin must be enabled for the relevant project. The plugin download page and import instructions are available in Epic’s official Datasmith documentation.

Check version compatibility at the start of the transfer. Epic does not always guarantee backward compatibility between the Datasmith exporter plugin and the versions of Unreal Engine and the Datasmith plugin. Although a .udatasmith file created with an older plugin may open in a newer version of Unreal Engine, relying on this is not recommended. The source documentation advises matching the exporter plugin to the versions of Unreal Engine and the Datasmith plugin you plan to use.

Step-by-step transfer and checks

1. Organize the scene for transfer. Review object names and hierarchy. Datasmith tries to preserve naming information from the source application in assets and actors wherever possible. However, results may vary depending on the source application or file format. If objects share the same name, asset labels in the Unreal Engine Content Browser may be repeated; actor names, by contrast, may be changed to make them unique in the level.

2. Simplify transforms. Coordinate conversions can produce unexpected results, particularly when non-uniform scales in the hierarchy are combined with custom pivot transforms adjusted at the object level. If an object’s position or transform does not match the source scene after transfer, consider returning to the source file and simplifying the transform hierarchy.

3. Prepare the plugin workflow. Make sure the Datasmith exporter plugin is available in 3ds Max and the Datasmith importer is available in the Unreal Engine project. Epic’s support table identifies the 3ds Max workflow as “Export Plugin.” Since the source documentation does not specify the exact plugin version to use for a particular project, match the version to the Unreal Engine and Datasmith plugin you are using.

4. Transfer the scene and verify real-world dimensions. Unreal Engine uses centimeters for distances. Datasmith automatically adjusts the scale to preserve the scene’s real-world dimensions, even if a different unit of measurement is selected in the source application. Still, check critical dimensions after import. In the example given in the official documentation, an object 10 inches long in the source scene is 25.4 units long in Unreal Engine.

5. Diagnose surfaces that appear to be missing. If a ceiling or pipe ends are invisible from certain angles, that does not necessarily mean the geometry failed to transfer. Unreal Engine may treat triangles facing away from the camera as backfaces and omit them from rendering. Check surface normals and geometry thickness in the source application. For objects that need to be visible from both sides, adding thickness and orienting normals outward is recommended.

6. Review lightmap preparation. For static lighting, each static mesh needs non-overlapping UV coordinates for its lightmap. Datasmith runs an automatic UV unwrapping system on the static meshes it imports, creating two UV sets and assigning the second generated UV set for the lightmap. If you already have lightmap UV channels prepared in 3ds Max, consult the dedicated 3ds Max guide for using those channels.

Common issues

A surface is visible from only one side: First check the direction of the surface normal and the model’s thickness. For a surface that should be visible from only one side, flipping the normal in the source application is one option. Making the material two-sided in Unreal Engine can also make the surface visible from both directions; however, Epic warns that this may cause visual artifacts with static or stationary lighting. Light passing through the surface may be a separate issue; in that case, the documentation points to the setting that makes a static mesh actor cast shadows from both sides.

Names look different after transfer: The static mesh label in the Content Browser, the name of the asset file on disk, and the actor name in the level do not have to match. File names are kept unique, while the Content Browser label and actor name may be derived differently from the source scene’s naming information. Keep this distinction in mind when working with Blueprint or Python.

Unexpected shadows with static lighting: If triangles in the lightmap UVs occupy the same area, lighting information may not be stored correctly. Using a two-sided material can also create artifacts with static or stationary lighting. Investigate UV overlap and surface orientation separately to determine the cause.

Impact on architectural and visualization workflows

This workflow is useful for architecture firms, interior designers, and visualization teams that want to bring a 3ds Max scene into Unreal Engine with more than just its geometry, including its scene structure and related information. Automatic scale conversion makes it easier to transfer projects created in different units, but checking critical dimensions remains important. Since complex hierarchies can cause transform issues, review scene organization and pivot use before transfer as well.

The sources do not include licensing or pricing information. Hardware requirements are also not specified, so this guide cannot be used to determine a particular computer configuration. Teams should pay particular attention to matching plugin versions, addressing the need for two-sided visibility during modeling, and validating UV channels when using static lighting.

Next steps

After the first transfer, check objects with known dimensions, the scene hierarchy, and any surfaces that need to be visible from both sides. If you are targeting static lighting, review the lightmap UVs and material behavior separately. If you are using lightmap UV channels prepared in 3ds Max, refer to Epic’s Datasmith guide for 3ds Max. Also note that collision and physics settings are not added to static meshes by default; if needed, configure them in Unreal Engine after import.

Sources and licensing

This guide has been adapted into English from Epic Games documentation on the Datasmith import process and supported software and file types. Both sources are official Epic Games documentation, and the sources state that the licensing information is freely available.