ACIS Release Notes

From DocR25

Jump to: navigation, search


Platform Support

This ACIS Release Notes document contains R25 information about additions and changes to the ACIS software and documentation set for this release of the 3D Modeling and Visualization Product Suite.

Spatial does not guarantee that an operation on an object in the 3D Modeling and Visualization Product Suite will have the same result from release to release.

Sometimes information about a release becomes available after the 3D Modeling and Visualization Product Suite Release Notes have been published. Such updates are available to you as information bulletins on Spatial's Web site.


Release Notes R25

New Features in the 3D Modeling and Visualization Product Suite

This section describes new features in this release for these products:

  • 3D ACIS Modeler
  • 3D ACIS Exchange
  • 3D Viz Exchange

Add-on Solutions (separate licensing required)

  • 3D Deformable Modeling
  • 3D Mesh
  • 3D PHL V5
  • Advanced Covering
  • Defeaturing

R25 GA Release Date: July 2014

Package and Build Changes

This release includes platform changes, as well as package and build changes. Refer to the release notes below for a summary of changes. Or, for more details, refer to these comprehensive pages:

Deprecation Notices

In ACIS R25 some of the non-documented obsolete functionality has been proposed for deprecation. Refer to the article ACIS Anticipated Deprecations for details.

Platform and Compiler Changes

This release has the following platform and compiler changes.

Windows XP
Beginning with R24 SP2, Windows XP is no longer supported. Refer to the Platform Support Release Notes for a list of supported platforms.
Windows Vista
Beginning with R25, Windows Vista is no longer supported. Refer to the Platform Support Release Notes for a list of supported platforms.
Windows 8.1 64-bit
Beginning with R25, Windows 8.1 64-bit is now supported. Refer to the Platform Support Release Notes for a list of supported platforms.
Visual Studio 2008
Beginning with R25, Visual Studio 2008 is no longer supported. Refer to the Platform Support Release Notes for a list of supported platforms.
Beginning with R25, the Macintosh Clang 4.1 compiler is now used instead of the gcc compiler. Refer to the Platform Support Release Notes for a list of supported platforms.
CGM and Core InterOp DLLs Compiler update
Beginning with R25, the CGM and Core InterOp DLLs are now being built with VS 2012 instead of VS 2010. Refer to the Platform Support Release Notes for a list of supported platforms.
Arch Renames
Beginning with R25, the following arch names have changed for ACIS:
  • macos_a64 is now macos_b64
  • linux_so is now linux_a
  • linux_amd_64_so is now linux_a64

Note: Debug libraries are no longer available for UNIX platforms.

Packaging Changes

The packaging of ACIS and InterOp has been significantly simplified in this release. Notably, from the Spatial download site, you will encounter these changes:

  • Many of the packages have been combined to simplify your download/installation process. During installation, select the products for which you have a license.
  • Windows packages are in the form of self-extracting installers.
  • UNIX and Macintosh packages are in the form of TAR files and no longer have installers.

For more details, refer to the following technical articles:

Product Documentation Enhancements

In R25, a new mapping from ACIS API to Scheme Extension was added to the ACIS documentation. This compliments the extant reverse mapping from Scheme Extension to ACIS API.


New Functionality

Shadow Projection

This API determines the shadow cast by a set of solid, manifold bodies on a given plane. It assumes that light is coming from a point source at infinity and thus, the rays are parallel to each other. Note that api_make_shadow was introduced in R24 SP1.

Multiple Shadows of a Solid Have Been Cast


outcome api_make_shadow( ENTITY_LIST const& bodies,
			 plane const& projection_plane,
			 BODY*& shadow,
			 make_shadow_options const* opts = NULL,
			 AcisOptions const* ao = NULL );


(solid:shadow-project bodies plane-pos plane-normal [shadow-opts] [acis-opts])

For more details, refer to the technical article Shadow Projection and to the documentation of api_make_shadow and solid:shadow-project.

Subdivide Face

A new API api_subdivide_face has been introduced to subdivide a face along multiple iso-parametric curves. Based on the relevant options, the API api_subdivide_face can either make a wire-body representing the trimmed iso-parametric curves or split the face along those lines.


outcome api_subdivide_face( FACE *face,
			    face_subdivision const &subdivision,
			    subdivide_face_output_handle *&sfoh,
			    subdivide_face_options const *sfo = NULL,
			    AcisOptions const *ao = NULL  );


(face:subdivide face {{ u_param_list v_param_list } | { (cons (cons u_low u_high) no_of_u_div) (cons (cons v_low v_high) no_of_v_div) }} [ split_face ] [ ao ])

By default this functionality splits the face with the iso-parametric curves as specified by face_subdivision. You can opt to get a wire body instead of splitting the face through subdivide_face_options. The output of this API is either a wire body or list of split faces. The output is available through the argument sfoh, and the class subdivide_face_output_query provides interfaces to query the output.

For more details, refer to the article Subdividing Face along Multiple Iso-parametric Curves.

Split Wire Edges

A new API api_split_wire_edges has been introduced. This API splits edges of a given wire using the given positions. Note that api_split_wire_edges was introduced in R24 SP2.


outcome api_split_wire_edges( BODY* wire, 
			      SPAposition_vector const &points,
			      split_wire_options* swo = NULL,
			      AcisOptions const* ao = NULL );


(wire:split-by-points wire-body position-list [ao])

For more details, refer to Splitting Wire Edges Using a Set of Points.

Improved Functionality

Wire/Edge Projection

Projection APIs api_project_wire_to_body and api_project_edge_to_face have been enhanced:

  • To resolve self-intersections within a projected edge
  • To resolve improper intersections across multiple projected edges
  • To handle degenerate projections better, that is, when a curve gets projected into a point
  • To handle tolerant entities better

From R25, the projection APIs attempt to resolve self-intersections within a projected edge and improper intersections between multiple projected edges. It is important to note that the default behavior of these APIs has been changed in R25. In case these APIs are unable to resolve either self-intersections or improper intersections, they will fail. But the behavior can be customized using the function project_options::set_self_ints_behavior. The Scheme extension bool:proj-options has also been enhanced to control this behavior.

Refer to the article Projection for more details.

Near-tangent Interactions

Boolean operations have been enhanced to handle near-tangent scenarios better when blend surfaces are involved. From R25 Booleans can optionally use the tangent constraints posed by blend definition to make the operation succeed whenever possible. As this involves identification of blend faces locally during the operation, Booleans may require more computation time. You may specify that Booleans detect and resolve blend interactions by passing appropriate values to the function BoolOptions::set_detect_design_constraints.

For certain scenarios when it is evident that the operations may fail due to blends, Booleans may choose to use blend information by default.

When a Boolean operation determines that it has failed due to near-tangent blend interactions, then it will return appropriate error information as part of the outcome object. Refer to the article Boolean Error Information for more details.

Tolerant Interactions

Boolean operations has been enhanced in R25 to better handle certain scenarios of tolerant interactions that used to fail with the error MANY_VERTEX_TO_ONE or BODY_VERTEX_CRUMBLE.

Absence of Periphery Shell

Beginning with R25, Boolean operations such as Union, Subtraction, Intersection, and the non-regularized types of those operations can better support bodies with inner shells without a periphery shell. If a body does not have a periphery shell, then it must contain one single lump.

ACIS Checker

Enhanced Checks

Separation Loops

ACIS expects that separation loops on a face contain each other. Earlier to R25, the Entity Checker may not report certain genuinely insane scenarios. We have improved the check for separation loops in R25. If a face has separation loops that do not contain each other, then the Checker will report the message "face has loop with wrong orientation".

Inconsistent Closure

A new insanity has been introduced in R25 to identify the situation where the face topology is closed but the surface is open. The insanity is reported as an "error in face loop" with an additional message of "Face topology is closed and surface is open".


New Functionality

Make Wire from Formatted Text

A new API overload api_make_wire has been introduced that allows users to create an ACIS wire body from a given string and format. The format includes font name, properties, and height in modeling units.


outcome api_make_wire( const formatted_text &text,
		       BODY *&body,
		       make_wire_options *mk_opts = NULL,
		       const AcisOptions *ao = NULL );


(wire:from-text text font [height = 1.0] [bold = #f] [italic = #f])

For details, refer to the technical article Make a Wire Body from Text.

New API: api_fit_line

A new API api_fit_line has been introduced for fitting a line to a given set of points. Note that api_fit_line became available in R24 SP2.

The signature of the API is as follows:

outcome api_fit_line ( const SPAposition_vector & point_list,
		       straight &                    line,
                       fit_line_options *        flo = NULL,
		       const AcisOptions *        ao = NULL )

The Scheme extension for accessing the API is line:fit-from-points.

New API: api_fit_plane

A new API api_fit_plane has been introduced for fitting a plane to a given set of points. Note that api_fit_plane became available in R24 SP2.

The signature of the API is as follows:

outcome api_fit_plane (const SPAposition_vector & points,
		       plane &                    fitting_plane,
                       fit_plane_options *        fpo = NULL,
		       const AcisOptions *        ao = NULL )

The Scheme extension for accessing the API is plane:fit-from-points.

This API is an enhanced version of the function get_plane_from_non_planar_points which is no longer recommended for use.


Deprecated Functionality

Mesh Manager Member Functions

The following two member functions have been deprecated in R25. They will be removed from the MESH_MANAGER in a future release.

  • MESH_MANAGER::need_edge_grading_on_face
  • MESH_MANAGER::need_edge_grading

Feature Detection

New Functionality

New API: api_detect_match

A new API function, api_detect_match has been added to the Feature Detection suite. It helps detect matching entities of a given seed entity from set of candidate entities.

The signature of the API is as follows:

outcome api_detect_match( const ENTITY* seed,
			  const ENTITY_LIST& candidates,		
			  const match_filter_group& mfg,
			  ENTITY_LIST& matches,
			  detect_match_options* dmo = NULL,
			  const AcisOptions *ao = NULL

The Scheme extension for accessing the API is entity:detect-match. For more details, refer to the article Detection of Matching Entities.


Support for HOOPS 20.10 for Macintosh and Windows

HOOPS is supported on all Spatial platforms. ACIS is built with HOOPS 20.10 for Windows and Mac platforms. HOOPS 17.00 is supported for Linux platforms.


FileId Name Change

The name of the symbol FileId was changed to FileIdent in fileinfo.hxx because the name clashed with a symbol in Microsoft Windows. This name change affects the calling of api_set_file_info, which is required before calling api_save_entity_list. For example code demonstrating how to call api_set_file_info with this modified symbol, refer to Save and Restore Examples.

New Interface for Making a SPAtransf

The new function make_transf returns a SPAtransf when an affine transformation matrix and a translation vector are given.

SPAtransf make_transf(const SPAmatrix& affine, const SPAvector& translation);

SAT/SAB File Format Change

The header information in SAT/SAB files has been enhanced in ACIS R25 to include additional information about the originating system. The inclusion of this information in SAT/SAB files is controlled by the option originate_data.

History Callback Implementation Change

All history callbacks are now thread-specific.

New Interfaces Related to Error Information

The following new interfaces are related to i_aux_data_holder.

virtual size_t i_aux_data_holder::get_descriptions( char const **&desc ) const = 0;
virtual i_data_set_list const* i_aux_data_holder::get_elements( char const *desc ) const = 0;
virtual char const* i_data_element::description_str() const = 0;
virtual char const* i_data_element::type_str() const = 0;

Due to memory related issues, the respective overloaded functions using std::string have been proposed for deprecation. Refer to Anticipated Deprecations for details.

Local Operations

New Remove Faces Complexity

A new Remove Faces complexity has been added and can be reported by the API function, api_remove_faces. For additional information, refer to Remove Complexities.

Object Relationships

Entity Entity Distance

The Entity Entity Distance (EED) algorithm has undergone a code refactoring with focus on performance and robustness improvements. Now distance queries run on average between two and three times faster than before and for numerous test cases, better results are found. The performance difference between R24 and R25 is demonstrated in the two figures below.

The EED performance of R24 and R25 are compared. For every rotation (360 times 1 degree) of the blue body, its distance to the yellow body is computed. The red ray shows the closest points. For all distance queries, R24 and R25 take 16.661 and 7.247 seconds, respectively. This corresponds to a speedup of 2.3.
Behavior Change

The fact that for numerous test cases R25 gives better distance results is a behavior change. In these cases the distance between the two closest points will be smaller and the two closest points will be different. However, one property remains intact: if you were to point_perp from the closest point on one body to the other body, you would obtain the other closest point.

Physical Properties

Mass Properties

An alternative Mass Properties algorithm has been introduced as a fallback if the default Mass Properties algorithm fails. This causes no behavior change in non-failing cases.


New Behavior

From R25 onward, generating the stitching.log file can be controlled by the global option stitch_log. This applies to the interfaces api_stitch and api_stitch_nonmanifold.

Likewise, this behavior applies to the Scheme extensions entity:stitch, stitch:edges, and entity:stitch-nonmanifold.


New Functionality

A new API api_wrap has been introduced in R25. The API wraps a planar wire or sheet tool body on a target sheet or solid body such that distortion of lengths and angles is minimized.

Reference points and directions on the tool and target bodies together define a mapping between the target and tool bodies. The reference needs to be provided through wrap_orientation_ref.

The API can optionally embed the wrapped body in the target body or return a separate wire body. For best results, only the target faces on which the solution is likely to be wrapped should be provided. Giving more or fewer faces than needed can affect quality and performance.


outcome api_wrap( BODY* tool,
	          wrap_orientation_ref const &tool_ref,
	          ENTITY_LIST const &target_faces,
	          wrap_orientation_ref const &target_ref,
	          BODY *&wrapped_body,
	          wrap_options *opts = NULL,
                  AcisOptions const *ao = NULL )


(wrap:planar-body tool_body tool_ref target_faces target_ref [wrap_opts] [acis_opts])

For more details refer to the article Wrapping a Planar Body.

ACIS Extensions and Suites

3D Mesh


Upgraded VKI Mesher

The 3D Mesh component has been upgraded to use VKI's Devtools version 4.3.0. The improvements in this version include:

  • The performance and robustness of the surface mesh generation module was improved for both triangle and quadrilateral surface meshing.
  • The surface mesh generation module now supports the specification of a global chord height tolerance to control element sizing on curved surfaces.
  • The hybrid mesh generation module now supports automatic generation of pyramid elements to transition from quadrilateral boundary elements to interior tetrahedra.
  • A parameter was added to detect mapped meshable surfaces for both triangular and quadrilateral meshing.
  • The target edge length parameter used in tetrahedral mesh generation can now be specified for specific volumetric regions.
Surface Mesh Option Changes

Six new parameters have been added to the va_surface_mesh_options class. These parameters are described in Mesh Options.

  • EnableBackToBack – Specifies whether back-to-back surface elements are generated on internal ACIS faces.
  • EnableEdgeTangSize – Specifies whether the Maximum Spanning Angle parameter will be used for edge curvature as well as face curvature.
  • EnablePresNodeSize – Specifies whether short edge lengths are added to the size map.
  • MaxChordHeight – Specifies the maximum distance between a surface element and the input geometry.
  • MaxEdgeAltRatio – Specifies the maximum edge length to altitude ratio.
  • MaxAngle – Specifies the maximum interior angle.

The parameter EnableIntSurfBack has been deprecated in ACIS R25. It will be removed in a future release. Applications should use EnableBackToBack instead of EnableIntSurfBack.

Tet Mesh Option Changes

Two new parameters have been added to the va_tet_mesh_options class. These parameters are described in Mesh Options.

  • MaxAngle – Specifies the maximum interior angle.
  • MaxEdgeAltRatio – Specifies the maximum edge length to altitude ratio.
Localized Meshing Controls

In ACIS R24 localized meshing controls were added which allowed you to specify the target size of surface elements on an ACIS face, along an ACIS edge, or around an ACIS vertex. In ACIS R25 you can specify the target size of tetrahedral elements within an ACIS cell. An example demonstrating the use of this new functionality is presented in Localized Mesh Controls.


Support for HOOPS 20.10 for Macintosh and Windows

HOOPS is supported on all Spatial platforms. ACIS is built with HOOPS 20.10 for Windows and Mac platforms. HOOPS 17.00 is supported for Linux platforms.


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

Platform Support

R25 GA Release Date: July 2014

Compiler Build Tested OS Processor
Microsoft Windows

Microsoft Visual C++ 2010 32-bit
Microsoft Visual C++ 2010 64-bit
Microsoft Visual C++ 2012 32-bit
Microsoft Visual C++ 2012 64-bit
Microsoft Visual C++ 2013 32-bit
Microsoft Visual C++ 2013 64-bit

Windows 7 32-bit and 64-bit
Windows 8 and 8.1 64-bit

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

Red Hat Enterprise Linux Version 5.5 (Tikanga)
Red Hat Enterprise Linux Version 6.2 (Santiago)

Apple Macintosh
Clang version 4.1 compiler 64-bit OS X 10.7 Intel-based Macintosh

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

As announced previously, R24 was the last version that supported Windows Vista, Windows XP, as well as the VS 2008 compiler. Contact Spatial Support for any additional information.

Installation Notes

The following sections explain the installation procedure for supported platforms and the resulting directory structure post-installation:

Note: You must not extract UNIX and Windows packages into the same directory.

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

Installing on Windows

  1. Download the self extracting installer from Spatial. Ensure that you download the correct configuration for your compiler and your modeler.
  2. Double-click the self extracting installer.
  3. At the Welcome screen, click Next to continue to the License Agreement screen. Select I accept the agreement to accept the license terms.
  4. The next screen prompts you for the destination folder. Select an empty folder to contain your ACIS installation. The installation then occurs in the selected location. Once your selection is done select Next.
  5. The next screen will prompt you to select which package you want to install. Select the appropriate product based on the products you license. Note that the radio buttons are mutually exclusive, while the checkboxes are not. Once your selection is done, select Next.
  6. Click Install to start the installation process

Important Runtime Installation Instructions for Windows

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, multiple .msi files are placed in a folder called redist, located in the Spatial products installation directory; for example:

<install_dir> \redist
              VC11\InstallDSSoftwareVC11Prerequisites_x86.msi (32-bit)
              VC11\InstallDSSoftwareVC11Prerequisites_x86_x64.msi (64-bit)

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

Important: Install the Visual Studio runtimes globally in your system's WinSxS directory (typically C:\WINDOWS\WinSxS) by using the .msi file in the redist folder. Choose either InstallDSSoftwareVC**Prerequisites_x86.msi for your 32-bit system, or InstallDSSoftwareVC**Prerequisites_x86_x64.msi for your 64-bit system.

Acis3dt uses different versions of HOOPS depending on availability.

  • Customers building their application on VS 2010 will need VC10 runtime.
  • Customers building their application on VS 2012 will need VC11 runtime.
  • Customers building their application on VS 2013 will need VC11 and VC12 runtime.

Using the Uninstaller

Spatial provides an uninstaller for easy removal of its products from your system. While you can remove the program by deleting the parent directory (default location is C:\Program Files (x86)\Spatial), this method will not update your Programs and Features list. Spatial recommends that you use the included uninstaller which is found in the products directory (C:\Program Files (x86)\Spatial\[product]\unis000.exe) to completely remove all components and traces of the program from your registry. The installer does not create any additional features such as start-up shortcuts.

Installing on UNIX and Macintosh

  1. Download the product TAR file from Spatial.
  2. Extract the product TAR file to the desired location.

Note: UNIX and Macintosh packages no longer have installers.

Directory Structure

The directory structure is divided into subdirectories as detailed below:

Directory Description
<arch> For each platform you install, there will be two arch directories: one for the release mode architecture and one for the debug mode architecture. Each arch directory contains the bin and lib directories as described below. The directory format is <arch>/code/bin and <arch>/code/lib. The location of the bin and lib directories changed in R24.
<arch>/code/bin The bin directory contains all the 3D Modeling and Visualization Product shared libraries, DLL files, and executables.
ReadMe_files The ReadMe_files directory contains the ReadMe files; the ReadMe_Acis.htm can be accessed at the top level of the installation directory.
include The include directory contains 3D Modeling and Visualization Product Suite header files.
<arch>/code/lib The lib directory contains all 3D Modeling and Visualization Product Suite static archives and Windows import libraries (.lib files).
scm The scm directory contains code for Scheme AIDE (Scheme interpreter, Scheme extensions, Scheme scripts and projects for building Scheme AIDE), and example projects and makefiles for rebuilding Scheme AIDE.
src The src directory contains source code (such as examples) that is shipped with the 3D Modeling and Visualization Product Suite.
redist The redist directory contains Microsoft redistributable packages. All customers using Spatial CATIA V5 translators need to install redist when developing/executing their application in a Windows environment.

Digital Signatures

Spatial products on Windows Operating System are 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.

Important Notes about Building Your Application with This Release

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.

HOOPS/ACIS Bridge Libraries

Graphics Card Information

The HOOPS 3D Application Framework supports a large number of graphics cards. However, with the large number of graphics cards and machines available today, it is possible that you may encounter a display problem when running the HOOPS-enabled applications such as the ACIS Scheme AIDE. If you are having problems, ensure you have done the following:

  1. Ensure that you are running the latest version of ACIS.
  2. Check the Tech Soft 3D site for updated information on your video card.
  3. Contact your graphics card provider. Your graphics card provider should be able to provide information, suggestions and even updated drivers to help solve the problem.

If you are still experiencing problems, contact our Spatial Support Services department or visit the Online Support Center.

Windows Library Naming Conventions

The table below illustrates how the DLL and Import Libraries for SpaACIS are named on the Windows platform.

Platform Library Names
Windows Release SpaACIS.lib, SpaACIS.dll
Windows Debug SpaACISd.lib, SpaACISd.dll

Licensing Information

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

In order to better protect the use of its intellectual property and gain a more accurate understanding of their use, Spatial products now require a license. Because Spatial does not sell end-user applications, Spatial has ensured that the licensing process is seamless to the end user. Refer to Licensing and Registration for more details.

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 to purchase a license.

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

© 2014 Spatial Corp., a Dassault Systèmes S.A. company. All rights reserved.
ACIS, SAT, and 3DScript are registered trademarks of Spatial Corp. All other names and products are trademarks of their respective owners.

This product includes software developed by Eigen, 
Eigen is covered by the MPL 2.0 license,
Personal tools