Altair Software and Hardware 2024.1 Release Notes

Hardware and Platform Support

Operating system additions
Support for the following platforms has been added:
  • Windows 11
  • SUSE Linux Enterprise Server 15 SP3
  • Red Hat Enterprise Linux 8.4/Oracle Linux 8.4
  • Rocky Linux 8.4
Discontinued hardware platform support systems
Support for the following platforms has been dropped:
  • SUSE Linux Enterprise Server 15 SP2
  • Red Hat Enterprise Linux 8.3/CentOS 8.3

Installation

HyperWorks 2024.1 suite contains independent product packages
Independent product packages give you the flexibility to download desired packages as needed. Any HyperWorks 2024.1 SA (standalone) update package can be installed either on top of an existing 2024.1 installation or it can be installed independently without the prerequisite of a 2024.1 base.
Important: You can no longer install a different version of an already installed product to the same location (for example, HW Desktop 2024.1 on top of HW Desktop 2024).
Installer capabilities and features
HyperWorks 2024.1 brings with it the robust capabilities and features of HyperWorks 2024 installers, as well as additional support for HotFix installers. These HotFix installers are quick patch type installers that are used to install on top of a prerequisite base installation, unlike the other full installers. These are marked with the word “hotfix” in the installer name and bring with them the quick fixes and features to better suit your needs.
Model files removed from installation package
To reduce the footprint size, the following tutorial model and demo model files are no longer included in the local installation. You can now find zipped tutorial model files and demo model files on Altair One via the Altair One Community and Altair One Marketplace sites. Altair recommends that you create an Altair One account and use it as your primary portal to access product documentation, a Knowledge Base, and customer support.
  • Tutorial Model Files
    • BasicFEA
    • HyperGraph
    • HyperLife
    • HyperLife Weld Certification
    • HyperMesh
    • HyperStudy
    • HyperView
    • HyperWorks
    • HyperWorks CFD
    • HyperWorks Collaboration Tools
    • HyperWorks Desktop
    • MotionSolve
    • MotionView
    • nanoFluidX
    • OptiStruct
    • Radioss
    • SnRD
  • Demo Model Files
    • OptiStruct > Examples
    • OptiStruct > Verification Problems
    • Radioss > Examples
    • Radioss > Verification Problems

Installation and Packaging Features

  • The installer JRE was updated to Amazon Corretto 11.0.19.7.1.
  • A launch script was added for HyperLife Crack Growth on Linux.
  • Inspire products and HyperMesh CFD now have their own lightweight installers that will download and install all required components.
  • HyperMesh CFD now supports server-mode installation.
  • Altair Inspire was added to the Linux menu.
  • Application Java Runtime was upgraded to Amazon Corretto 11.0.21.9.1.
  • HyperStudy has been updated with a new user interface.
  • Desktop 2022.3 can be installed using the 2024.1 Altair HyperWorks Products Installer (main installer).
  • HyperMesh CFD was added as a new product on Windows and Linux.
  • Installers were upgraded to InstallAnywhere 2022 R2.
  • Digital signatures have been added to more executables to improve security.
  • Installers have been improved to reduce the file footprint and improve installation performance.
  • Mechanical Solvers installation is now modular, so you can choose which solvers to install.
  • nanoFluidX was added to the CFD Solvers package on Windows, it is also available on Linux.
  • File associations for HyperWorks Desktop were updated to open files in the new user interface.
  • FluxMotor was added to the Flux package on Windows.
  • newFASANT was added to the Feko package on Windows and Linux.
  • Overwrite/overlay installation is no longer supported, and the installers will prevent it from happening.

Known Issues

The following known issues will be addressed in a future release as performance of the software is continuously improved:

  • The use of commas in the install path causes multiple products to not function currently.
  • On Windows 11, the shortcut icons for server and client mode installations are blank unless remote paths in shortcut icons is enabled in the Windows group policy editor.
  • Using the Back/Previous option with an installer may not reset the installer variables correctly if changes are made and the install session is continued.
  • On Linux, installing to a directory with spaces is not supported. Additionally, if the path that the installers are run from contains a space, you will see a harmless message in the terminal window.
  • Special characters in the path to the temp location can cause the Java in the installer to not function correctly.
  • On Linux, during a console mode install, when using the response file output command -r in the Help Configuration response file may not write out correctly.
  • If there is not enough TMP/TEMP space on the main drive (for example, C: under Windows), the installer will prompt you to input a new location. Some Java TMP/TEMP space will still try to go to the main drive even when selecting this new location.
  • Click Cancel to stop an installation:
    • via the Altair HyperWorks Products Installer (main installer) does not clean up the already installed files, but does clean up the files in the TMP/TEMP folder. You will need to uninstall/delete the installed files from the chosen install folder manually if Cancel was clicked.
    • causes the Add/Remove uninstaller icon to possibly not function correctly, and then manual removal of the installed files would be necessary.
  • The HyperWorks installers do not support the use of the default InstallAnywhere installer.properties files. It is requested that a unique name is used when using a response file; for example, installer_hw2024.properties, and to use it with the -f <path_to_file>/<filename> command line option.
  • For NETSETUP client installs from a server installation of HyperWorks, a UNC path must be used to get to the server installation path through Windows Explorer or Windows Network.
  • On Linux, there is an issue with using the Altair HyperWorks Products Installer (main installer) with the IATEMPDIR variable to specify a custom temporary directory location. All sub-installers will try to use /tmp from the machine running the installers for temporary installer files.
  • The installer does not run the Linux Menu installation by default, the user must run the installation script.
  • When the Main Uninstaller is used, desktop shortcuts, if any, will not be removed during uninstallation.

Resolved Issues

  • Installers that were failing to install when the Windows Regional Format was set to Arabic or Hebrew now install successfully.
  • EDEM will no longer set file associations if you have not selected that option when using the HyperWorks Products Installer.
  • Hydra services started by Feko and Flux were not being stopped before an uninstall.
  • The installer names were being truncated on displays with scaling set to 125% or higher.
  • Installing Feko as a non-administrator no longer causes a non-fatal installation error.
  • Installing SimSolid by itself using the Altair HyperWorks Products installer (main installer) no longer causes a non-fatal installation error.
  • Installing Flux in silent mode on Linux no longer causes an unexpected terminal message.
  • HyperMesh File Preview (thumbnail) registration was not occurring for some types of installations.
  • Silent installs will no longer check for running processes using PowerShell.
  • When SimLab is uninstalled from a multi-product install, it no longer removes the common Python directory.
  • The Altair HyperWorks Products Installer (main installer) reported an incorrect amount of available disk space on Linux.
  • The most recent package was not selected in the Altair HyperWorks Products Installer (main installer) Choose Install Set panel in some cases.
  • Multiple successive spaces in the installation directory or shortcut folder caused an issue on Windows.
  • Running the NETSETUP client installer as a non-administrative user now works properly.