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 ACIS Release Notes document contains R20 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.

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.

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 PHL V5
• Advanced Covering
• Defeaturing

Package and Build Changes

ACIS Windows DLLs Restructured

For ACIS R20, all core ACIS functionality has been consolidated into a single ACIS DLL, specifically SpaACIS.dll. Thus, the following DLL files have been eliminated from the ACIS DLL set:

• SpaBase
• SpaAasm
• SpaABlend
• SpaALops
• SpaAPart
• SpaASurf
• SpaAVis
• SpaAWarp

ACIS and InterOp Windows DLLs Renamed

In recent ACIS and InterOp releases, a suffix was placed on the Spatial libraries to distinguish one architecture from another, for example, AMD64 builds were SpaAcisa.dll, while NET builds were SpaAcisn.dll. For R20, these arch suffixes have been removed. However, the "d" suffix has been kept to distinguish debug builds.

ACIS Windows Auto-linking Modifications

For ACIS R20, the ACIS auto-linking behavior has been changed. By default (that is, not defining anything), Windows customers will be auto-linked to the corresponding ACIS release libraries in their lib-path. By defining _DEBUG, Windows customers will be auto-linked to the corresponding ACIS debug libraries in their lib-path. As before, you can still define SPA_NO_AUTO_LINK to disable auto-linking.

Thread-Safe ACIS

All R20 versions of the ACIS product targeting Windows platforms are now thread-safe in the context defined by thread-safe ACIS (TS-ACIS) functionality. This required changes to the definitions of all global resources of the modeler, even those visible to customers, to utilize thread-local storage (TLS). To minimize the impact of such changes, we relied on an internally developed object oriented solution called safe types. For example, SPAresabs is no longer a global double but is instead a global safe_floating_type class object. We have gone through great lengths to assure build compatibility with customer code and request that any incompatibilities be brought to our attention. Please see Thread-Safe ACIS for more information.

Additionally, we have started leveraging the capabilities of TS-ACIS in specific modeler functionality. Our initial efforts have focused on entity point distance operations. The ACIS API api_entity_point_distance can now utilize multiple threads via the ACIS thread manger to speed up its calculations. Please see Entity point distance for more information.

Assembly Modeling

Functional Changes

New API: asmi_restore_model_list

The function asmi_restore_model_list can now be used to load SAT and SAB files into a new model. The functionality automatically works if you pass the function a file pointer to a SAT/SAB file. Loading SAT/SAB files in this manner is different from using api_restore_entity_list, because this ASMI routine creates a model and puts the part into it, while the API loads the part but does not create an asm_model.

Blending

Robustness Improvements

Tolerant Friendly Blending

In R20, the behavior of ACIS Blending on tolerant parts has been made more robust, especially in the areas mentioned in the sub-sections below.

Face Roll-over and Edge Roll-on when Blending Tolerant Parts

When an entity-entity blend intervenes a smooth edge, the blend propagates. This behavior used to be fragile when the intervening edges are tolerant smooth or near-tangent. This behavior has been made more robust in R20. It is important to note that in such cases, the cross edges that are made by blending would be tolerant too.

Similarly, when an entity-entity blend or edge blend intervenes a sharp edge on its side (along the spring) the blend may roll-on the intervening edge [this happens when a side cap is not possible or it fails]. This behavior used to be fragile when the intervening sharp edges are tolerant. This behavior has been made more robust in R20.

Entity-Entity Blend in which Rollover (smooth propagation) happens over a 'tolerant' edge

Before Blending - Edges marked in CYAN are tolerant

After Blending

Entity-Entity Blend in which Rollover (smooth propagation) happens over a 'tolerant' edge

Before Blending - Edges marked in CYAN are tolerant

After Blending

Entity-Entity Blend in which Roll-on happens on a 'tolerant' sharp edge

Before Blending - Edges marked in CYAN are tolerant

After Blending

Capping on Tolerant Parts

The robustness of Capping (both Endcap and Sidecap) on tolerant parts has been improved for those cases where capping faces need not be extended to trim blend face.

Blend has an endcap that intervenes with 'tolerant' edges

Before Blending - Tolerant Edges are shown in CYAN

After Blending

Failure diagnostics

Improved error information

When the blend operation fails, the error message is supplied as part of the "outcome" object from the respective API. From R20, Blending APIs provides additional diagnostic information as part of their outcome. This would potentially give some more clues to identify the problem zone. Detailed information about this enhancement is available at Blending Error Codes.

Booleans

New Functionality

Failure diagnostics: Boolean error information

If a Boolean operation fails, then the returned error information object may now contain pointers to the faces at which the failure occurred. Up to two faces may be returned in the error information object, depending on the manner in which the Boolean operation failed. If two faces are returned then one of them is from each of the input bodies. If one face is returned then this can be from either input body.

Constructors

New Functionality

New API: api_chamfer_wire_vertex

A new API, api_chamfer_wire_vertex, has been introduced for performing a vertex chamfer on a wire-body. The signature of the API is

outcome api_chamfer_wire_vertex(
  VERTEX  *ver,
  double  offset,
  chamfer_wire_options* co = NULL,
  AcisOptions* ao = NULL)

The Scheme extension for accessing the API is vertex:chamfer.

New Class: chamfer_wire_options

A new options class, chamfer_wire_options, has been introduced to supply options to the wire chamfer API api_chamfer_wire_vertex.

Faceter

New Functionality

• Faceting edges

A new option, facet_edge_features, has been added to improve the Faceter. Sometimes edges may have wild fluctuations. When set to true, the faceting of these edges is enhanced by first using knot values of the spline representation, and then proceeding with the old algorithm. This ensures that features of these edges are captured in the faceting solution. However, there may be more facets along the edge than previously realized. The default for this option in ACIS R19 is false, whereas the default in ACIS R20 and later is true.

• Adaptive Faceting on the fringe

A new option, adaptive_t_fringe, has been added to enable use of adaptive faceting on the fringe of faces. Refer to Adaptive Faceting for more information.

HOOPS/ACIS Bridge

New Functionality

New Function: HA_ReRender_Body_Transforms

A new function, HA_ReRender_Body_Transforms, has been introduced to allow you to update scene graphs in an efficient way when only body transforms have been changed. By using it, you may avoid unnecessarily remaking the entire graph to respond to a very specific type of change.

The signature of the function is

logical HA_ReRender_Body_Transforms(ENTITY_LIST& bodies)

New Function: HA_ReRender_Visibility_ASM

A new function HA_ReRender_Visibility_ASM, has been introduced to allow you to update visibility conditions of an assembly model in an efficient way.

Note: This function does not treat part models.

You will typically call it after using HA_Set_Rendering_Options to change which types of entities—faces, edges, vertices—are to be made visible or invisible. By using this function, you may avoid unnecessarily remaking the entire scene graph to respond to a very specific type of change.

The signature of the function is

void HA_ReRender_Visibility_ASM()

Kernel

New Functionality

New behavior: api_replace_edge_with_tedge

The behavior of functions which make edges tolerant, such as api_tolerize_entity, api_check_edge_errors, and api_replace_edge_with_tedge, has changed. If the input EDGE is based on an curve with procedural geometry, then the procedural geometry is now also used for the output TEDGE. Previously the geometry of the output TEDGE was based on the approximating bs3 approximation. A new option, keep_tedge_proc_geom controls this behavior: switching the option to FALSE reverts to the old behavior of this API.

New API: api_deep_down_copy_entity

A new API, api_deep_down_copy_entity, has been introduced for creating a complete copy of an entity and all connected entities below it without references to underlying shared entities or geometry of the original. Use this API to avoid copying a complete body when only a portion is needed.

The signature of the API is

outcome api_deep_down_copy_entity(
  ENTITY* source_body,
  ENTITY*& target_body,
  logical dpcpy_skip = FALSE,
  AcisOptions* ao = NULL)

The Scheme extension for accessing the API is entity:deep-down-copy.

New option parameter: SPA_approx_options

A new options parameter has been added to the SPA_approx_options which controls the degree of the approximation. Using the SPA_approx_options::set_degree method, clients can change the default approximation degree from cubic (3) to quintic (5). Quintic is recommended for approximations with fit tolerance smaller than SPAresfit. The SPA_approx_options are for use with the api_approx apis. Note that clients work with one of the two derived classes SPA_EDGE_approx_options or SPA_COEDGE_approx_options, depending on which signature of api_approx they are using.

The scheme extensions for setting the SPA_approx_options are spa-coedge-approx-options:set and spa-edge-approx-options:set.

More information and examples can be found in the technical article Approximations.

New behavior: error_info

The error_info class associated with outcome objects has been enhanced to provide a link to entities associated with a problem or failure. It is no longer necessary to ask if an error_info is an entity_error_info (see below) or to use entity tags in order to identify an entity. Now one simply calls the error_info::get_entities_alive method in order to access the live entities involved in a bad outcome.

Moved Classes

Refer to ACIS Interface Change History and ACIS Anticipated Deprecations regarding the following changes.

Class entity_error_info

The class entity_error_info has been deprecated; the services it provided are now accessible through the error_info class interface. It has been renamed to entity_error_info_legacy; the associated header file ent_err_info.hxx has been renamed deprecated_ent_err_info.hxx. The class and its associated header will be removed in a future release.

Local Operations

Moved Classes

Class rem_error_info

The header file associated with the rem_error_info class has been renamed deprecated_rem_error.hxx (formerly rem_error.hxx).

Model Analysis

ACIS Checker

New ACIS checker level 5

Some level 10 topology checks have been changed so that they are performed at level 5. This enables the ACIS checker to be executed with check level 5 to perform "Fatal topology checks". See Types_of_Checks for futher details.

Separate missing non-G¹ or non-G² discontinuity errors into an error and a warning

The check for missing non-G¹ or non-G² discontinuities has been changed so that an error is produced for missing non-G¹ discontinuities, but missing non-G² discontinuities only produce a warning.

Intersectors

New Functionality

New Scheme extension edge:self-intersect?

The new Scheme extension edge:self-intersect? for accessing existing APIs api_crv_self_inters and api_ed_self_inters has been created to determine whether an edge self-intersects. If a self-intersection is found, the extension returns the edge-curve parameters corresponding to the intersections.

Object Relationships

New Functionality

Multi-threaded api_entity_point_distance

The multi-point api_entity_point_distance API will now take advantage of multiple processors automatically. The only code change required to enable this will be to initialize thread safe acis.

Refer to

• Using in Multithreaded Mode for a code snippet indicating how to use the API in multithreaded mode, and
• Thread-Safe ACIS and thread_work_base for more general information on threading.

Clash improvements

The function api_body_clash has undergone a significant rewrite to improve robustness and performance when the clash_mode is CLASH_EXISTENCE_ONLY.

Ray Testing

New Functionality

New API: api_ray_fire

This new API, api_ray_fire provides an interface to a new ray testing algorithm. This API generally performs better than the older ray testing APIs, and honors the radius of a ray reliably. The older APIs remain available using the older algorithm; there are likely to be significant behavior differences between the algorithms.

Offsetting

New APIs

New API: api_offset_edges_on_faces

A new API, api_offset_edges_on_faces, has been introduced for creating a wire body by offsetting edges on the faces of the same body. The amount of separation between the input edge and the corresponding offset edge is equal to the offset distance as measured along the surface geometry of the intervening face(s). Refer to the technical article Offsetting Edges on Faces for more information.

The Scheme extension for accessing the API is edges:offset-on-faces.

Multiple Offsets of the Green, Non-Smooth Chain of Edges

Springback

New Functionality

Optimizations for use with Finite Element data

To support Springback operations based on Finite Element data, the SPA_spring_back_def can be optimized to support large sets of point constraints. This is done by calling

void SPA_spring_back_def::set_do_FEA(TRUE)

before passing the SPA_spring_back_def to api_spring_back.

Clients can query the current option setting using

logical SPA_spring_back_def::get_do_FEA()

We recommend that clients using ACIS Springback in an FEA work flow always use this optimization.

Overriding Surface Trimming in Springback Operations

By default, surfaces processed by a Springback operation are trimmed back from their original ranges when doing so might help to minimize gaps between output geometry and the target constraints. You can now override this behavior by means of the new class method

void SPA_spring_back_options::set_do_maintain_surface_ranges(logical do_maintain)

and also query the current option setting using

logical SPA_spring_back_options::get_do_maintain_surface_ranges() const

Use the first of these, with an argument of TRUE, on a SPA_spring_back_options class object before passing the latter to api_spring_back, in order to override surface trimming. The resulting output surfaces will then have ranges that match their associated inputs.

Note: Subsetting is considered an integral part of the definition of a surface's range. If you wish it to be ignored in the construction of the output surfaces, use surface::unlimit prior to the Springback operation.

Sweeping

New Functionality

Sweeping normally across tangent faces

Given a collection of contiguous tangent faces, and an unbranched wire on the faces, api_make_rails can now provide rail laws which can be used with api_sweep_with_options to sweep a profile along the wire, in a direction always normal to the faces. For example, if the faces are sliced with a plane (using api_slice), the resulting wire would be a suitable path.

A scheme example can be found in the Sweeping With Options tech article.

New Product-specific Features

HOOPS/ACIS Bridge

Support for HOOPS 17.0

ACIS R20 is built against HOOPS 17.0 (hoops1700 library). All supported Spatial platforms use HOOPS in the R20 release.

Installation Notes

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

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.

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

Installing on Windows

1. Download the product ZIP file from Spatial's Online Support Center.
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 specified installation directory.
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 3D Modeling and Visualization Product Suite R18 installation. The installation then occurs in the selected location.

Important Runtime Installation Instructions for Windows

Note: The following instructions apply only to customers who build their application using the Microsoft Visual Studio .NET 2005 (SP1) 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.

Note: The following instructions apply only to customers who build their application using the Microsoft Visual Studio .NET 2008 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
.
.
.
              VC9\vcredist_x86.exe (32-bit)
              VC9\vcredist_x64.exe (64-bit)

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

Installing on UNIX and Macintosh

1. Download the product TAR file from Spatial's Online Support Center.
2. Extract the product TAR file to the desired location.
3. Run the installation program acis_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.

Directory Structure

The directory structure is divided into subdirectories as detailed below:

bin directory

The bin directory contains all 3D Modeling and Visualization Product Suite executables, shared libraries, and DLLs within its subdirectories. For each platform you install, bin contains two arch subdirectories: one for the release mode architecture, and one for the debug mode architecture.

docs directory

The docs directory contains the ReadMe files.

include directory

The include directory contains 3D Modeling and Visualization Product Suite header files.

lib directory

The lib directory contains all 3D Modeling and Visualization Product Suite static archives and Windows import libraries (.lib files) within its subdirectories. For each platform you install, lib contains two arch subdirectories: one for the release mode architecture, and one for the debug mode architecture.

scm directory

The scm directory contains code for Scheme AIDE (scheme interpreter, Scheme extensions, Scheme scripts and projects for building the Scheme AIDE), and example projects and makefiles for rebuilding Scheme AIDE.

src directory

The src directory contains source code (such as examples) that is shipped with 3D Modeling and Visualization Product Suite.

redist directory

The redist directory contains Microsoft redistributable packages for those who build their application using the Microsoft Visual Studio .NET 2005 (SP1) compiler.

Digital Signatures

Spatial products on Windows Operating System with Microsoft Visual C++ 2005 compiler 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

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.

Update Tool

In versions prior to and including R12, an Update Tool was provided with 3D Modeling and Visualization Product Suite to assist in migrating customer code to the new version. This tool primarily implemented changes in header file path references. R13 through R18 have no such changes, therefore no Update Tool has been included with these versions. If you are migrating from a version of 3D Modeling and Visualization Product Suite older than R12, contact Spatial Customer Support to obtain the appropriate version of the Update Tool.

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.

Library Extension on AIX Platform

In order to comply with standard naming conventions for shared libraries, all libraries on the AIX platform have an ".a" rather than a ".so" extension.

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

^{© 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.