The following table lists the recommended CAE/CAD graphic boards to use with HyperWorks** applications. The most recent vendor/manufacturer drivers should be used and all driver support for these cards should be addressed to the appropriate manufacturer of the graphic board.

AMD (FirePro 3D series)

NVIDIA (Quadro series)

**In order to provide advanced graphical capabilities and features in the HyperWorks products, there is a minimum requirement of OpenGL 3.2. Not meeting this hardware and driver requirement may cause problems with newer HyperWorks versions and features. Performance of HyperWorks may be degraded with compositing desktop effects enabled under Linux environments.

**NOTE: HyperWorks Graphical User Interface (GUI) products (HyperMesh, HyperView, HyperGraph, MotionView, etc), when used with Ultra High Definition (UHD) displays consisting of 1920x1200 or higher (for example, 3200x1800, 3840x2160 or 4096x2160), may result in graphical problems. Some GUI items may not be displayed correctly, some functionality such as image captures many not capture images correctly, and window selection may become an issue. HyperWorks 2017 does not officially support these high screen resolutions. We suggest setting your resolution to 1920x1200 or lower to resolve or minimize these types of issues from occurring. Our development teams are aware of these problems and are working closely with the hardware vendors to find a quick resolution to the issue.

**In order to provide advanced graphical capabilities and features in the HyperWorks products, there is a minimum requirement of OpenGL 3.2. Not meeting this hardware and driver requirement may cause problems with newer HyperWorks versions and features. Performance of HyperWorks may be degraded with compositing desktop effects enabled under Linux environments.

Under Linux, HyperWorks 2017 sets the environment variable XLIB_SKIP_ARGB_VISUALS=1 in the startup scripts, which may degrade GUI menu performance. To override this option set the variable XLIB_SKIP_ARGB_VISUALS=0 within the system’s or user’s environment.

Compiz or “Desktop Effects” under the Gnome Linux windowing environment may degrade performance if enabled. Altair recommends not using the Compiz or “Desktop Effects” and instead use the standard windowing themes.

**NOTE: HyperWorks Graphical User Interface (GUI) products (HyperMesh, HyperView, HyperGraph, MotionView, etc), when used with Ultra High Definition (UHD) displays consisting of 1920x1200 or higher (for example, 3200x1800, 3840x2160 or 4096x2160), may result in graphical problems. Some GUI items may not be displayed correctly, some functionality such as image captures many not capture images correctly, and window selection may become an issue. HyperWorks 14.0.120 does not officially support these high screen resolutions. We suggest setting your resolution to 1920x1200 or lower to resolve or minimize these types of issues from occurring. Our development teams are aware of these problems and are working closely with the hardware vendors to find a quick resolution to the issue.

For NVIDIA GPU based laptops/notebooks the Optimus power saving option in the BIOS should be disabled and the NVIDIA drivers properly installed for optimal performance in HyperWorks.

For AMD GPU based laptops/notebooks; the Enduro/Switchable Graphics power saving option should be disabled and the AMD drivers properly installed for optimal performance in HyperWorks.

All power saving modes, settings and governors for CPU frequencies and GPU performance should be set to maximum settings in order to get the optimal performance out of HyperWorks. This includes smooth graphics and high frame rates (FPS) on Windows and Linux platforms.

The following table lists the supported Tesla graphic boards for use with the Altair HyperWorks solvers for high-powered GPU computing. This includes HyperWorks OptiStruct direct solver and RADIOSS implicit iterative solver computations.

The NVIDIA Driver Update recommendation is to use the Custom installation option and select the Perform clean installation option to validate that there are no conflicts in DLL/drivers. Below is an image of the option mentioned. The same should be done with AMD hardware and drivers as well using AMD’s custom uninstall tools.