The 3D ACIS® Modeler (ACIS) is Spatial’s prominent 3D solid modeling engine. 3D InterOp is a CAD data translation framework (Interoperability)

From DocR20

This Release Notes document contains information about additions and changes to the InterOp software and documentation set for the 3D InterOp R20 release.

Spatial does not guarantee that an operation on an object in InterOp will have the same result from release to release.

Updates occurring after a major release of 3D InterOp are available in the service pack release notes. You can access service pack release notes at doc.spatial.com.

Release Notes R20

Enhancements and Functionality Changes

General

• Change in Default Value for Options Affecting BRep Translation

The default value has been changed from false to true for the following options that affect BRep translation. This change has been made for all applicable Reader and Writer components.

• TranslateFreeCurves
• TranslateFreePoints
• TranslateWorkPlanes
• TranslateSheetBodies

ACIS Reader/Writer Component

• Support for Extremities of Dimensions

The SPAXPMI_DIMENSION class has an interface for getting extremity points of dimensions. Refer to Retrieving Dimension Extremities for more details.

• Support for Importing Assembly PMI

The ACIS Writer imports PMI annotations created at assembly level in source assembly file. This is supported only in ACIS .asat or .asab assembly files. This is not supported in XML or flatten (.sat or .sab) route. Also, assembly PMI annotations attached onto workplanes or axis systems (local coordinate systems) of parts are not supported. Refer to the section Assembly PMI Annotations for more details.

• Support for Material Names

The ACIS Writer imports Material Names of bodies. Refer to the section Material Names for more details.

CATIA V4 Reader/Writer Component

• Deprecated Option: TranslateExtraEntities

The TranslateExtraEntities option has been deprecated and is no longer available.

CATIA V5 Reader Component

• Support for Extremities of Dimensions

The CATIA V5 Reader can export extremity points for ordinate and linear dimensions. Refer to Dimension Extremities in CATIA V5 for more details.

• CATIA V5 Toolkit Update

The CATIA V5 Reader has been updated with the CATIA V5 R19 toolkit.

• Support for Hidden Instances in Assembly

The CATIA V5 Reader exports hidden instances from CATIA V5 assembly. Refer to the section Assembly for more details.

• Support for Material Names

The CATIA V5 Reader now exports Material Names of bodies. Refer to the section Material Names for more details.

• Support for Translating Non-semantic Stacked GeomTol PMI

The CATIA V5 Reader translates non-semantic stacked GD&T PMI. Refer to the section Non-semantic Stacked GeomTol PMI for more details.

• Support for Translating Assembly PMI

The CATIA V5 Reader exports PMI annotations created at assembly level in CATProduct file. Assembly PMI annotations attached on workplanes or axis systems of CATPart files are not supported. Refer to the section Annotations in CATIA V5 for more details.

CATIA V5 Writer Component

• Replacing non-ASCII characters in File Names

When you specify non-ASCII characters to a new CATIA V5 file name, the CATIA V5 Writer will replace those non-ASCII characters with "_" (underscores). This feature is applicable to both Assembly and Part files. Refer to No Support for File Names with Non-ASCII Characters for more details.

• CATIA V5 Toolkit Update

The CATIA V5 Writer has been updated with the CATIA V5 R19 toolkit.

• Support for Hidden Instances in Assembly

The CATIA V5 Writer imports hidden instances from source assembly. Refer to the section Assembly for more details.

• Face Splitting Optimization

When a face's underlying surface is not continuous as per CATIA V5 requirements, CATIA V5 automatically splits that face and creates new faces according to its continuity requirements. In this release, face splitting while writing to a CATIA V5 file is optimized so that a fewer number of new faces are created after the split. Refer to the section CATIA V5 Writer BRep for more details.

IGES Reader/Writer Component

• Support for Reading IGES Files on Systems Running Under Non-English Locale

InterOp supports reading decimal data found in IGES files while running under a system locale whose decimal formatting rules differ from the English (United States) locale. Refer to Working with Localized File Paths for more details.

Inventor Reader Component

• Support for Inventor 2009 version

InterOp supports translation of Part and Assembly files of Inventor 2009 version. Refer to the section Limitations for limitations of Inventor 2009 support.

Parasolid Reader/Writer Component

• Support for Extremities of Dimensions

The Parasolid Reader/Writer includes an interface for returning extremity points of ordinate and linear dimensions. Refer to the section Dimension PMI for more details.

• New Option: DeepHealing

The DeepHealing option controls the healing of data that has performance-expensive errors. Its default value is false.

• Support for Material Names

The Parasolid Writer imports Material Names of bodies. Refer to the section Material Names for more details.

Parasolid Manufacturing Option

• Angular Dimension in Degree

The InterOp Parasolid Manufacturing Option returns the angular dimension value in degrees. In previous releases, the returned dimension value was in radians. Refer to Reference Angular Dimension for more details.

Pro/E Reader Component

• Support for Wildfire 4 Version

The Pro/E Reader supports reading Wildfire 4 version part and assembly files. Refer to Pro/E Version Support for more details.

• Removed Option: AllowNonmanifoldTopology

The option AllowNonmanifoldTopology has been deprecated beginning with R19 SP2 and removed in this release. Use TranslateSheetBodies instead.

• Support for Free Curves

The Pro/E Reader supports reading of free curves and wires. Refer to Support for Free Curves for more details.

Pro/E Manufacturing Option

• Support for Wildfire 4 PMI

The Pro/E Manufacturing Option supports reading PMI data from Pro/E Wildfire 4 files. Refer to Manufacturing Information for more details on Pro/E PMI support.

• Linear Dimension Extremities Support

InterOp Connect supports linear dimension extremities for Pro/E. Refer to the section Support for Linear Dimension Extremities for more details.

• PMI with No Leader

InterOp Connect behavior for translating PMI with no leader has changed. In previous releases, Connect would return a leader having coordinate (0,0,0) for head and tail points, but now correctly returns an empty leader list. Refer to Support for Pro/E PMI Display Information for more details.

SolidWorks Reader Component

• Support for Reading Unit of SolidWorks Part and Assembly Files

The InterOp SolidWorks Reader supports reading unit information from part and assembly files. Refer to Limited Support for Reading Units in Part or Assembly Files for more details.

• Support for Unicode in SolidWorks Reader

The InterOp SolidWorks Reader supports reading part and assembly files' paths having localized strings without setting the locale. Refer to Working with Localized File Paths for more details.

• Support for SolidWorks 2009

InterOp Connect supports SolidWorks version 2009. Refer to the section SolidWorks Reader for more details.

STEP Reader/Writer Component

• Support for Reading/Writing Localized Strings in STEP Files

The InterOp STEP Reader/Writer supports reading/writing localized strings in STEP files as described in Localized Text in STEP Files.

• Option Default Value Change: WriteAssemAsCtxtDepShapeRep

The default value of for the WriteAssemAsCtxtDepShapeRep option has changed to true. Refer to WriteAssemAsCtxtDepShapeRep for more details.

Unigraphics Reader Component

• Support for Extremities of Dimensions

The Unigraphics Reader can export extremity points for ordinate and linear dimensions. Refer to Limited Support for Dimension Line Extremities for more details.

• Support for Unicode

The InterOp Unigraphics Reader supports reading part and assembly files' paths having localized strings without setting the locale. Refer to Working with Localized File Paths for more details.

• Support for NX6 version

The Unigraphics Reader supports BRep, Assembly, and PMI data of Unigraphics NX6 version files. Refer to the section Limitations for limitations of Unigraphics.

Unigraphics Manufacturing Option

• Support for NX 6 PMI

The Unigraphics Manufacturing Option supports reading PMI data from NX 6 files. Refer to Manufacturing Information for more details on Unigraphics PMI support.

VDA-FS Reader/Writer Component

• Support for Reading VDA-FS Files on Systems Running Under Non-English Locale

InterOp supports reading decimal data found in VDA files while running under a system locale whose decimal formatting rules differ from the English (United States) locale. Refer to Working with Localized File Paths for more details.

XML E-BOM Reader Component

• Support for Writing "Visibility" and "Suppressed" Attributes

InterOp supports writing "Visibility" and "Suppressed" attributes to child nodes in XML assembly structures. These are optional attributes which are written only in case that "Visibility" has a value of false and "Suppressed" has a value of true. Refer to Support for Translation of Hidden Instances for more details.

• Support for Hidden Instances in Assembly

The XML E-BOM Reader exports hidden instances from XML assembly. Refer to the section Support for Translation of Hidden Instances for more details.

• Unit Support

The XML E-BOM Reader supports reading unit information from XML files. If there is no unit information in the XML file, then the millimeter unit is assumed. Refer to Unit Support for more details.

XML E-BOM Writer Component

• Support for Writing "Visibility" and "Suppressed" Attributes

This release supports writing "Visibility" and "Suppressed" attributes to child nodes in XML assembly structures,that is if the option "TranslateHiddenEntities" is set to 'true' then the hidden instances from the source assembly will be written to XML but with value of 'false' assigned to the attribute "Visibility". These are optional attributes which are written only in case that "Visibility" has a value of false and "Suppressed" has a value of true. Refer to Support for Translation of Hidden Instances for more details.

• Support for Unicode

The InterOp XML E-BOM Writer supports writing XML files with UTF-8 encoding. Beginning with this release, XML files will contain only UTF-8 encoding. Refer to Working with Localized File Paths for more details.

• Instance Files Are Written in Binary Mode

By default, the XML E-BOM Writer writes instance files in binary format. That is, a .sab file is generated for ACIS and .x_b is generated for Generic formats. The new option BinaryTargetDocument enables you to write the instance files in binary or text mode.

• Support for Hidden Instances in Assembly

The XML E-BOM Writer imports hidden instances from source assembly. Refer to the section Support for Translation of Hidden Instances for more details.

• Unit Support

The XML E-BOM Writer supports writing unit information to XML files. Refer to Unit Support for more details.

• Support for Mixed Mode Translation

The XML E-BOM Writer supports generating XML files which reference a Parasolid document. Refer to Support for Mixed Mode Translation for more details.

• Support for Missing Parts and Sub-assemblies

The XML E-BOM Writer supports missing parts and missing sub-assemblies information when translating from Pro/E and Unigraphics assembly files. Refer to Support for Missing Parts and Sub-assemblies for more details.

Platform Support

The supported platform details for the 3D Modeling and Visualization Product Suite are:

Microsoft Windows

Support for the Microsoft Windows operating system is provided using the following compilers, operating systems, and hardware configurations:

Products Compiled to 32-bit Multi-threaded Dynamic Libraries (DLL)

Products Compiled to 64-bit Multi-threaded Dynamic Libraries (DLL)

All other configurations of the Windows operating system, C++ compilers, and hardware are not officially supported.

Note: Spatial has been informed that when a customer application links against and initializes PHL V5, the Microsoft debug runtime reports leaks after their application exits. Spatial has examined these leaks and it is our assessment that:

• Microsoft generates their leak report when MFC is unloaded. If your application's library load/unload order causes MFC to be unloaded before the PHL V5 libraries, false memory leaks may be reported in PHL V5 libraries. Refer to Understanding False Memory Leaks Reported in ACIS-based MFC Applications for more details.
• There are memory blocks in the leak report that are true leaks. These are from allocations that take place in the PHL V5 libraries in static initialization and are never deallocated in static termination. These memory blocks are meant to "live" for the lifetime of the application session; failing to return them in static termination is not a serious issue, as the operating system reclaims that memory when the application exits. However, Spatial is working to resolve these leaks.

Red Hat Enterprise Linux

Support for the Red Hat Enterprise Linux operating system is provided using the following compilers, operating systems, and hardware configurations:

Products Compiled to 32-bit Shared Libraries (DLL)

Products Compiled to 64-bit Shared Libraries (DLL)

Note: You may need to install the following RPM package(s): libXmu-1.0.2-5 and libXmu-devel-1.0.2-5. This ensures that the correct libXmu libraries are installed on the system.

All other configurations of the Red Hat Linux operating system, C++ compilers, and hardware are not officially supported.

Hewlett-Packard HP-UX

Support for the Hewlett-Packard HP-UX operating system is provided using the following compilers, operating systems, and hardware configurations:

Products Compiled to 32-bit and 64-bit Shared Libraries

All other configurations of the Hewlett-Packard HP-UX operating system, C++ compilers, and hardware are not officially supported.

IBM AIX

Support for the IBM AIX operating system is provided using the following compilers, operating systems, and hardware configurations:

Products Compiled to 32-bit and 64-bit Shared Libraries

All other configurations of the IBM AIX operating system, C++ compilers, and hardware are not officially supported.

Sun Solaris

Support for the Sun Solaris operating system is provided using the following compilers, operating systems, and hardware configurations:

Products Compiled to 32-bit and 64-bit Shared Libraries

All other configurations of the Sun Solaris operating system, C++ compilers, and hardware are not officially supported.

Apple Macintosh

Support for the Apple OS X operating system is provided using the following compilers, operating systems, and hardware configurations:

Products Compiled to Intel 32-bit Shared Libraries

All other configurations of the Apple Mac OS X operating system, C++ compilers, and hardware are not officially supported.

End of Life Notifications

R20 is the last version for ACIS/InterOp binaries on HP-UX and Solaris platforms. Starting with R21, ACIS/InterOp binaries will not be provided for Hewlett-Packard HP-UX nor for SUN Solaris operating systems. Contact Spatial Support for any additional information.

Previous Release Notes

• InterOp Release Notes R19
• InterOp Release Notes R18

Installation Notes

The following sections explain the installation procedure for supported platforms and important post-installation information:

Note: The Spatial installation software does not need to be run separately for each Spatial product or supported platform. You may extract packages for both the 3D Modeling and Visualization Product Suite and the 3D InterOp Product Suite across multiple platforms into one directory and run the installer once. However, you must not extract UNIX and Windows packages into the same directory.

Digital Signatures

Spatial products on Windows Operating System with Microsoft Visual C++ 2005 compiler are now digitally signed for identification purposes. Digital signatures for Spatial products have been issued by VeriSign and recipients can use this to authenticate the identity of Spatial products.

Installing on Windows

1. Download the product ZIP file from http://www.spatial.com/downloads.
2. Extract the product ZIP file by double-clicking the file and specifying the desired installation directory.
3. Double-click the setup.exe file in the location specified in step 2.
4. At the Welcome screen, click Next to continue to the License Agreement screen. Select Yes to accept the license terms.
5. The next screen prompts you for the destination folder. Select the top-level directory of your InterOp installation. The installation then occurs in the selected location.

Important Runtime Installation Instructions for Windows

Note: The following instructions apply ONLY to customers who meet one or more of the following conditions:

• Build their application using the Microsoft Visual Studio .NET 2005 (SP1) compiler
• Use the CATIA V5 component with any Windows compiler

After you install your Spatial products, you must install the executable (for 32-bit or 64-bit) provided with your Spatial products installation package.

During the Spatial products installation process, two executable files are placed in a folder called redist, located in the Spatial products installation directory; for example:

<install_dir> \redist
.
.
.
              VC8\vcredist_x86.exe (32-bit)
              VC8\vcredist_x64.exe (64-bit)

where <install_dir> is the confirmed location of your Spatial products installation directory.

The following diagram depicts proper compiler and runtime configurations.

Note: The following instructions apply ONLY to customers who meet one or more of the following conditions:

• Build their application using the Microsoft Visual Studio .NET 2008 compiler
• Use any Parasolid component.

After you install your Spatial products, you must install the executable (for 32-bit or 64-bit) provided with your Spatial products installation package.

During the Spatial products installation process, two executable files are placed in a folder called redist, located in the Spatial products installation directory; for example:

<install_dir> \redist
.
.
.
              VC9\vcredist_x86.exe (32-bit)

where <install_dir> is the confirmed location of your Spatial products installation directory.

The following diagram depicts proper compiler and runtime configurations.

Installing on UNIX and Macintosh

1. Download the product TAR file from http://www.spatial.com/downloads.
2. Extract the product TAR file to the desired location.
3. Run the installation program iop_install.
4. At the first screen, review the details about navigating the installation program. Press <Enter> to continue with the installation process.
5. The License Agreement appears on the next screen. If you accept these terms and conditions, select Y and press <Enter>; otherwise, select N, and the program quits the installation process.
6. The last screen prompts you to verify the top-level installation directory <install_dir> where the product is to be installed. All products will be installed into this directory. After entering Y to confirm the location of the installation directory, the installation program completes the installation process.

Understanding False Memory Leaks Reported in ACIS-based MFC Applications

False memory leaks are reports of leaks by memory management systems that can be proven to be erroneous. In this case Spatial specifically refers to the leak reports generated by the Microsoft debug CRT when an ACIS-based MFC application exits.

Faulty leak reports are generated when the runtime library that was loaded last exits, not when the runtime library that was loaded first exits. In other words, the faulty leaks are reported when the first runtime library exits, not when the last one exits. (This is a bug that has been acknowledged by Microsoft.) Moreover, other libraries may be unloaded after the first runtime library exits. These other libraries may free memory when they unload, which is the case with ACIS libraries. These deallocations can occur after the leak report has already been generated, in which case they are incorrectly reported as leaks.

No faulty leaks are reported when all runtime libraries are loaded before other libraries during application startup. This desirable behavior can be achieved by managing link order and by managing the types of runtimes used by the application.

Libraries specified as additional dependencies in the project settings are loaded in the order specified before all other libraries. (This is referred to as "explicit linkage".) Adding the appropriate MFC runtime library to the beginning of the link dependencies should remove erroneous leaks in most cases. Additionally, you can load all libraries with the use of pragmas. This is the suggested way to link ACIS libraries into your application. (This is referred to as "implicit linkage".) From our experience, applications that link libraries implicitly are less likely to encounter faulty leak reports. Note that pragmas added to source code will, therefore, require project rebuilds.

Faulty leak reports can also occur when mixed versions of runtime libraries are loaded because of dependencies from other libraries. For example, a typical MFC application may use MFC80D.DLL and have dependencies on other libraries that use MFC80UD.DLL. The latter library may be loaded after other libraries have been loaded, specifically after ACIS libraries are loaded. This is a scenario for faulty leak reports since libraries are unloaded in reverse load order. This cannot be solved with explicit linkage because of link errors (such as multiply defined symbols) and mixed runtime issues. The best solution is to manage the types of runtimes used by the application by using the same ones whenever possible.

Licensing Information

Note: Application Licensing and Registration are supported on Windows operating systems only.

Use of this Spatial software and the associated documentation is governed by the license agreement between the parties. If you do not have such a written license agreement for this software, do not use this software or documentation. If you do not have a valid license, contact your sales representative or productsales_spatial@3ds.com to purchase a license.

Any use of this Spatial software or documentation without a valid license is illegal and is strictly prohibited.

=========================================================================
== NOTICE file corresponding to section 4(d) of the Apache License  ==
== Version 2.0, in this case for the Apache Xerces distribution.    ==
=========================================================================
This product includes software developed by
The Apache Software Foundation (http://www.apache.org/).
Portions of this software were originally based on the following:
- software copyright (c) 1999, IBM Corporation., http://www.ibm.com.
See the text file XERCES_LICENSE for the complete Apache License, Version 2.0.

^{© 2009 Spatial Corporation, a Dassault Systèmes S.A. company. All rights reserved.}

ACIS and SAT are registered trademarks of Spatial Corporation. All other names and products are trademarks of their respective owners.