Abaqus 6.9-EF Graphics Devices
SIMULIA tests specific graphics devices to insure adequate performance with Abaqus/CAE and Abaqus/Viewer; the graphics devices that have been tested (or scheduled for testing) are listed in the table below. However, we cannot certify that these devices are completely compatible with all possible hardware and software configurations. Graphics cards certified with the 6.9-1 release are also supported with the 6.9-EF release. Full listing of the 6.9-1 supported graphics can be found here. Other devices may be compatible but have not been tested.
NOTE: Newer driver versions for the graphics card listed on this page are expected to work, but may not be compatible. We recommend that you use the tested driver version if you experience problems.
We may update graphics tuning parameters for graphics devices. These changes are intended to configure Abaqus to best utilize individual graphics devices. Updated graphics tuning parameters are included in the graphicsConfig.env file, which can be downloaded and placed in your Abaqus installation.
The use of graphics hardware acceleration on Windows platforms may cause display problems with some graphics adapters or drivers. Users may wish to disable graphics hardware acceleration to determine if a particular issue is specific to their graphics adapter or graphics driver.
Listing of tested configurations per platform:
- Windows/x86-32
- Windows/x86-32(laptop)
- Windows/x86-64
- Linux/x86-32
- Linux/x86-64
Windows/x86-32 | |||||
Vendor | Graphics Device | Graphics Memory | Driver Version | Operating System | Results |
AMD [ATI] | FirePro V3700 |
512MB | 8.633 | Windows XP SP2 | Pass |
NVIDIA | Quadro FX 1800 |
768MB | 190.38 | Windows XP SP2 | Pass |
Quadro FX 4800 |
1.5GB | 186.18 | Windows Server 2008 | Pass |
Windows Laptop (32-bit) | |||||
Vendor | Graphics Device | Graphics Memory | Driver Version | Operating System | Results |
AMD [ATI] | Mobility FireGL V5700 |
512MB | 8.563 | Windows XP SP2 | Pass |
Intel | GMA X3100 |
384MB | 6.14.10.4926 | Windows XP SP2 | Pass |
NVIDIA | Quadro FX 570M |
512MB | 178.74 | Windows XP SP2 | Pass |
Windows/x86-64 | |||||
Vendor | Graphics Device | Graphics Memory | Driver Version | Operating System | Results |
AMD [ATI] | FirePro V8700 |
1GB | 8.633 | Windows Vista Business* | Pass |
NVIDIA | Quadro FX 3700 |
512MB | 190.38 | Windows Server | Pass |
Quadro FX 4600 |
768MB | 190.38 | Windows 7 Professional* | Pass |
Linux/x86-32 | ||||||
Vendor | Graphics Device | Graphics Memory | Driver Version | X11 Version | Operating System | Results |
NVIDIA | Quadro FX 570 |
256MB | 180.44 | X.org 6.9.0 | SLES10 | Pass |
Linux/x86-64 | ||||||
Vendor | Graphics Device | Graphics Memory | Driver Version | X11 Version | Operating System | Results |
AMD [ATI] | FirePro 3750 | 256MB | 8.789 | X.org 6.9.0 | SLES 10 | Pass |
NVIDIA | Quadro FX 3400 | 256MB | 185.18.31 | Xorg 7.1.99 | SLES 10.2 | Pass |
Quadro FX 580 | 256MB | 185.18.31 | X.org 7.1.1 | RHEL 5.0 | Pass |
Additional Information
Abaqus/CAE and Abaqus/Viewer support OpenGL hardware graphics acceleration on all supported platforms. For instructions on how to turn off hardware acceleration, see How to Disable Graphics Hardware Acceleration to Resolve Graphics Incompatibility.
All Windows laptops are tested with their original factory display. Testing does not include any external display devices.
If the graphics device in which you are interested in is not listed on this page, you may submit a Request for Enhancement.
See Customer Submission of Requests-for-Enhancements (RFEs) for SIMULIA
To determine your graphics card and graphics card driver for Windows systems
It is best to use the system Display Properties dialog to get this information, but if you have difficulty, or if you only have remote access to the system, try the findVid program.
- Download the findVid program appropriate for your system (32-bit or 64-bit)
- Then run the executable in a command prompt window
- Following is example output from running the findVid.exe command
=============================================
C:\Temp>findVid32.exe
Device Name: NVIDIA Quadro FX 5600
Video Processor: Quadro FX 5600
Driver Date: 02/18/2009
Driver Version: 6.14.11.8208
Horizontal Res: 1280 pixels in 387 mm => 3.307493 pix/mm
Vertical Res: 1024 pixels in 310 mm => 3.303226 pix/mm
Display Settings: 1680 x 1050 @ 0,0 - 32-bit - 60 Hz============================================
Updating your graphicsConfig.env file
Follow these instructions for updating your graphicsConfig.env file. You should update each release of Abaqus 6.9-EF that you have installed (6.9-EF1, 6.9.EF2, ...). The examples given in the instructions show updating Abaqus 6.9-EF.
NOTE: The date stamp on the graphicsConfig.env file should help you determine which releases of Abaqus 6.9-EF you should update. If the date of the file is later than the creation date of the release (reported by abaqus whereami), then you should update that release.
- Find your Abaqus 6.9-EF version install directory and set your current directory to the site directory for that version.
% abaqus whereami
Abaqus Version 6.9-EF-1
Abaqus Site ID:
Abaqus is located in the directory /disk2/abaqus/6.9-EF-1
/disk2/abaqus/6.9-EF-1/cae/External/ebt
Sequence Information:
/disk2/abaqus/6.9-EF-1/cae: 2008_11_19-18.06.29 91470
% cd /disk2/abaqus/6.9-EF-1/site - Rename the existing graphicsConfig.env file
% cp graphicsConfig.env graphicsConfig.env.old
- Download the new graphicsConfig.env file by clicking on the file name in the browser window.
- Select the 'save as' option, and save the file in your Abaqus 6.9-EF-1 site directory. In the current example, the path to this directory is /disk2/abaqus/6.9-EF-1/site.
- Reset the permissions on the graphicsConfig.env file.
% chmod 644 graphicsConfig.env
* Defect number v67_0984:
Refresh issues occur when running ABAQUS/CAE on Windows Vista or Windows 7 with the Aero theme.When using multiple viewport windows, the viewports may become invalid after an expose event (like uncover) but will not refresh. This happens because the operating system tries to restore the viewport contents rather than asking the application (i.e /CAE) to redraw the window. The only recourse left to the user is to perform some action in the affected viewport so /CAE will redraw the window.
This issue is classified as a product limitation. There is currently no plan to address it.