Optimize your 3D models

Artikkel
07/13/2021
Lugemiseks kulub 2 minutit

For best rendering and best possible real-time performance, your 3D models need to be converted and might need to be optimized before using Microsoft Dynamics 365 Import Tool (Preview). Third-party applications that convert CAD files often have tools that can optimize content as well.

The following table lists software tools that you can use to convert and/or optimize your CAD files or intermediate files and export them as a supported file format. Your use of third-party applications is subject to terms between you and the third party. Microsoft does not endorse any particular third-party application and assumes no responsibility or liability for any third-party application you elect to use.

Software	Import	Export	Convert/transcode	Optimization
PiXYZ Software	STEP, Catia, JT, OBJ, FBX, and more	glTF 2.0 and more	Yes	Yes
Maxon Cinema 4D	SOLIDWORKS, STEP, Catia, JT, and IGES	FBX, OBJ, GLB/glTF 2.0 (beta)	Yes	Yes
Simplygon Studios	FBX, OBJ	FBX	No	Yes
Unreal Datasmith	STEP, Catia, JT, OBJ, FBX, and more	FBX, OBJ	Yes	No
Autodesk Inventor	STEP, Catia, JT, OBJ, FBX, and more	FBX, OBJ, STL	Yes	Yes
Blender	Collada (DAE), FBX, PLY, OBJ, STL, glTF, GLB, and more	FBX, OBJ, glTF 2.0, and more	Yes	Yes

Important

Dynamics 365 Guides uses meters as the default scale unit. If your 3D model scale is set to millimeters when you export from your CAD solution, the model will be converted to meters in Dynamics 365 Guides. For example, if your model is 50 millimeters, it will be converted to 50 meters. To ensure size consistency between your CAD solution and Dynamics 365 Guides, make sure to set your model scale unit to meters when you export.

Here are examples of CAD, converted, and optimized 3D models.

CAD	Converted to GLB	Optimized GLB

Original CAD file	52,000 triangles	9,000 triangles

Performance targets

The Dynamics 365 mixed-reality applications can be used on Microsoft HoloLens, immersive headsets, and mobile devices. The goal is to provide the highest possible visual fidelity without adversely affecting performance.

The following table lists some general conservative targets to aim for when acquiring or authoring 3D models for a range of hardware. When in doubt, target the midrange profile for a balance of fidelity and performance.

Device	Low-scene complexity	Medium-scene complexity	High-scene complexity
HoloLens	Objects: 1-3 per scene Triangles: <100,000 Materials: 1-2 per object	Objects: 4-10 per scene Triangles: <30,000 Materials: 1-2 per object	Objects: 10+ per scene Triangles: <10,000 Materials: 1-2 per object
Immersive headsets	Objects: 1-3 per scene Triangles: <15,000,000 Materials: 1-2 per object	Objects: 4-10 per scene Triangles: <500,000 Materials: 1-2 per object	Objects: 10+ per scene Triangles: <150,000 Materials: 1-2 per object
Mobile	Objects: 1-3 per scene Triangles: <500,000 Materials: 1-2 per object	Not applicable	Not applicable