SAM 3.2.x latest [Jun 19, 2026]

SHA: 13d9b63b

Fixed Bugs

CSAM-1653 - Part 2 Performance regression while reading Ansys input deck related to the CPAIR

Fix to the performance regression due to the CPAIRs generation while reading Ansys cdb file

CSAM-1650 - Fix face sets contact export to native format

When a contact pair definition is based on element face sets ids, we do not export “CONT.MAST.ELEM*” and “CONT.SLAV.ELEM*” datasets anymore. An error was returned as these datasets were empty.

CSAM-1642 - Added missing data provider options query for VTK plugin

The VTK data provider plugin is missing options published by VtkDataProviderFactory::getProviderInfo().

  • PVD_NODE_WELDING
  • PVTU_NODE_WELDING
  • PVTU_PARTID_FIELD_NAME
  • VTU_VECTOR_AS_DISPLACEMENT
  • VTU_USE_CEETRON_ACCESS_COMPATIBILITY
  • VTU_RESULTS_NATURE_MAPPING
  • VTU_PARTID_FIELD_NAME

You can query available options in a data provider plugin using the getProviderInfo() function. I also updated the description for this option to be able to differentiate the file type it applies to. https://techsoft3d.atlassian.net/browse/CSAM-1642 I don’t know if this should include a new note in the change log for plugin: https://docs.techsoft3d.com/hoops/access/topics/dataproviders/plugins/vtk.html

CSAM-1640 - Fix ABALIB_UPGRADEODB behavior

In some cases, vdm_ABALibGetInteger could return VDM_PHASE instead of the expected ABALIB_UPGRADEODB value.

CSAM-1639 - Avoid error while loading connector elements in Abalib

While loading Abaqus result files with connector elements, an error could be raised while not impacting the reading. This error has been removed.

CSAM-1638 - Fixes VGL OpenGL validation errors for depth peeling

Fixes issue where OpenGL validation errors (GL_INVALID_OPERATION) could occur on some OpenGL implementations when rendering using depth peeling.

CSAM-1637 - Fix for solving an Abaqus FEA model with CONN3D2 Beam elements

Fix to a solver failure when CONN3D2 Beam elements present in Abaqus FEA model. Expected changes:

  • Some element property datasets of Abaqus FEA model which contains BEAM connector elements will be modified.

CSAM-1636 - VGL offscreen depth format selection: prefer 24-bit but allow 32-bit when needed

Fixed an issue where depth buffer blitting could fail on some platforms (GL_INVALID_OPERATION) due to inconsistent use of 32-bit depth formats. Now tries to use 24-bit depth for offscreen textures whenever the default framebuffer depth precision is 24 bits or lower.

CSAM-1635 - Fix to the performance regression due to the CPAIRs generation while reading Ansys cdb file

Fix to the performance regression due to the CPAIRs generation while reading Ansys cdb file

CSAM-1633 - Support combination of front buffer drawing and advanced rendering techniques in VGL

Added support for rendering techniques such as oit, multisampling and depth peeling when doing front buffer drawing (VGL_FRONTBUFFERDRAWMODE = VGL_ON)

CSAM-1629 - Fix to the reading of correct coordinate system id for CBUSH elements from Nastran op2 files.

Fix to the reading of correct coordinate system id for CBUSH1D and CBUSH1DNL elements from Nastran op2 files. Expected Changes: The datasets related to the coordinate system will be modified if CBUSH1D elements are present.

CSAM-1628 - OP2 support: fix missing element results for strain or stress

When importing stress or strain results from a Nastran OP2 file, some results could be missing for certain element types, or some datasets could appear duplicated. This issue has now been fixed. Expected changes: Some datasets root_name:id1:id2:id3 with an unexpected numeric identifier id3 could disappear. Their data is now added to the dataset root_name:id1:id2.

CSAM-1619 - Wrong node results might appear in Naslib

In some very rare cases, wrong result at nodes could be reported.

CSAM-1574 - Avoid duplicating centroidal elemental results into element nodal

Fixed the creation of element nodal datasets for CQUAD4 elements (ecode = 33) that contain centroid-only results. Expected changes:

  • Element nodal datasets will no longer be created for files containing only centroid-only result elements.
  • For files containing mixed element types, element nodal datasets will still be created; however, centroid-only result elements will contain 0 values for nodal results.
  • In such cases, the vis_StateDataStat API can be used to determine whether valid data exists for those elements.

CSAM-1464 - Duplicate material in Nastran export according to element types

In Nastran export, when an anisotropic or orthotropic material is associated with shell and solid element properties, the material is duplicated and exported with the right MAT keyword

New Features

CSAM-1655 - support CPair algorithm type

A new integer property has been added to the vis_CPair object: CPAIR_ALGORITHM. This property defines the contact algorithm to be used. It is particularly useful for the Ansys format. The property can take one of the following three values:

  • CPAIR_ALGORITHM_PENALTY
  • CPAIR_ALGORITHM_AUGMENTED_LAG
  • CPAIR_ALGORITHM_MPC

CSAM-1644 - Improve performance of vis_SpaceLineGroup function

Line-element intersection queries are now significantly faster for large models, delivering approximately 4x to 5x performance improvement.

CSAM-1641 - Support LBF-IN unit system with hour time unit in Nastran input and result files

LBF-IN unit system now returns the right mass units when the unit of time is set to hours for Nastran input and result files.

CSAM-1612 - Update Ansys CFX version to 26R1

Ansys CFX reader is updated to 2026R1 release.

CSAM-1558 - Support new FEMZIP API

Support of the new FEMZIP API. This is now the default API supported.

CSAM-1534 - Support Nastran keywords: BGSET BGADD BCTADD and fix BCTEST

The Nastran keywords BGSET, BGADD, and BCTADD are now supported for both import and export. BGSET is translated into a vis_CPair object with the type CPAIR_TIE_DEF. The numerical parameters SDISTi and EXTi are stored using the parameters CPAIR_POSITIONTOL and CPAIR_EXTENSIONZONE. BCTSET has been corrected when the keyword defines multiple relationships between source regions and target regions; each relationship is now stored in a vis_CPair instead of a single object as previously. Expected changes: Following the support of the BCTADD keyword, importing Nastran models may introduce changes in vis_SProp objects, with a higher number of contacts stored in SPROP_CONTACT_NUM.

CSAM-1521 - Implement Nastran method for Laminate transverse shear stiffness

For SHELLPROP_INTEGRATE and SHELLPROP_LAMINATE shell properties, the internal method used to compute the transverse shear correction factor has been modified. We now use an approach like the one implemented in MSC Nastran. Expected changes:

  • The previous method could lead to an overestimation of the transverse shear stiffness in composite laminates exhibiting strong stiffness heterogeneity through the thickness. In such cases, a more compliant shell response may now be observed.

CSAM-643 - Adding explicit names to new AUTODYN variables

The following AUTODYN results now have an explicit Access name:

  • EROSION -> DELETED.E*
  • STATUS-> STAT.E*
  • DAMAGE-> DAMAGE.E*
  • TIMESTEP-> TIME.[STEP].E*
  • COMPRESS-> COMPRESSION.E*
  • BOND_STATUS-> STAT.[BOND].E*
  • RB_CONTACT_E-> ENERGY.[RIGID,BODY,CONTACT].E*

However, the ALPHA variable will still be stored in UNKNOWN.[ALPHA]* datasets as it can be of different nature, depending on the context.

CSAM-14 - Add Local system definition in concentrated load

It is now possible to define a concentrated load of type LCASE_FORCE or LCASE_MOMENT in a specific coordinate system using the functions vis_LCaseSetConcCoordSys or vis_LCaseAddConcCoordSys. The vis_CoordSys object passed as argument must have a defined ID. This ID can optionally be retrieved using the function vis_LCaseConcCoordSysId. The Force or Moment vectors are automatically expressed in the global coordinate system. An issue in the Abaqus input reader has been fixed. When a CLOAD was defined on a node or node set associated with a TRANSFORM, the Force or Moment vectors were being transformed twice.

Benchmark Report of HOOPS Solve

Provided Third Parties

The use of Third-party libraries in each of the HOOPS SAM components can be found here in the Compilation Options tab.