In brief
- Datasmith automatically adjusts scene scale based on the units used in the source application.
- Epic’s supported software list includes 3ds Max 2016–2026 and an exporter plugin workflow.
- Single-sided geometry or reversed normals may make surfaces invisible from some angles in Unreal Engine.
- Lightmap UVs are generated for static meshes; physics is not set up by default.
Datasmith is a workflow for importing scenes from supported design applications into Unreal Engine. Epic’s documentation explains how scale is handled during import, how names and geometry are converted, and why visibility or lighting issues can arise in some cases. The steps below cover what to check when bringing in content from 3ds Max, Revit, SketchUp, and other supported applications. Application versions are based on the information in Epic’s supported software list.
1. Verify application and plugin support
First, check whether your source application is within the supported version range. Epic’s list gives 3ds Max 2016–2026, Revit 2016.3–2023*, Archicad 23–28, and SketchUp Pro 2019–2025. The 3ds Max and Archicad workflows use an exporter plugin; for SketchUp Pro, the list includes either an exporter plugin or the DirectLink option.
Enable the Datasmith importer plugin in your Unreal Engine project that matches the source application or file type. Epic’s support table specifies the required importer for each workflow, so don’t choose a plugin based only on the name of the source application.
Match the exporter plugin version to the Unreal Engine and Datasmith plugin versions you plan to use. Epic does not guarantee backward compatibility across all version combinations. Although it may be possible to open a
.udatasmithfile created with an older plugin in a newer Unreal Engine version, relying on this compatibility is not recommended.
| Setting | Recommended value | Effect |
|---|---|---|
| Exporter plugin | A version that matches the Unreal Engine and Datasmith plugin you’ll use | Helps reduce the risk of version incompatibility. |
| Scene units | The units used in the source application | Datasmith automatically adjusts the scale during import. |
| Geometry visible from both sides | Thickened geometry and outward-facing normals where possible | Helps prevent backfaces from becoming invisible. |
| Lightmap UVs | UV layout with no overlapping triangles | Keeps lighting and shadow information separate for each surface. |
2. Scale, names, and transforms
Prepare your source scene using the units you’re accustomed to. Although Unreal Engine expresses distances in centimeters, Datasmith converts the size and position of scenes built with other units. For example, an object that is 10 inches long in the source application is represented as 25.4 world units long in Unreal Engine. You don’t need to change the working units in the source application for the scale conversion.
Give scene objects meaningful names and keep the hierarchy organized. Datasmith attempts to use the names it finds in the source for imported assets and actors; however, the static mesh label in the Content Browser, the filename on disk, and the actor name in the level may differ. Asset files on disk must have unique names. If actors share a name, Unreal Engine may append numbers. Keep this naming difference in mind when managing assets with Blueprint or Python.
When non-uniform scale on parent objects is combined with custom pivot transforms, coordinate conversions may cause the scene to look different in Unreal Engine than it does in the source application. If this happens, try returning to the source scene and simplifying the transform hierarchy.
3. Check for invisible surfaces and lightmap issues
If a surface appears to be missing after import, inspect the model from different angles. Unreal Engine may cull triangles that face away from the camera. A surface being visible from the other side doesn’t necessarily mean the geometry failed to import; its normal may face the wrong way, or the model may have been made as single-sided geometry.
Where possible, model objects that need to be visible from all sides with thickness, and make sure the normals face outward. For a single-sided model that only needs to be visible from one direction, reversing the normal in the source application and reimporting the scene may help. Enabling the
Two Sidedproperty on the material also makes the surface render from both sides. However, with static or stationary lighting, both sides using the same lightmap space can cause visual artifacts.If the geometry is visible but light appears to pass through the object, consider the
Lighting > Shadow Two Sidedsetting in the Static Mesh Actor details. Changing face orientation in the Static Mesh Editor may be lost when the source scene is edited and the Datasmith Scene Asset is reimported. For a lasting fix, check the geometry in the source model as well.If you’re using static lighting, inspect the lightmap UVs. Datasmith adds two UV sets to imported static meshes and sets up the second one for lightmap data. If multiple triangles share the same UV space, lighting and shadow information may not be stored separately for each surface, which can lead to lighting errors. If you plan to use pre-authored lightmap UV channels in 3ds Max, refer to Epic’s Datasmith documentation specific to 3ds Max.
4. Lights, collision, and architectural visualization
Keep in mind that lights may not exactly match their counterparts in the source application after import. Datasmith converts lights in supported files to the appropriate Unreal Engine light types. Because some area and volume lights have no direct equivalent, certain lights may be represented by the custom
DatasmithAreaLightMeshBlueprint. This setup is used to create both the light’s visible surface and its lighting effect.Remember that physics settings are not added to static meshes by default. For interactive use, set up collision and physics in Unreal Editor after import. If you’re using 3ds Max, custom collision geometry can be modeled in the source application, and the Datasmith importer can automatically assign it to the Static Mesh assets it creates.
For architectural and interior design teams, these checks make it easier to understand the results of an import before a real-time presentation or scene review. In particular, check surfaces visible from both sides, UV layout for static lighting, and how imported lights are represented. If an office uses 3ds Max, Revit, or SketchUp, testing the workflow with a small sample scene can help identify plugin matching, scale, and visibility issues before moving on to a larger project.
Common mistakes
Assuming geometry failed to import because a surface is invisible; first check its normals and inspect the model from different angles.
Treating a
Two Sidedmaterial as a fix that always works; consider the possibility of visual artifacts with static or stationary lighting.Changing the source scene’s units because Unreal Engine uses centimeters; Datasmith converts the scale automatically.
Assuming different plugin and Unreal Engine versions are guaranteed to be compatible; match the versions.
Expecting physics to be set up automatically on static meshes; configure collision after import.
This guide is based on Epic’s documentation about the Datasmith import process and supported software. The support table states that most exporter plugins and the Datasmith importers in Unreal Editor are available on Windows. For macOS, it lists export support through SketchUp Pro 2019–2025, Archicad 23–28, and Rhino 6, 7, 8. According to the note in the Revit table, as of Unreal Engine 5.3, new Revit exporter plugins are managed by Autodesk, and the plugin is included with Revit 2024+.
Sources
2 sourcesSource texts are not republished; short quotes are marked, everything else is our own summary and commentary.
For architecture and visualization offices in Turkey, Datasmith’s practical benefit is that it makes it easier to bring a scene created in a design application into Unreal Engine. However, the result depends on how the source model is organized, the orientation of its surfaces, and whether plugin versions match. Static lightmaps and surfaces visible from both sides should be reviewed before a project presentation.
The source documentation doesn’t specify hardware requirements or license pricing, so cost and workstation assessments should be based on the software licenses and hardware already in use. Teams should agree on version compatibility at the start of a project and account for the fact that geometry changes made in the editor may not be preserved when reimporting.
Frequently asked questions
Which versions of 3ds Max does Datasmith support?
Epic’s supported software list includes 3ds Max 2016–2026. The listed workflow requires an exporter plugin.
Does Datasmith convert scene scale when importing into Unreal Engine?
Yes. Datasmith automatically adjusts scene scale even if the source application uses different units.
Are physics settings added to static meshes imported with Datasmith?
No. The documentation states that physics settings are not set up by default; collision and physics can be configured in Unreal Editor after import.



