Is this page helpful?

CAD Converter 209.0.0#

Release Date: March 2026

Converter Versions Included:#

  • omni.kit.converter.cad = {version = 209.0.0}

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

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

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

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

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

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

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

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

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

Changed#

  • [CAD Converter] Improved and expanded the advanced converter options UI with better organization and more configurable parameters exposed directly in the interface.

  • [CAD Converter] Added performance metrics logging to track conversion timing profiling and diagnostics.

  • [CAD Converter] Added HTTP endpoints to omni.services.convert.asset and omni.services.convert.cad for programmatic conversion management. Updated Overview.md documentation with endpoint paths, response codes, JSON formats, status values, and environment variables.

  • [CAD Converter] Conversion log files now use unique names per job to prevent overwrites during concurrent conversions.

  • [CAD Converter] Renamed DiagnosticLogConsumer to BackendLogConsumer and added CoreExtLogConsumer to capture and surface log output from core extensions running in subprocesses.

  • [DGN Converter] Updated ODA Kernel and Drawings SDKs to version 27.1.

  • [HOOPS Converter] Updated HOOPS Exchange SDK to version 2026.1.

  • [HOOPS Converter] Skip suppressed product occurrences during conversion.

Fixed#

  • [HOOPS Converter] Added support for JT Active Layer Filtering to control visibility of hidden geometry. This resolves the known issue where hidden elements in JT models could incorrectly appear as visible in converted output.

Known Limitations#

  • The following DGN element types are unsupported currently in the DGN Converter:

    • OdDgCellHeader2d

    • OdDgAnnotationCellHeader2d

    • OdDgAssocRegion2d

    • OdDgDetailingSymbolCellHeader2d

    • OdDgTitleText2d

    • OdDgSectionMarker2d

    • OdDgArrowMarker2d

    • OdDgDetailMarker2d

    • OdDgOle2Frame2d

    • OdDgShape2d

    • OdDgShape3d (hole)

    • OdDgComplexShape (hole)

    • OdDgTextNode2d

    • OdDgTextNode3d

    • OdDgText2d

    • OdDgText3d

    • OdDgCurve2d

    • OdDgCurve3d

    • OdDgComplexString

    • OdDgConic2d

    • OdDgConic3d

    • OdDgPointString2d

    • OdDgPointString3d

    • OdDgDimension

    • OdDgDimSizeArrow

    • OdDgDimSizeStroke

    • OdDgDimSingleLocation

    • OdDgDimStackedLocation

    • OdDgDimAngleSize

    • OdDgDimArcSize

    • OdDgDimAngleLocation

    • OdDgDimArcLocation

    • OdDgDimAngleLines

    • OdDgDimAngleAxisX

    • OdDgDimAngleAxisY

    • OdDgDimNote

    • OdDgDimLabelLine

    • OdDgDimRadius

    • OdDgDimRadiusExtended

    • OdDgDimDiameter

    • OdDgDimDiameterExtended

    • OdDgDimDiameterParallel

    • OdDgDimDiameterPerpendicular

    • OdDgDimCustomLinear

    • OdDgDimOrdinate

    • OdDgDimCenter

    • OdDgMultiline

    • OdDgTagElement

    • OdDgRasterHeader2d

    • OdDgRasterHeader3d

    • OdDgRasterComponent

    • OdDgRasterFrame

    • OdDgSectionClip

    • OdDgKMLPlacemark2d

    • OdDgKMLPlacemark3d

  • 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 be or how much memory is required. In most cases, we recommend a minimum of 16 GB. Complex files will need a minimum of 32 GB of memory available for conversion.

  • PMI and BIM data is not converted for the following formats: .dgn, .jt, .fbx, .obj, .gltf, .glb, .ply, .lxo, .md5, .e57, and .pts.