April 22, 2016

BETA CAE Systems announces the release of
the v16.1.2 of its software suite

---

---

About this release

BETA CAE System S.A. announces the release of v16.1.2 of its software suite.

This maintenance release focuses on the correction of identified issues.

Users updating to v16.1.2 from v16.0.3 will find that fixes of v16.0.4, not already solved with v16.1.1, are also now propagated to v16.1.2.

For further information about fixes on v16.0.3 issues please refer to v16.0.4 release announcement.

The most important additions and fixes implemented in v16.1.2 are listed below.

Contents

Enhancements and known issues resolved in ANSA
Known issues resolved in META
Compatibility and Supported Platforms
Download

---

Enhancements and known issues resolved in ANSA

Enhancements in ANSA

Radioss

The IMPDISP Keyword is updated according to RADIOSS versions 11.0 and onwards.

Known issues resolved in ANSA

General

Sorting by column would not be available in the Check List.

Script>Load: Upon activation, the File Manager would start in the user's home directory, instead of the current working directory.

CAD Translators

Translator would not operate as expected due to an issue with the command line syntax, related to "-idir" argument.

Connections & Assembly

By Connections>Check double connections, the selection of check method -i.e. "By absolute distance" or "By average thickness" would be regarded conversely, leading to erroneous results.

GEBs referring to other GEBs in their connectivity field, would not be applied.

Compare

When using the function Compare With Current Model the temporary models created during executing the Compare Tool, remained loaded after the completion of the comparison process.

Shell Mesh

By Grids Release, selected frozen elements were also affected.

In certain cases, when using Thick Zones not all of the defined zones would be created around a triple bound.

Volume Mesh

Check of Negative Volumes reported erroneous number of violating elements.

Decks

Checks: Upon fixing free nodes, all BCs defined on SETs would be erased.

Laminates: Comments for woven laminate layers were erroneously written, resulting in unexpected termination during file input.

Upon running a sequence of checks through a script, unexpected termination could occur.

NASTRAN

During input, the keyword following the MATT8 definition was not read properly.

NVH – Console

Grid Point cards would not open when Sockets were selected with double-click, within the NVH Console diagram.

LS – DYNA

Cases where the keyword *DEFINE_CURVE_FUNCTION was erroneously output multiple times, when the option "Disregard includes" was inactive.

Float values, in the field NP of the *AIRBAG_PARTICLE element card, could lead to unexpected termination.

Pam-Crash

When mapping NASTRAN pressures to Pam-Crash, mapped pressure and re-orientation of target mesh were erroneously indicated.

Morphing

Applying Direct Morphing with DFM could generate distorted geometry.

Scripting

The issues with the Script PartToPID have been resolved.

 

For more details about the new software features, enhancements and corrections please, refer to the Release Notes document.

 

Enhancements and known issues resolved in META

Known issues resolved in META

General

Reading NASTRAN Contact Forces results in the Section Forces tool could cause unexpected termination.

Saving results of elements and nodes in CSV format might not work for adaptive mesh.

Supported Interfaces

Abaqus *NMAP, ..., TYPE = TRANSLATION was not supported correctly.

Wrong nodal results might be calculated from NASTRAN files by the Linear Combination tool if Nodal Calculation Averaging Order: Average,Compute was used.

2D Plots

User defined (template) curves for Radioss Spring Forces results would not be plotted.

 

For more details about the new software features, enhancements and corrections please, refer to the Release Notes document.

 

Compatibility and Supported Platforms

ANSA files saved by all the first and second point releases of a major version are compatible to each other. New major versions can read files saved by previous ones but not vice versa.

META Project files saved from version 16.1.2 are compatible and can be opened by META version 16.0.0 or later. To be readable by META versions earlier than v16.0.0, they have to be saved selecting the option "Version <16.0.0".

Support for 32-bit platform has been discontinued for all operating systems.

 

 

Download

Where to download from

Customers who are served directly by BETA CAE Systems, or its subsidiaries, may download the new software, examples and documentation from their account on our server. They can access their account through the "user login" link at our web site.
Contact us if you miss your account details. The [ PublicDir ] link will give you access to the public downloads area.
Customers who are served by a local business agent should contact the local support channel channel for software distribution details.

What to download

All files required for the installation of this version reside in the folder named "BETA_CAE_Systems_v16.1.2" and are dated as of April 22, 2016. These files should replace any pre-releases or other files downloaded prior to that date.
The distribution of this version of our pre- and post-processing suite is packaged in one, single, unified installation file, that invokes the respective installer and guides the procedure for the installation of the required components.

For the installation of the software on each platform type, the.sh installer file residing in the folder with respective platform name, for Linux and MacOS or the respective .msi installer file for Windows, 64bit, have to be downloaded.

In addition to the above, optionally, the µETA Viewer is available to be downloaded for each supported platform.

The tutorials and the example files reside in the folder named "TUTORIALS". This folder includes the complete package of the tutorials and example files, and a package with only the updated ones.

The Abaqus libraries required for the post-processing of Abaqus .odb files are included in the installation package and can be optionally unpacked.

Earlier software releases are also available in the sub-directory called "old" or in a folder named after the product and version number.