BETA CAE Systems Japan Inc.is pleased to
announce the new release of v25.1.1.
New functions are equipped with v25.1.1.
For details of new features and bug fixes, please refer in the
following.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
About this release
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
We officially announce the v25.1.1 release, for ANSA, EPILYSIS, META, KOMVOS, SPDRM, ANSERS, FATIQ and RETOMO.
Just two months past the official commencement of v25.1.x series, v25.1.1 comes at a perfect timing to empower you with boosted performance, more stability - yet greater flexibility - at your processes, thanks to critical bug fixes and selected implementations.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Enhancements and known issues resolved in ANSA
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
< Known issues resolved in ANSA >
Data Management
Focusing on Logbook, selecting any values to be displayed in the embedded META Viewer, would result in the values of the next column being displayed instead.
Moreover, in DM Browser, file attachments would be lost upon next iteration/download and while saving a new version.
Modular Run Management
Defined Target Id ranges on Impactors used by target Point Library Items would not be written in the solver keyword file.
In addition, the default numbering rules would not be read in the case of Next Iteration on a solver Subsystem.
Connections & Assembly
Converting Shells or Faces to Adhesive Faces would lead to an unexpected termination when using a Subsystem as Current and having active the Subsystem Draw Mode.
FE Representations
Concerning RBE2, for LS-DYNA and for a rigid Connectivity, the created
*CONSTRAINED_SPOTWELD would result in errors in the solver. Now,
*CONSTRAINED_EXTRA_NODES are created instead.
Furthermore, realizing RBE3/ RBE2-CBEAM/ RBE2/ BEAM-CONTACT with regular distribution could lead to abnormal termination.
Shell Mesh
Unexpected termination could happen after editing values in Quality Criteria window.
Laminates
Upon report generation, ABD matrix was not printed if PCOMPs were attached on geometric faces.
NVH Console
In cases where the option "Exclude Rigid Body Modes" was activated in the Defaults, Rigid Body Modes were excluded from the calculations in FRF Assembly for all components of all NVH Console runs.
LS-DYNA
ANSA would become unresponsive for a few seconds, when drawing beam elements with ELFORM=3 and the "Line elements cross section" presentation parameter was active.
Pam-Crash
During Input, unexpected termination would occur for BAGIN/, if GNAME was not in single quotes.
Optimization Tool
The values of an Optimization Study would not be updated when DM was empty.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Enhancements and known issues resolved in EPILYSIS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
< Known issues resolved in EPILYSIS >
General
The performance of transient response analysis has been significantly improved in cases where too many RFORCEs are set.
Significant time reduction has also been noted in AMLS phase 5 for "Fluid physical space responses recovery" in case of FRF calculation with detailed cavity models.
EPILYSIS would terminate unexpectedly if a static pre-load (STATSUB) was used in two different dynamic subcases (SOL111).
SOL200
Abnormal termination would occur in cases with many DESVARs and many retained constraints (dual casting).
Output
Unexpected results would be produced in case of overlapping ERP panels and ALLPANEL output was requested.
In addition, ERP calculation did not work correctly in case of common shell/solid faces, or when requesting results on a Set.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Enhancements and known issues resolved in META
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
< Known issues resolved in META >
General
"Auto Redraw" option in SETs did not work since version 25.0.0.
NVH Calculators
Focusing on FRF Assembly, NVH Insights would just animate the component where the response was taken and not the complete assembly.
Regarding Modal/FRF Correlation, META would terminate unexpectedly when loading results from Nastran SOL105 dynamic subcase solution.
Project Files & METADB
META would not successfully detect the file format, when reading geometry from a compressed (.zip) METADB file.
In addition, user created results were not saved in Project Files when using the option "Save References" to Results Files.
States & Animation
State attributes did not appear in the Right Mouse Button menu options of the animation bar.
Managing Curve Data
Curves from DIAdem files were erroneously read.
TDMS files were not read correctly.
Modal Displacements were not read from SOL111 and SOL112 results file, when the option Modal Displacement (contribution analysis) was selected.
Curves from ERFH5 files were read multiple times when they were read from session file.
Handling Entities
Unexpected termination could occur when selecting MAT8 material on the 3D window.
Annotations
Annotation on synchronized curve value kept on returning values, while animating states, even after the end of date was reached for the annotated curve.
Abaqus
META wouldn't read Abaqus models with cyclic symmetry correctly, if element and node IDs were bigger than 1M.
File export
When saving nodes to CSV format, multiple lines would be written per node.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Enhancements and known issues resolved in KOMVOS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
< Known issues resolved in KOMVOS >
Data Management
Editing of an attached file of a Subsystem would not be possible.
Machine Learning
Machine Learning training would not be completed on Windows OS, when field results from META databases that contained the colon symbol, e.g. "Model_1:Displacements".
Configuration
KOMVOS.defaults would not be saved correctly after launching KOMVOS, while previously connected to an SPDRM server.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Enhancements and known issues resolved in SPDRM
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
< Known issues resolved in SPDRM >
Data Management
Modifying the Status Property of a Subsystem would erroneously lead to the corruption of the stored DM object.
Data Migration/Archival
The relationships (links) between data objects were not retained during data migration from one SPDRM environment to another, using the DM Export/Import functionality among separate packages exported from the same source environment.
Furthermore, the DM import would be interrupted when it encountered properties/attributes with special (multi-byte) characters, due to an encoding issue on the SPDRM java client application.
Users Management/Security
It would not be possible to set ACLs (privileges) on data based on the value of a particular property/attribute (e.g. Project), in case the list of its accepted values was defined according to rules.
Moreover, the sorting function in the Users list under the SPDRM Admin. web portal (Users Management tab) was not working as expected.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Enhancements and known issues resolved in ANSERS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
< Known issues resolved in ANSERS >
General & Frontend
Opening a shared dashlet in new tab would activate it also in current tab.
Actions using Send to functionality were not saved directly in the dashlet.
The static html report generated from a dashlet could not be loaded correctly in various cases.
Panels
Several bug-fixes regarding various panel types have taken place, as follows:
In case a second model was selected to be displayed in a 3D Model panel, it appeared undeformed.
In Curves chart points could not be displayed.
In Scatter and Curves charts changes to axis and curve line style options were not applied directly but only after refreshing the browser page.
In Table panel selection brought wrong objects to the implicit datasource, when the table was sorted.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Enhancements and known issues resolved in FATIQ
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
< Known issues resolved in FATIQ>
Modal Response
Centroid stresses were output by the analysis embedded Modal Response task, despite defining the output request on Corners.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Enhancements and known issues resolved in RETOMO
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
< Known issues resolved in RETOMO>
Item Browser
Representative foam cell center coordinates are now seamlessly calculated and printed in the "Cell List". This information is also exported in the CSV file, along with the rest of the columns.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CAD data translator
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The supported CAD-data formats handled by the CAD DATA Translators are
listed
below.
・CATIA V5 (R7 - V5-R34) [.CATPart], [.CATProduct]
Tesselated data [.cgr]
・CATIA V6 (2011x - 2013x)[.3Dxml]
・3DExperience (2014 - 2022x)[.3Dxml]
・NX (CT based, Unigraphics V11.0 - NX1957, NX CR 2306, NX CR 2312, NX CR 2406)
[.prt]
・NX (UG Open based, NX1953, NX1980, NX2007, NX2206, NX2212, NX2306, NX2312)
[.prt]
・Parasolid (all - 36) [.xmt_txt], [.xmt_bin], [.x_b], [.x_t]
・Pro/ENGINEER (from WF3 to WF5),
PTC Creo Parametric 2.0 M140, PTC Creo Parametric 3.0 M020,
PTC Creo Parametric 3.0 M030, PTC Creo Parametric 3.0 M040,
PTC Creo Parametric 3.0 M090, PTC Creo Parametric 4.0 F000,
PTC Creo Parametric 5.0 - 11.0 [.prt], [.asm]
・SolidWorks (2007 - 2024) [.sldprt], [.sldasm]
・JT (v8.0 - v10.8) [.jt]
・Inventor (2010 - 2025) [.ipt], [.iam]
・CoreTechnologie [.ctp], [.cta]
・Rhino(up to v7) [.3dm]
・ACIS(R27) [.sat]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Recommended GPU (OpenCL Support) requirements
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following presents the recommended GPU requirements.:
・GPU :NVIDIA、AMD
・OpenGL Version:4.5
・GPU memory :2GB
・OpenCL Version:1.2
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Virtual Machine Environment
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Please pay attention to the following specification that is described in a
document
beta_lm_tools_v7.2_setup_guide.pdf
・In other words, any instance of an application launched through a Virtual
Machine or Machine of NIC Teamng will not share the same license and will
occupy the prescribed
number of credits.
In addition,regarding user account and password for downloading modules and
documentation, we announce ones only to the customers who had contract.
The customers who had contract,in case user account and password are
unknown,
please contact our sales team(Emaill: betajp.sales@cadence.com Tel:
+81-45-478-3696).
If you have any technical questions about BETA CAE Systems softwares,
please contact our technical team(Emaill: betajp.support@cadence.com Tel:
+81-45-478-3841).