InterOp:Release Notes

From DocR23

Jump to: navigation, search
edit  

Archive


Platform Support
InterOp

This service pack is a collection of new features and updates that fix issues reported against the InterOp R23 release and incorporates all of the InterOp R23 content.

Important: The service pack is stand alone and needs to be installed into a directory that does NOT contain prior releases.


This service pack is not a required upgrade; however, if you are currently running InterOp R23, we encourage you to download this service pack to ensure that you are running the most current, up-to-date version of InterOp.

Note: This InterOp service pack should be used with the same service pack level of ACIS.

Contents

Release Notes R23 SP2

IMPORTANT
This Service Pack is standalone and must be installed into a directory that does NOT contain prior releases.

Enhancements and Functionality Changes

Graphical Suite

  • Support for NX 8.5
InterOp's Graphical Suite now supports NX 8.5. However, PMI is not supported for NX 8.5.

ACIS Writer Component

  • Support for User Defined Attributes
The InterOp ACIS Writer component supports writing of User Defined Attributes. Refer to ACIS Writer User Defined Attributes for more details.
  • Support for Material Properties
The InterOp ACIS Writer component supports writing of Material Properties. Refer to ACIS Writer Material Properties for more details.
  • Support for Geometric Validation Properties
The InterOp ACIS Writer component supports writing of Geometric Validation Properties. Refer to ACIS Writer Geometric Validation Properties of Document and ACIS Writer Geometric Validation Properties of BREP for more details.

CATIA V5 Reader Component

  • Support for User Defined Attributes
The CATIA V5 Reader component supports translation of User Defined Attributes. Refer to CATIA V5 User Defined Attributes for more details.

CATIA V5 Reader/Writer Component

  • Support for CATIA V5 R23
The CATIA V5 Reader/Writer component supports importing and exporting CATIA V5 R23 parts and assemblies on Windows platforms only. Refer to Format and Version Support for more details.

Inventor Reader Component

  • Support for Material Properties
The Inventor Reader component supports translation of Material name and Material properties from Inventor files. Refer to Inventor Material Properties for more details.

NX Reader Component

  • Support for User Defined Attributes
The NX Reader component supports translation of User Defined Attributes from NX files. Refer to NX User Defined Attributes for more details.
  • Support for Material Properties
The NX Reader component supports translation of Material name and Material properties from NX files. Refer to NX Material Properties for more details.
  • Support for NX 8.5
The NX Reader component supports version NX 8.5 for only BREP and Assembly. PMI is not supported for NX 8.5. Refer to NX Reader for more details.

NX Direct Reader Component

  • Support for User Defined Attributes
The NX Direct Reader component supports translation of User Defined Attributes. Refer to NX Direct User Defined Attributes for more details.
  • Support for Material Properties
The NX Direct Reader component supports translation of Material name and main Material properties. Refer to NX Direct Material Properties for more details.
  • Support for NX 8.5
The NX Direct Reader component supports version NX 8.5 for only BREP and Assembly. PMI is not supported in NX 8.5. Refer to NX Direct Reader for more details.

Parasolid Writer Component

  • Support for User Defined Attributes
The InterOp Parasolid Writer component supports writing of User Defined Attributes. Refer to Parasolid Writer User Defined Attributes for more details.
  • Support for Material Properties
The InterOp Parasolid Writer component supports writing of Material Properties. Refer to Parasolid Writer User Material Properties for more details.
  • Support for Geometric Validation Properties
The InterOp Parasolid Writer component supports writing of Geometric Validation Properties. Refer to Parasolid Writer Geometric Validation Properties of Document and Parasolid Writer Geometric Validation Properties of BREP for more details.

Pro/E Reader Component

  • Support for Material Properties
The Pro/E Reader component supports translation of Material Properties. Refer to Pro/E Material Properties for more details.

STEP Reader Component

  • Support for Geometrical Validation Properties
The STEP Reader component supports translation of Geometrical Validation Properties from a STEP file. Refer to STEP Reader Geometric Validation Properties for more details.


Resolved Issues

For any issues you have submitted, log into the Downloads area at the Spatial Web site to check their status.

Documentation

For a complete listing of new and updated technical articles, refer to:

Platform Support

R23 GA Release Date: July 2012

Compiler Build Tested OS Processor
Microsoft Windows

Microsoft Visual C++ 2005 SP1 32-bit
Microsoft Visual C++ 2005 SP1 64-bit
Microsoft Visual C++ 2008 SP1 32-bit
Microsoft Visual C++ 2008 SP1 64-bit
Microsoft Visual C++ 2010 32-bit
Microsoft Visual C++ 2010 64-bit

Windows XP Professional 32-bit SP3
Windows XP Professional 64-bit SP2
Windows Vista 32-bit and 64-bit SP2
Windows 7 32-bit and 64-bit

x86-64
Red Hat Enterprise Linux1
GNU C++ gcc 4.1.2 32-bit
GNU C++ gcc 4.1.2 64-bit

Red Hat Enterprise Linux Version 4.0 Update 7
Red Hat Enterprise Linux Version 5.0 Update 1

x86-64
IBM AIX
VisualAge C++ Professional Version 10.1 32-bit
VisualAge C++ Professional Version 10.1 64-bit 		AIX Version 6.1 (TL02) RS/6000
Apple Macintosh
gcc version 4.2.1 compiler 64-bit OS X 10.7 Intel-based Macintosh

1 Linux is built on RHEL4.0 Update 7 and links to glibc 2.3.4-2, thus the minimum OS for runtime is RHEL4.0.

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. Refer to Understanding False Memory Leaks Reported in ACIS-based MFC Applications for more details.


End of Life Notifications

R23 is the last version that supports gcc 4.1.2, RHEL 4.0 OS, and VS 2005 for Windows OS. Contact Spatial Support for any additional information.


Platform Support for 3D InterOp Products

The following table illustrates supported platforms for the 3D InterOp products.

InterOp Product Platform Matrix
Products (Packages) intel_a
(Windows VS 2008)		 Windows 32
VS 2005, 2008 & 2010 		win_b64
(Windows x64 VS 2008) 		Windows x64
VS 2005, 2008 & 2010 		IBM 32 Linux 32 Linux 64 Mac 64
3D InterOp Connect (Trans Pkg)
ACIS CATIA V4 Reader/Writer X X X X X X X X
ACIS IGES Reader/Writer X X X X X X X X
ACIS Inventor Reader X X X X
ACIS Parasolid Reader/Writer X X X X X X X X
ACIS Pro/E Reader X X X X X X X X
ACIS Pro/E Manufacturing Option X X X X X X X
ACIS STEP Reader/Writer X X X X X X X X
ACIS NX Reader X X X X X X X
ACIS NX Manufacturing Option X X X X X X X
ACIS VDA-FS Reader/Writer X X X X X X X X
Generic CATIA V4 Reader/Writer X X X X X X X
Generic IGES Reader/Writer X X X X X X X
Generic Inventor Reader X X X X
Generic Pro/E Reader X X X X X X X
Generic Pro/E Manufacturing Option X X X X X X X
Generic STEP Reader/Writer X X X X X X X
Generic NX Reader X X X X X X X
Generic NX Manufacturing Option X X X X X X X
Generic VDA-FS Reader/Writer X X X X X X X
CATIA V5 Reader/Writer (CATIA V5 Pkg)
ACIS CATIA V5 Reader X X X X
ACIS CATIA V5 Writer X X X X
ACIS CATIA V5 Manufacturing Option X X X X
Generic CATIA V5 Reader X X X X
Generic CATIA V5 Writer X X X X
Generic CATIA V5 Manufacturing Option X X X X
SolidWorks Reader (SolidWorks Pkg)
ACIS SolidWorks Reader X X X X
Generic SolidWorks Reader X X X X
Direct Translators (Direct Pkg)
ACIS Parasolid Direct Reader X X
ACIS SolidWorks Direct Reader X X
ACIS NX Direct Reader X X
Graphical Translators (Graphical Pkg)
Graphical Suite X X
3D InterOp CGM
CGM Suite X X

Note: Beginning in R24, the intel_a and win_b64 environments on which 3D InterOp Graphical and 3D InterOp Direct are provided will be built with Visual Studio 2010 (VC10) instead of Visual Studio 2008 (VC9).

Note: CSDK requires other components for its use. Supported platforms are limited by its components.

Note: For information about supported platforms for the 3D InterOp CGM and 3D InterOp Graphical product lines, refer to 3D InterOp Graphical Platform Support. For information about supported versions and formats, refer to 3D InterOp Connect Format and Version Support.




Downloading the Service Pack

To download this service pack:

  1. Go to the Spatial Downloads Center.
  2. Log in with your Customer ID and Password at this screen.
  3. At the next screen, select the service pack you want to download from the drop-down list box.
  4. Download the 3D InterOp Products service pack applicable to your platform and operating system.

Installing the Service Pack

The following sections explain the installation procedure for supported

IMPORTANT
Service Packs are standalone and must be installed into a directory that does NOT contain prior releases.

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.


Installing on Windows

To install the service pack on Windows:

  1. Download the product ZIP file.
  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.
    1. To install multiple products simultaneously, extract the install files to a single location and double-click setup.exe.
  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 an empty folder to contain your InterOp installation. The installation then occurs in the selected location.

Installing on UNIX and Macintosh

To install the service pack on UNIX or Macintosh:

  1. Download the product TAR file.
  2. Extract the product TAR file to the desired location.
  3. Run the installation program iop_install.
  4. The first screen displayed contains information for navigating the installation program. After reading this screen, press <Enter> to continue the installation program.
  5. The next screen displays the license agreement. If you accept these terms and conditions, enter Y and then press <Enter>. If you do not accept these terms and choose N, the program quits the installation process.
  6. The last screen prompts you to verify the InterOp installation directory, <install_dir>, where the product is to be installed. Enter Y to confirm, and the installation program completes the installation process.

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 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 an empty folder to contain 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:

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\InstallDSSoftwareVC9Prerequisites_x86.msi (32-bit)
              VC9\InstallDSSoftwareVC9Prerequisites_x86_x64.msi (64-bit)

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

Important: Install the VC9 runtimes globally in your system's WinSxS directory (typically C:\WINDOWS\WinSxS) by using the .msi file in the redist folder. Choose either InstallDSSoftwareVC9Prerequisites_x86.msi for your 32-bit system, or InstallDSSoftwareVC9Prerequisites_x86_x64.msi for your 64-bit system.


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 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 run-times 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 run-times 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.

© 2012 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.

Xerces License

=========================================================================
== 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.

ICU License - ICU 1.8.1 and Later

COPYRIGHT AND PERMISSION NOTICE

Copyright (c) 1995-2006 International Business Machines Corporation and others

All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder.

All trademarks and registered trademarks mentioned herein are the property of their respective owners.

Retrieved from "http://doc.spatial.com/index.php/InterOp:Release_Notes"
Personal tools