Wherever possible, we recommend taking advantage of this by using instances in 3ds Max for all repeating elements in your scene (such as windows, doors, or chairs). This is typically better for the runtime memory requirements and performance of your Project, and it helps you manage your content by keeping the number of Static Meshes down. It then places multiple instances of that Static Mesh into the Level in Unreal. When Datasmith detects multiple instances of the same master object in your 3ds Max scene, it only creates one Static Mesh Asset for that object. For more information on this setting, see the 3ds Max Help. For these kinds of objects, 3ds Max allows you to customize the granularity of the tessellation that it uses when rendering in a viewport in its Viewport Display Settings > Mesh Quality Presets setting: Coarse, Medium, or Fine:ĭatasmith respects the level of tessellation you set here for each Body Object in the scene. The exception to this rule is 3ds Max Body Objects, where Datasmith bases the geometry of the Static Mesh Asset on the 3ds Max viewport mesh instead of the render mesh. That means that your Assets in Unreal will typically have exactly the same triangles as you see in 3ds Max renderings. In most cases, Datasmith uses each 3ds Max object's render mesh to create the geometry for the corresponding Static Mesh Asset in Unreal.

This section describes what's special about the way Datasmith converts geometric objects from your 3ds Max scene into Static Mesh Assets and Actors in your Unreal Engine Project. To read more about other types of Datasmith workflows, see Datasmith Supported Software and File Types.

3ds max models