[Go to Previous] [Go to Next]


Common Run-Time Errors FAQ

Q. What do I do if I get a 'Could not create a graphics configuration' error?

A. First, check for the most updated video card driver. If the problem still remains, the 32bit Linux installer comes with an option to install Java3D 1.3. Rerun the installer and select to install Java3D 1.3.

Q. What do I do if I get 'JAVA 3D Error: GLX extension is not supported' and 'Could not create a graphics configuration' errors?

A. GLX is an extension that must be supported by the graphics card.  This error is most likely occurring because the graphics drivers for RHEL are not properly configured.

Assuming that the latest graphics drivers are installed, they must be configured in the window system configuration file. Since RHEL uses Xorg, look in the file

/etc/X11/xorg.conf

and see if there are any references to "GLX" or "glx" (and possibly "dri").  If there are, try uncommenting them and rebooting.

Q. What do I do if I see 'Connection refused' and 'No public datasets found' errors when connecting to the listed data servers?

A. If you have a firewall and are trying to get data from the remote servers (image, radar, point, upper air and profiler data), error messages such as "Error opening connection ... Operation timed out" or "No Data Available" are normal.  For these servers to send data, your firewall software must allow connections on ports 112 (ADDE) and 8080 (THREDDS Data Server).

Q. Why am I having drawing problems on Monitor2 of a two-monitor system?

A. A common error seen with this problem is '...adding a container to a container on a different GraphicsDevice'. Some graphics card/driver combinations don't allow these functions to work in Monitor2 of two-monitor systems. For now, you can simply move the McIDAS-V windows to Monitor1 then successfully add new tabs and run bundles.

If you are running Red Hat with a NVIDIA graphics card using TwinView and are having problems, go to the preferences, click on the primary display, and make sure the "Make this the primary display..." checkbox is checked.

Q. Why is there no map drawn in the McIDAS-V Main Display window?

A. Try changing your memory to use 1 GB or lower and restart McIDAS-V. You can change the amount of memory used by McIDAS-V by editing the Maximum Heap Size in the Advanced tab of the Preferences by selected Edit->Preferences... from the Main Display window.

Q. Why do my images display blank (black or white) when there should be valid data?

A. The first thing to do is to make sure that your graphics drivers are up to date. If this does not solve the problem, another option is to change the amount of memory allocated to McIDAS-V. From the Main Display window's menu bar, select Edit->Preferences. This opens a User Preferences window, where you want to select the Advanced tab. At the top of the window there are two options for selecting memory. Click the radio button that allows you to specify the numerical value of memory allocated to McIDAS-V. Enter in a value of 512 megabytes and click OK to save the change. Then exit and restart McIDAS-V (changes in the Advanced User Preferences require a restart of McIDAS-V to take effect). If this resolves the issue of white images, you can start increasing the memory until the problem appears again. Stay below the memory value that produces the problem.

We have also received reports of this problem (blank images in the Main Display window) occurring on computers with the Mobile Intel 4 Series Express Family of graphics cards. If you have a computer with that configuration and are seeing the problem, try setting the card's "Vertex Processing" configuration setting to "Enable Software Processing". That setting is recommended because it will likely work with a typical amount of memory allocated to McIDAS-V (e.g., 80% of available). If the "Vertex Processing" option is set to a different value (e.g., "Application Settings" and "Default settings"), you may have to select a memory value of 800 MB or less in order to avoid the problem.

Q. Why do I get an error that starts something like "Unexpected Signal : 11 occurred at PC=0x6F79CE1" when starting McIDAS-V under Linux?

A. If the error message also includes a line that is looking for a Library with "dri" in it's name (e.g.: Library=/usr/X11R6/lib/modules/dri/i915_dri.so), it means that you are trying to load the DRI library in your X server which is not compatible with Java 3D. You need to comment out the line:
Load "dri"

in your X server configuration file (xorg.conf or XF86Config).


[Go to Previous] [Go to Next]