Import

The CATIA V5 Reader and Writer are not able to process file paths comprising of wide characters

Root instance's color and transparency properties are not imported.

3D XML files are always assembly files. Thus, no graphical data can come from it using the Connect 3D XML Visualization Reader in the form of in-memory data.

Graphical data (like color, transparency) is currently only supported at part level; assembly level graphical data applied on part occurrence is not supported.

Export in XML Tessellation type is not supported.

• 3D XML files can store visualization data in two ways — Static Tessellation and XML Tessellation. 3D InterOp supports export of the visualization data in only Static Tessellation' type.

Transformation applied to part occurrence at assembly level is not supported.

Features such as Layers, Hidden or Suppressed Entities, and Groups are not supported.

Attributes such as Entity Names are not supported.

Free Points are not supported.

Only the highest LOD (Level of Detail) will be read or written.

InterOp does not read 3DXML file created with the "simplification" process in the 3DExperience platform. In 3DExperience, it is created using command/menu "New Content >>Types >> Physical Product Structure >>VOCSimplification" and save as a 3DXML file.

JT Big-Endian File Type Not Supported

The Reader does not support attributes such as layer and name from JT files.

The Reader does not support assembly instance level colors from JT files.

The Reader does not support Smart Topology Table, STEP BREP and AEC Shape segment types.

The Reader does not support ULP segment type from JT.

Assembly Cut

• Show/ No Show tool body attribute. By default the tool will be translated without the Show No-Show attribute.

• Linking from tool instance to the corresponding tool free body is not provided.

• Free body as targets is not supported.

• InterOp Connect supports the assembly cut feature applied on only first level instances. So if the assembly level cut feature is applied on occurrence entities with more than one level deep instance hierarchy, the output might not be correct.

Tool Body Used for "Cut"

• InterOp does not distinguish between the tool body and target bodies.

Limited Support for Assembly Attributes

• Translation of Hidden Attribute in assembly files is not supported.

• Translation of layer information in assembly files is not supported.

• Translation of NX layer category in assembly files is not supported.

• Single level suppressed instance is supported.

• When same sub-assembly definition is instantiated more than once and assigned different colors at each level, InterOp will translate the color combination of the first sub-assembly definition colors found. InterOp does not duplicate the same sub-assembly definitions if the sub-assembly is used multiple times.

Hole Feature

• The Hole name will not match the feature name in NX. For example, an NX feature name in a feature tree may have the name SIMPLE HOLE (3), however, InterOp will output the name as SIMPLE HOLE (1).

• Hole top face information is not supported.

• Pattern of Hole feature is not supported.

Lattice Feature

• Mixed geometry created by the application of the Lattice feature is not supported. When a Lattice feature is applied on the design body, it creates a mixed geometry and hence, InterOp cannot give any output in this case.

Rate Unit

• Rate Unit cases are not supported

Datum Target

• Non-semantic Datum Target without datum reference is not supported.

• Semantic Datum Target Type Arbitrary Shape is not supported.

Name Attribute for Sketches

• As for sketches, the name attached to a sketch is not translated, but the name attached to the curve or point of a sketch will be translated.

User Defined Attributes

• For user defined attributes in NX having a "number" type, the values are converted/scaled to NX file units.

• Units are not given for "number" type user defined attributes.

• From NX 1953, the angle data type will be only in radians.

• Category is not translated if the value is given through a referenced text editor. Examples of the different types of categories in a user defined attribute such as "Materials" are shown in the User Defined Attributes section.

• Feature level user defined attributes are not supported. Also user defined attributes are not supported for free parts in NX assembly.

• Reference Set level UDA is not supported.

• In Assembly UDA, only the Assembly Definition level UDA is supported. If UDA is attached to any of its instances, then that is not supported.

Material Properties

• If a material property has multiple values, then only the first value in the table is given as the value for that property.

• In material properties, only the Unit systems available in an NX Modeler are supported. Custom Unit systems are not supported.

Facet Body

• NX files can have only visualization data and not BREP data for some bodies. These bodies are seen as "Facet Body" in the NX modeler. Currently InterOp does not export visualization data for such bodies.

Captures

• Currently Captures and Annotation Views are supported from version NX 7.5 and later.

• Clipping plane is not supported in both graphical nor semantic.

• Captures of linked Model view are not supported.

• Captures of sheet views are not supported.

• Capture sets are not honored. Hence, all model views in a "Capture Set" are normal independent Captures.

• Shading settings are not supported.

• Captures will not be translated if there are no PMI entities in the input NX file.

• Sub-Assembly level captures are not supported.

Work Plane Support

• The Name attribute for work planes is supported from NX 8 and later files.

Symbolic Thread Feature

• Symbolic threads name attribute will not match with NX Modeler.

• The Bottom type and Limit face of thread features are not supported.

Datum Axis Support

• Datum axis is supported from NX 12 and later files.

• Datum Axis is not supported in Connect Parasolid.

Product structure:

• Flexible Assemblies information is not supported. Instance specific transformation will not be read from flexible components. This means that positioning or sizing of imported flexible components may be incorrect.

• Table information is not supported. This means that positioning or sizing of imported components may be incorrect.

• Component Pattern is not supported. Pattern information will be missing and underlying definition will not be processed. Product Structure for Component Pattern will be incorrect.

• Constraint-based positioning of instances is not supported. If constraints are used to determine the final position of an instance or any of its components in an assembly, the resulting placement may be inaccurate, as 3D InterOp currently does not read positions after constraint resolution.

Product structure properties

• Instance-level visibility (hide/show) information is not imported from Inventor assemblies using 3D InterOp.

• Suppression is only imported from the first level deep instances in Inventor assemblies.

• If a component in the assembly is replaced, its persistent name will change. This behavior is different from other CAD formats like SOLIDWORKS, where the persistent name of even replaced components stays the same.

BRep

• Free curves and free points are not imported.

• Entities created using advanced Inventor operations such as lofting, are not imported.

• Entities created using Advanced Inventor Environments such as Tube & Piping, Cable & Harness, Weldments etc., are not supported.

BRep properties

• Names of bodies in Inventor will not be imported.

• Color property is imported from Inventor version 2012 and later files.

• Color property is not supported for import from files created in a local, non-English version of the Inventor application.

• Body Level color is not supported in Inventor; instead, it is propagated to each of the individual faces.

• Entity level names are not supported.

• 3D InterOp may misread a color for Entities with multiple color attributes. For example, when both Face color and Document level face color are modified for a part and then that part is used as a base part in a derived part, then the derived part will get a face with multiple color attributes.

• Persistent names of topology edited in a different version of Inventor may not remain persistent. For example, an Inventor file created in Inventor 2014, if edited in Inventor 2015 may result in updated persistent names of topology, thus rendering this functionality useless.

• Persistent Name is not unique; for example, two different faces or laminar edges may have the same Persistent Name.

Global

• Alpha, Beta, and PR versions (even of supported official versions) are not supported. Thus, for example, although the SOLIDWORKS 2014 version is supported, however, SOLIDWORKS 2014 beta version is not supported.

• Import of SOLIDWORKS 2015 and later version files is only supported on 64-bit arches.

• No support for TranslateHiddenEntities option for versions earlier than SOLIDWORKS 2009.

• No support for Transparency for versions earlier than SOLIDWORKS 2011.

• No support for translation of coordinate systems, axis, free curves, or free points.

• No support for external referenced features.

• For much older versions (such as 2005) assembly files in Linux, product structure cannot be read completely.

Product structure

• Changes to sub-assembly not reflected in parent assembly unless rebuilt and saved
  After modifications to a sub-assembly, the parent assembly must be rebuilt and saved to correctly reflect the modifications.

• No configuration support for assemblies and sub-assemblies for versions prior to Sw98
  Configuration support is present for version Sw98Plus through the latest and currently supported SOLIDWORKS version.

Properties

• Root instance's, 2014_block_Cylinder_MainAsm node in the above example, color and transparency properties are not imported by 3D InterOp.

Document Information

• Unit information in files of version earlier than 2001 is assumed to be meters.

• Non-standard Units such as angstroms and feet & inches (this is different from the unit feet and the unit inches, both of which are individually supported) are not supported and are assumed as meter.

BRep

• Suppressed bodies do not get imported.

• Free points do not get imported.

• External referenced features are not supported.

• Workplanes are not supported for InterOp ACIS and InterOp Parasolid workflows.

Polyhedral

• not supported

BRep properties

• The default body name — Boss-Extrude2 — is supported from SOLIDWORKS 2023. If the body name has been updated under "Solid Bodies" as shown in the picture above, the body name is considered a user-modified body name. If the body name is modified in any other place in the feature tree, the default body name is imported.

• Translation of "Secondary Color" of materials are supported and the translation of "Dominant Color" of materials is not supported for SOLIDWORKS 2021 or earlier versions files.

• Transparency values are not supported when the file is created using the Make Multibody Part in SOLIDWORKS 2024.

• Persistent Name is not unique; for example, two different faces or laminar edges may have the same Persistent Name.

Global

• For any facet having more than three vertices, the output result is unpredictable.

• Does not import layer data from STEP files.

• Does not import selection set data from STEP files.

• 
  

User properties

• does not import part-level user properties.

• User properties of external references (for example, CATIA V5) in the STEP file may not get imported.

External References

• User properties of external references (for example, CATIA V5) in the STEP file may not get imported.

Free Parts

• Assembly features in STEP files are not supported for import using 3D InterOp

• Hidden assembly instances are not supported for import.

3D InterOp only imports FBX nodes with attribute FBXMesh. All other nodes are ignored.

Animations are not imported. If an FBX file has animations, visualization data representing the first frame is imported.

All data is triangulated upon import. FBX model may contain polygons other than triangles.

Black color on facets is not imported.

Since STL files do not explicitly save units, 3D InterOp assumes unit of measurement from STL files as millimeter, always.

The 3D InterOp STL Writer does not support handling Mirror Transform; Mirror Transform is a non-rigid body transform (it changes handedness) and so it is technically not valid as a product structure instance transform.

BRep transparency is not supported for import.

Layers are not supported.

Origin shift cor-ordinates are not imported. If geometry in the IFC file is located outside a valid range, then this data will be shifted after import to lie within the valid range.

Mapping data import is not supported for IFC files.

Monolithic assemblies introduced from Creo 8.0 are not read by 3D InterOp. Monolithic refers to a single file holding all the data required to define the assembly. These are also known as "Inseparable Assemblies".

Root instance's, color and transparency properties are not imported by 3D InterOp.

Properties with Unicode characters are not supported.

Support is limited to Creo Parameters at Assembly and Part level. Other user properties defined as Feature, Quilt, Surface, Edge, Curve, Composite-curve, Material, or Annotation levels are not supported for import.

Creo Reader does not support electrical harness data like piping or cables in any form (that is, in B-rep or visualization).

Suppressed bodies do not get imported.

In the case of a Creo model that has a lump with multiple shells (lump with void), 3D InterOp CGM will import this a multiple bodies, one per shell of a lump.

3D InterOp ACIS and 3D InterOp Parasolid may not import models with multiple lumps or lumps with multiple shells (lump with void) as expected in complex B-rep scenarios.

3D InterOp imports cosmetic surfaces of cosmetic threads and standard hole threads as regular sheet bodies. There is no easy way to filter these surfaces.

Body Name is not imported. Instead, it will be assigned the Part Name after import.

Visibility (hide/show) of Merge features may not get imported correctly.

Visibility (hide/show) of a Solid that has been added to a Layer by a SolidGeom filter is not supported.