Welcome
What's New
View new features for Altair HyperWorks 2025.1.
- 2025.1 Release Notes
- 2025 Release Notes
Get Started
Learn the basics and discover the workspace.
Tutorials
Learn more about the Altair HyperWorks suite of products with interactive tutorials.
Startup Procedures and Customizations
Start and configure the applications.
Tool Finder
View a list of deprecated panels and their newer, equivalent workflows.
Manage Files and Data
Create, open, import, and save models.
Sessions and Report Templates
Set up sessions and create report templates.
Interface with External Products
Solver interfaces supported in HyperMesh.
Entities and Solver Interfaces
A solver interface is made up of a template and a FE-input reader.
Browsers
Browsers provide a structured view of model data, which you can use to review, modify, create, and manage the contents of a model. In addition to visualization, browsers offer features like search, filtering, and sorting, which enhance your ability to navigate and interact with the model data.
Sketching
Create and edit 2D parametric sketch geometry.
Topology
Create, edit, and cleanup geometry.
FE Geometry
FE geometry is topology on top of mesh, meaning CAD and mesh exist as a single entity. The purpose of FE geometry is to add vertices, edges, surfaces, and solids on FE models which have no CAD geometry.
Meshing and Elements
Explore the different types of mesh you can create in HyperMesh and create and edit 0D, 1D, 2D, and 3D elements.
Model Build and Assembly
Create, organize and manage parts and subsystems.
Composites
HyperMesh composites modeling.
Connectors
Create connections between parts of your model.
Morph
Rapidly change the shape of the FE mesh without severely sacrificing the mesh quality.
Skeleton Modeling
Create a reduced ordered model to facilitate optimization at the concept phase.
Design Space
Workflow to support topology optimization model build and setup.
Optimization
Setup an Optimization in HyperMesh.
Design Explorer
Multi-disciplinary design exploration and optimization tools.
Validate
Validate the model built before running solver analysis.
Analyze
Models require loads and boundary conditions in order to represent the various physics and/or physical equivalents to bench and in-use testing.
Axisymmetry
Reduce a full 3D model with axisymmetric surfaces while accounting for imperfections.
Concept Modeling
Tools and workflows that are dedicated to rapidly creating new parts for specific use cases, or amending existing parts. The current capabilities are focused on stiffening parts.
Crash and Safety
Tools used for crash and safety analysis.
Airbag
Use airbag folder utilities and export a resulting airbag in a Radioss deck.
Aerospace
Essential utility tools developed using HyperMesh-Tcl.
Aeroelasticity
Import an aeroelastic finite element model with Nastran Bulk Data format.
Certification
Framework to plug certification methods to assess margin of safety from the model and result information.
PhysicsAI
Use PhysicsAI to build fast predictive models from CAE data. PhysicsAI can be trained on data with any physics or remeshing and without design variables.
Results Data in HyperMesh and HyperView
Results data can be post-processed using both HyperMesh and HyperView.
Developer
The Developer ribbon contains tools for automation and customization.
Plot Data in HyperMesh and HyperGraph
Plot data can be post-processed using both HyperMesh and HyperGraph.
Multibody Modeling in MotionView
MotionView is a general pre-processor for Multibody Dynamics.
Media Files in MediaView
MediaView plays video files, displays static images, tracks objects, and measures distances.
Tabulate Results in TableView
Use TableView to create an Excel-like spreadsheet.
Text Files in TextView
TextView math scripts reference vector data from HyperGraph windows to automate data processing and data summary.
Publishing and Reporting
Create, define, and export reports.

View All Altair HyperWorks Help

PAM-CRASH Interface

New Features

Read Solver Output File in Penetration Tool: The ability to read solver output files has been added to the Penetration tool. This can be helpful in reviewing penetrations reported by the solver run.
Safety Tools: A new Seatbelt Deformer workflow has been added. See the Safety Tools release notes for more information.

Enhancements

Keywords Migrated to New Entity: The MASS keyword has been migrated from the Element entity to the Solver Mass entity.; The NSMAS and NSMAS2 keywords have migrated from the Group entity to the Solver Mass entity.
Keyword Updates: CKCTRL/: the METRIC_2D_GEOMETRY_QUALITY, METRIC_3D_GEOMETRY_QUALITY, METRIC_2D_CONSISTENCY, METRIC_3D_CONSISTENCY, METRIC_2D_GEOMETRY_FATAL, and METRIC_3D_GEOMETRY_FATAL options have been added.; ECTRL/: TIED_SUPERPOSITION for superposition of TIED segments has been added.; OCTRL/: new pre filter types TYPE0_PREFILLED and TYPE1_PREFILLED have been added. New outputs in GLBTHP – SECRA, SECRD, SECRV, SECTA, SECTD, and SECTV have been added.; PRCTRL/: the TABLE_INPUT, ETFBC_GES, and INETF_GES qualifiers have been added.; ICTRL/: the PENK3D_M3D_SKIP_ELEMENTS and NL_CONVERGENCE_RIGID_BODY options have been added for implicit solver.; LACTRL/: DIRECT_MUMPS_SCHUR_DFS, DIRECT_MUMPS_SOLVER, DIRECT_MUMPS_BLR_THRESHOLD, DIRECT_MUMPS_BLR_OPTIONS, DIRECT_MUMPS_DISTRIBUTED_RHS, and DIRECT_MUMPS_SCHUR_COMPLEMENT have been added for implicit solver.; TCTRL/: the STRAIN_INCREMENT_LIMIT and CUTBACK_CRITERIA options have been added for implicit solver.; Contact type 43: the IPCP option for the implicit constraint method has been added.; The BDFOR/ card has been updated with the definition of body force's cutting plane.; The PYRA5 solid element is now supported.

Resolved Issues

An import and export issue with the SECURE/ PYVAR keyword has been resolved.
Importing a solver deck with an undefined property now sets the card image to the default property card image instead of none.
QUALIFIER = CURVE is no longer added automatically when importing a model with an NLAVE card. This fix prevents calculation errors.
An export issue with multiple nested include file paths has been resolved.
The Group keyword now retains listed components after importing a .pc file containing a rigid body component with a duplicate comp ID that previously caused conflicts.