Fluent Graphics Issues - Errors / Resolutions
|
The most common reason for graphics issues is because you have an older or unsupported video card/driver installed on your system. ANSYS certifies the NVIDIA Quadro FX high-end line or the ATI FireGL/Pro high-end line only. Problem Description: Fluent / TGrid Dual Monitor Issue. If you are using a dual monitor setup, Fluent will display a RED background or will display poor graphics or no graphics or you will receive a Floating Point error when displaying graphics. TGrid also displays the same behavior. 1) Download the latest NVIDIA drivers (the option I'm about to use is not in older drivers. Our old drivers have 3 radio-buttons for multi-display type, new drivers have 5 buttons) 2) On the NVIDIA control panel, 'set up multiple displays' and change the type from 'Dualview'(default) to type "Horizontal Span", and then set the display resolution to be 3600x1200 pixels (2xwidth, 1xnormal height of my monitors), then the problem is fixed. OR Uncheck "Embed Graphics Windows" in the Fluent Launcher. OR Disable dual monitors then launch Fluent or TGrid. Once Fluent or TGrid is opened, enable dual monitors again. ------------------------------------------- Problem Description: Fluent crash after a large number of iterations when monitors are plotted to graphics windows. This behavior has been seen in Fluent both within Workbench and when running Fluent standalone. A large number of iterations are sometimes necessary on transient runs with a small time step. The crash often occurs at 32768 iterations, which is 2^15. The following error is seen in the Fluent console window: No error handler available Error: Cortex received a fatal signal (SEGMENTATION VIOLATION). Error Object: () The stack backtrace in the terminal or shell might look like (in part) : Stack backtrace generated for process id 8212 on signal 11 : fluent[0x4b675a] /lib64/libc.so.6[0x3512c30280] /usr/lib64/libX11.so.6(XFreeFont+0x37)[0x35148282c7] /usr/local/ansys_inc/v120/v120/fluent/lib/lnamd64/libhoops1417.so[0x2b779ac7d203] /lib64/libc.so.6(exit+0xe5)[0x3512c33355] /usr/lib64/libX11.so.6(_XIOError+0x27)[0x3514849f97] /usr/lib64/libXt.so.6(_XtWaitForSomething+0x47b)[0x352762cc2b] Please include this information with any bug report you file on this issue! Resolutions/Workaround: Update the video card to a supported certified video card (ANSYS certifies the NVIDIA Quadro FX high-end line or the ATI FireGL/Pro high-end line only) *Locating the Video Card/Driver* Windows XP 1.Open up Control Panel > Display > Settings > Advanced > Adapter (this will tell you what video card you are using). 2.Properties > Driver > Driver Version (this will tell you what driver version you are using). 3.Once you have your video card and driver information, go to the video card vendor's website and download a newer driver. Choose one of the links for your video card vendor's website. Make sure you remove the existing driver before you install the newer driver. Windows 7 1.Open Control Panel > Device Manager > Display Adapters > Driver tab > Driver Version. (If you are prompted for an administrator password or confirmation, type the password or provide confirmation). 2.Once you have your video card and driver information, go to the video card vendor's website and download a newer driver. Choose one of the links for your video card vendor's website. Make sure you remove the existing driver before you install the newer driver. *Remove the existing driver* Windows XP: 1.Open up Control Panel > Add/Remove Programs > Uninstall NVIDIA or ATI Drivers. 2.Reboot the machine. 3.Install the newer downloaded driver. 4.Reboot the machine again. Windows 7: 1.Open Control Panel > Device Manager > Display Adapters > Driver tab > Uninstall. (If you are prompted for an administrator password or confirmation, type the password or provide confirmation.) 2.Reboot the machine. 3.Install the newer downloaded driver. 4.Reboot the machine again. IMPORTANT NOTE: It is very important that you follow these steps exactly, especially removing the existing driver, rebooting the machine, and then installing the newer driver. LINUX/UNIX To view your graphics card and driver information output: /sbin/lspci glxinfo Local Display on Linux/Unix With OpenGL Driver Verify that the system has a native driver from the graphics vendor and it is using it. Linux/Unix systems come with the mesa driver by default. If your certified NVIDA or ATI graphics card is using the mesa driver instead of vendor driver graphics, performance will decrease. Verifying the Driver Fluent is Using 1.Launch Fluent. 2.Choose Display -> Options... -> Info (this will print a message in Fluent console either (a) "Driver GLX_Hardware" or (b) "Driver GLX_Software". For the best performance it should come output (a), as it uses OpenGL hardware. Read below for information about how to resolve most other Fluent graphics issues. Fluent 12.x - Windows 1.Check to make sure Fluent, when launched, is using OpenGL. 2.In Fluent, choose the Help menu, then Version. Look for the "Graphics Version": ###.#, xxx/win line. If it states msw/win, Fluent is NOT using the OpenGL driver. You can force Fluent to use OpenGL by putting the following in the "Environment" tab in the Fluent 12.x Launcher: LAUNCHER_FLUENT_OPTIONS=-driver opengl IMPORTANT NOTE: Making this change in the Fluent Launcher will only work when running Fluent outside of Workbench. This environment variable will work inside of Workbench for ANSYS Fluent version 13.x. Fluent 12.x - Linux/UNIX 1.Check to make sure Fluent, when launched, is using OpenGL. 2.In Fluent, choose the Display Menu Driver> Info button. 3.In the Fluent window look for the Driver line. If it states Driver X11 v.#.## then Fluent is NOT using the OpenGL driver. You can force Fluent to use OpenGL by putting the following in the "Environment" tab in the Fluent 12.x Launcher: LAUNCHER_FLUENT_OPTIONS=-driver opengl IMPORTANT NOTE: Making this change in the Fluent Launcher will only work when running Fluent outside of Workbench. This environment variable will work inside of Workbench for ANSYS Fluent version 13.x. *Command Line Options* If running Fluent at the command line you can also use the following flags: Windows: fluent 3d -driver opengl Linux/UNIX: fluent 3d -driver opengl Remote Access Best Practices Running any ANSYS application using remote access software is not certified or supported. If the machine you are remoting into has a PCIx16 slot with an NVIDIA Quadro FX or AMD ATI FirePro/FireGL high-end graphics card it could work with some considerations. Remember that most servers DO NOT have a PCIx16 slot so this will not be possible. There are servers on the market that do offer this capability. Please check your hardware vendor's web site for more information. See the entire FAQ on this topic in Related Solution 2016636 : Remote Access Best Practices ------------------------------------- *ATI Radeon Drivers and FLUENT* ATI Radeon drivers usually conflict with FLUENT graphics and will crash FLUENT when displaying grids and contours. These graphic cards are not professional graphics cards and were never developed to run engineering applications like FLUENT. However, ATI has been aware of these issues and has posted some newer Catalyst drivers that might fix floating point errors or other graphics errors you might encounter. Visit the ATI download page at <a target=_blank href="http://www.amd.com/">http://www.amd.com/</a>http://www.amd.com/ and download the latest Catalyst drivers. If after you have installed a newer Catalyst driver and the graphics issues are still not resolved you can start FLUENT using the Microsoft Windows driver as a workaround. |
||
|