ACIS Release Notes
This service pack is a collection of new features and updates that fix issues reported against the ACIS R24 release and incorporates all of the ACIS R24 content.
Important: The service pack is standalone and must 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 ACIS R24, we encourage you to download this service pack to ensure that you are running the most current, up-to-date version of ACIS.
Note: This ACIS service pack should be used with the same service pack level of InterOp.
Release Notes R24 SP2
|This Service Pack is standalone and must be installed into a directory that does NOT contain prior releases.|
No platform changes in this release.
Splitting Wire Edges
A new API api_split_wire_edges has been introduced. This API splits edges of a given wire using the given positions. The signature of the API is as follows:
outcome api_split_wire_edges ( BODY* wire , const SPAposition_vector &points , split_wire_options* swo = NULL , const AcisOptions* aO = NULL )
New API: api_fit_line
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
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.
Support for HOOPS 20.00 for Windows
ACIS R24 SP2 is built with HOOPS 20.00 for Windows, HOOPS 19.18 for Mac, and HOOPS 17.00 for the Linux platform. All supported Spatial platforms use HOOPS in this release.
For any issues you have submitted, log into the Support area at the Spatial Web site to check their status.
For a complete listing of new and updated technical articles, refer to:
R24 SP2 Release Date: February 2014
|Compiler Build||Tested OS||Processor|
Microsoft Visual C++ 2008 SP1 32-bit
Windows Vista 32-bit and 64-bit SP2
|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)||x86-64|
|gcc version 4.2.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
R24 is the last version that supports Windows Vista, as well as the VS 2008 compiler. Contact Spatial Support for any additional information.
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
- Download the product ZIP file from Spatial's Online Support Center.
- Extract the product ZIP file by double-clicking the file and specifying the desired installation directory.
- Double-click the setup.exe file in the specified installation directory.
- At the Welcome screen, click Next to continue to the License Agreement screen. Select Yes to accept the license terms.
- The next screen prompts you for the destination folder. Select an empty folder to contain your 3D Modeling and Visualization Product Suite 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 2008 (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 . . . 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
- Download the product TAR file from Spatial's Online Support Center.
- Extract the product TAR file to the desired location.
- Run the installation program acis_install.
- At the first screen, review the details about navigating the installation program. Press <Enter> to continue with the installation process.
- 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.
- 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.
The directory structure is divided into subdirectories as detailed below:
|<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 has 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.|
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:
- Ensure that you are running the latest version of ACIS.
- Check the Tech Soft 3D site for updated information on your video card.
- 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.
Windows Library Naming Conventions
The table below illustrates how the DLL and Import Libraries for SpaACIS are named on the Windows platform.
|Windows Release||SpaACIS.lib, SpaACIS.dll|
|Windows Debug||SpaACISd.lib, SpaACISd.dll|
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 firstname.lastname@example.org 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 and SAT are registered trademarks of Spatial Corp. All other names and products are trademarks of their respective owners.