CAD Converter

1.0 Overview

1.1 Introduction

The CAD Converter extension (omni.kit.converter.cad) depends on the HOOPS, DGN, and JT extensions for conversion from many common CAD file formats to USD.

1.2 System Requirements

To run Omniverse Kit and Omniverse Kit Apps, users must follow the below technical requirements.

Driver Version Requirements:

Driver Version Support	Windows	Linux
Recommended	537.58 (GameReady, Studio), 537.70 (RTX/Quadro, Grid/vGPU)	535.129.03 (GameReady, Studio, RTX/Quadro, Grid/vGPU)
Minimum	537.58 (GameReady, Studio), 537.70 (RTX/Quadro, Grid/vGPU)	535.129.03 (GameReady, Studio, RTX/Quadro, Grid/vGPU)

Suggested Minimums by Product:

Product	Supported Operating Systems	Min CPU: (intel/amd)	Min Ram	Min GPU	Min Disk
Kit	Windows 10/11 Ubuntu 20.04/22.04 CentOS 7	Intel i7 Gen 5 AMD Ryzen	16GB	GeForce RTX 3070	250GB
USD Presenter USD Composer USD Explorer	Windows 10/11 Ubuntu 20.04/22.04 CentOS 7	Intel i7 Gen 5 AMD Ryzen	16GB	GeForce RTX 3070	250GB

Please consult Omniverse documentation for details on technical requirements: https://docs.omniverse.nvidia.com/materials-and-rendering/latest/common/technical-requirements.html

1.3 Formats and Features Supported

The following file formats are supported by CAD Converter:

• CATIA V5 Files (*.CATPart, *.CATProduct, *.CGR)

• CATIA V6 Files (*.3DXML)

• IFC Files (*.IFC, *.IFCZIP)

• NX - Unigraphics Files (*.PRT)

• Parasolid Files (*.XMT, *.X_T, *.X_B, *.XMT_TXT)

• SolidWorks Files (*.SLDPRT, *.SLDASM)

• STL Files (*.STL)

• ACIS Files (*.SAT, *.SAB)

• Autodesk Inventor Files (*.IPT, *.IAM)

• Autodesk 3DS Files (*.3DS)

• AutoCAD 3D Files (*.DWG, *.DXF)

• Creo - Pro/E Files (*.ASM, *.PRT)

• Revit Files (*.RVT, *.RFA)

• Solid Edge Files (*.ASM, *.PAR, *.PWD, *.PSM)

• Step/Iges (*.STEP, *.IGES)

• JT Files (*.JT)

• DGN (*.DGN)

• OBJ Files (*.OBJ)

• FBX Files (*.FBX)

• 3MF Files (*.3MF)

• GLTF Files (*.GLTF, *.GLB)

NOTE: The file formats *.fbx, *.obj, *.gltf, *.glb, *.lxo, *.md5, *.e57 and *.pts are supported by Asset Converter and also available by default.

NOTE: If expert tools such as PTC Creo, Autodesk Revit or Autodesk Alias are installed, we recommend using the corresponding connectors. These provide more extensive options for conversion.

NOTE: CAD Assemblies may not work when converting files from Nucleus. When converting assemblies with external references we recommend either working with local files or using Omniverse Drive.

1.4 Known Issues and Unsupported

• Some DGN geometry data is not supported and will not convert USD mesh. If you have an example of such a DGN file, please let us know so we can troubleshoot and fix any remaining issues.

• Converting to USD can take more memory and CPU power depending on the type of data and Tessellation settings. File size is not an indicator of how fast a conversion will take or how much memory is required. In most cases we recommend a minimum of 16 GB. Complex files will need up to 32 GB of memory available for conversion.

• PMI and BIM data is not converted.

• Most properties are not converted to USD attributes.

We recommend converting Revit and Creo files using the Connectors instead of the CAD Converter for best results.

1.5 Getting Help

Enterprise Customers can report Omniverse issues here: https://www.nvidia.com/en-us/omniverse/enterprise/support/ Alternatively, uses can also report Omniverse issues on NVIDIA forums: https://forums.developer.nvidia.com/t/how-to-report-an-issue-with-omniverse/199675

2.0 Related Extensions

These related extensions make up the CAD Converter. This extension provides import tasks to the extensions through their interfaces. The DGN Core extension, however, is launched and provided configuration options through a subprocess to avoid library conflicts with those loaded by the other converters.

2.1 Converter Core Extensions

• Hoops Core: omni.kit.converter.hoops_core

• DGN Core: omni.kit.converter.dgn_core

• JT Core: omni.kit.converter.jt_core

2.2 Converter Wrapper Extensions

• Hoops GUI: omni.kit.converter.hoops

• DGN GUI: omni.kit.converter.dgn

• JT GUI: omni.kit.converter.jt

2.3 Converter Versions Included:

• omni.kit.converter.common = {version = 500.4.0}

• omni.kit.converter.hoops_core = {version = 501.3.0}

• omni.kit.converter.dgn_core = {version = 500.3.0}

• omni.kit.converter.jt_core = {version = 500.3.0}

• omni.kit.converter.hoops = {version = 501.3.0}

• omni.kit.converter.dgn = {version = 500.3.0}

• omni.kit.converter.jt = {version = 500.3.0}

• omni.services.convert.asset = {version = 500.2.0}

• omni.services.convert.cad = {version = 500.3.0}

2.3 Services

• Asset Converter Service: omni.services.convert.asset

• CAD Converter Service: omni.services.convert.cad

2.4 Utils

• Converter Common: omni.kit.converter.common

3.0 Usage UI/UX

The CAD Converter GUI extensions are available on builds of USD Composer, USD Explorer, and Isaac Sim. To obtain any of these Omniverse Apps, go to https://docs.omniverse.nvidia.com/launcher/latest/overview.html for steps to download and install the Omniverse Launcher. The Omniverse Launcher provides access and installs Omniverse Apps.

3.1 Omniverse Apps Import Functionality

To begin conversion of a CAD, open any one of these three Omniverse Apps. The user can then import the CAD file into Omniverse as a USD file through the File menu or through the Content window.

3.1.1 Import through the File menu

To import a CAD file into Omniverse, choose Import in the File menu. Use this method to import CAD Data into your scene - either by reference or directly into your stage.

3.1.2 Begin “Import” through the Content Window

By default the Content window is located at the bottom of the Omniverse App. It contains panels for showing a tree hierarchy of the user’s file system along with icon or list representation of the files in the currently open folder. If it is not shown, go to the toolbar, select “Window”, and then select “Content”. To convert a CAD file to USD, select the file in the Content window and choose Convert to USD in the context menu with right mouse button.

3.2 Selecting a File for Import

The user should now see a window similar to a file manager. The user needs to then select a CAD file for conversion from this window.

When a supported CAD file has been selected, the user should see a panel on the right-side of the window like below:

The user can change the options based on the file format. For details on conversion options, please consult the converter GUI extensions:

• Hoops GUI: omni.kit.converter.hoops

• DGN GUI: omni.kit.converter.dgn

• JT GUI: omni.kit.converter.jt

4.0 Kit Service

For setting up a Kit Service to run locally or Omniverse FARM, go to the Asset Converter Service extension: omni.services.convert.asset For setting up a Kit Service to run locally or Omniverse FARM, go to the CAD Converter Service extension: omni.services.convert.cad

5.0 Switching to a different CAD Converter Version

To switch to a different version of CAD Converters using the Extension Manager, you need to restart the application. Here’s how:

• Open the Extension Manager within the Omniverse Application (e.g., Isaac Sim App).

• Use the search bar to find omni.kit.converter.common.

  • Note: Disabling this extension will disable all CAD Converter extensions, as they all depend on it. Only one version of omni.kit.converter.common can be enabled, choose CAD Converter extensions that use the same version.

• Select the extension from the search results.

• Use the search bar to find omni.kit.converter.cad.

• Select the extension from the search results.

• In the extension menu, click on the three vertical lines icon.

• Choose the version you want to use. Instead of enabling it immediately, select Autoload.

• Close the Omniverse application and then reopen it.

• The selected version of the extension should now be active when you start the application.

6.0 Licensing Terms of Use and Third-Party Notices

The omni.kit.converter.cad and related CAD converter Extensions are Omniverse Core Extensions. Do not redistribute or sublicense without express permission or agreement. Please read the Omniverse License Agreements and the Third_Party_Notices.md for detailed license information.