3D Viewer FAQ

3D Viewer FAQs

The following is a list of frequently asked questions about the EarthVision 3D Viewer program evview.

Q: For Sun workstations, what graphics hardware is required for running the 3D Viewer?
Q: For Sun workstations, what OpenGL software is required for running the 3D Viewer?
Q: How can I diagnose problems running the 3D Viewer on the Sun Ultra?
Q: How can I drape a contour map of one surface on top of a different surface in the 3D Viewer?
Q: How can I convert my GIF or TIFF image to the format required by the 3D Viewer for image draping?
Q: How can I tell what command line arguments or environment variable settings are allowed in the 3D Viewer?
Q: What are the various 3D Viewer environment variable settings and what do they do?
Q: Dual-Headed Information

Note: In all scripts and command lines that follow, a backslash ( \ ) at the end of a line indicates that the current line is continued on the line that follows. When creating the script or typing the command line, these lines should be entered as one continuous line without the backslash.

1. For Sun workstations, what graphics hardware is required for running the 3D Viewer?

Sun now has two types of 3D graphics hardware that can be used for running the 3D Viewer.

The "Creator3D" series of graphics hardware has been around for several years, and has just been newly released in its 3rd generation. 3D Viewer performance benchmarks on the "Series 3" Creator3D boards has been very impressive.

The "Elite3D" is Sun's new family of high performance graphics boards. Performance numbers have been somewhat higher than Creator3D.

Either of these graphics options can be run in Sun's Ultra desktop family (Ultra 10, 30, 60). The Ultra 5, a low-end desktop machine, only comes with "on-board" graphics, and is really meant more for 2D applications. As such, its performance is probably not sufficient for the 3D Viewer.

More information on hardware configuration requirements can be obtained at the following:

http://www.dgi.com/config.shtml

2. For Sun workstations, what OpenGL software is required for running the 3D Viewer?

The Dynamic Graphics 3D Viewer software requires third-party 3D software called OpenGL. The OpenGL software typically comes from the hardware vendor (SGI, Sun, IBM, etc.). The difference between SGI and Sun is that SGI pre-installs OpenGL on the workstation, so when an SGI machine is purchased, chances are that 3D applications like the 3D Viewer will be able to run right away. Sun requires its OpenGL to be installed from separate CDs that they distribute or that can be downloaded from their web site.

For EarthVision 5.0 on a Sun Ultra, OpenGL 1.1.1 is required.

EarthVision 5.0 requires Open GL 1.1.1 Runtime for Solaris for running the 3D components of EarthVision 5.0. OpenGL can be obtained from Sun via their web site free of charge. Sun maintains the following web sites regarding OpenGL:

www.sun.com/solaris/opengl

Information on OpenGL issues

www.sun.com/solaris/opengl/download/verify_install.html

Information on verifying an OpenGL installation

www.sun.com/solaris/opengl/download

Information on downloading OpenGL

The user must register at this site and download four software packages (make sure all four check boxes are selected; one for each package). The required packages are:

SUNWffbgl
SUNWglrt
SUNWglrtu
SUNWglwrt

After downloading the file, extract the subsets using the tar command, and then run the INSTALL script that comes with the packages.

Note: It is very important that the workstation be rebooted after the INSTALL script is completed, as this completes the installation procedure.

In addition, $OPENWINHOME/lib must be added to each user's LD_LIBRARY_PATH variable.

3. How can I diagnose problems running the 3D Viewer on the Sun Ultra?

The process of installing OpenGL on a Sun, and getting it configured to run, is something that can be done incorrectly any number of ways. The script ultra.diag is intended to help diagnose problems with running EarthVision's 3D Viewer on Sun Ultras running OpenGL.

To get the most accurate information, the following is required:

Run the script in the environment of an EarthVision user.
Make sure the DGIHOME variable is set correctly.
Sit at the Ultra console to run this script.

To run short version of diagnostics, just type the name of this script:

ultra.diag

To run more comprehensive diagnostics, put in a word after the script file name:

ultra.diag full

After this script is run, the following OpenGL demo should be run:

/usr/openwin/demo/GL/ogl_install_check

OpenGL information and updates can be obtained at the following: http://sw.sun.com/solaris/opengl

4. How can I drape a contour map of one surface on top of a different surface in the 3D Viewer?

You can easily drape a color-filled contour map already created in EarthVision on to the top of any surface displayed in the 3D Viewer. Simply bring up the color-filled contour map in evzplot (evzplot <filename>.plt; or, as the map is being created, simply have the file display on the screen) and create an XWD file from the image, using the File -> Print -> Save xwd Screen Dump function. Alternatively, if the file already exists and so you can get maximum resolution automatically, you can use the following command:

evzplot -screenDump contour_map.xwd \-maximize <filename>.plt

After you have the xwd file, you can convert it to an RGB file, using the following command:

fromxwd contour_map.xwd contour_map.rgb

Then you can drape the RGB file, contour_map.rgb, on the model using the commands on the 3D Viewer's Image menu.

5. How can I convert my GIF or TIFF image to the format required by the 3D Viewer for image draping?

Dynamic Graphics provides some "gift" utilities in $DGIHOME/ev5/dgi_gifts that can convert from (and to) various commonly used image file formats to the SGI-format image file (often just called "rgb" files since they normally end with the suffix .rgb).

Programs for converting to rgb file format are: fromgif, fromppm, fromsun, fromtiff, fromxwd

Programs for converting from rgb file format to another are: togif, topics, toppm, tops, tosun, totiff, toxwd

In addition, three other useful image utilities are:

ipaste <file.rgb> - "paste" or display an image file.

istat <file.rgb> - gives statistics, such as the height and width in pixels, for the image file.

izoom <infile> <outfile> <xscale> <yscale> - scale an image file by user-specified X and Y scale factors, and output to a separate image file.

6. How can I tell what command line arguments or environment variable settings are allowed in the 3D Viewer?

The -h option provides help on which command line options are available in the 3D Viewer:

racerx 1316% evview -h
Usage: evview files -options

FILES (Used for sequencing, not for simultaneous display)
     <Faces file>           (.faces suffix)
     <2-D grid file>        (.2grd suffix)
     <3-D grid file>        (.3grd suffix)
     <Scattered data file>  (.dat, .pdat, .path suffixes)

(A single Vue file can follow one of the above data files):

     <Faces Vue file>       (.vue suffix)
     <2-D grid Vue file>    (.2gvue suffix)
     <3-D grid Vue file>    (.3gvue suffix)
     <Scat data Vue file>   (.dvue suffix)

(A single file containing a list of files to load):

<Display list file> (.dlist suffix) (simple listof files)
<Script file> (.script suffix) (uses specific keywords)

OPTIONS
     -c                     Use large arrow cursor
     -d                     Print data fields used and exit
     -dual                  Enable dual screen                              display (if available)
     -env                   Print all environment                              variables and exit
     -feature <feature>     Requested license feature
     -h                     Print this message
     -m                     Omit menu panel display
     -ml                    Display menu panel on                              left side of screen
     -mr                    Display menu panel on                              right side of screen
     -si <directory>        Input Vue files for                              synchronized 3D Viewers
     -so <directory>        Output Vue files for                              synchronized 3D Viewers
     -symbolFile <file>     Specify symbols file for annotation
     -V                     Print version and exit
     -v '<param> <value>'   Set a single Vue file parameter
     -vo <file>             Output named Vue file                              after each redraw

The FILES section that describes which types of EarthVision data files can be viewed in the 3D Viewer, what the associated vue files are for each model, and how the models can be sequenced.

Following the FILES section is an OPTIONS section that describes individual settings for enabling a particular feature, e.g, a dual-headed display or toggling on the large arrow cursor.

The -env option lists all the environment variable settings that can affect the 3D Viewer. This command is described in more detail in the environment variable settings FAQ list item.

The -d option lists all the scattered data field names that the 3D Viewer reads in and recognizes as "special." EarthVision has a large number of data field names, but currently the 3D Viewer only reads in a subset of these (X, Y, Z, P, LINEID, etc.) These values in these fields can be directly edited, displayed in the 3D Viewer information box, or utilized in some manner in the display of the point, e.g., color or size.

7. What are the various 3D Viewer environment variable settings and what do they do?

Typing evview -env prints out all the environment variables that the 3D Viewer recognizes and gives a brief one-line explanation of each. Expanded definitions are given below. (Note: typing unsetenv ENV_NAME disables the previous setting.)

1) setenv DGIDEBUG

The 3D Viewer prints out the arguments passed to it, as well as any arguments passed to other programs called from within the 3D Viewer (e.g., "evdwddisplay", "evtieline", "izoom", "ev_slice", "ev_wellpath", "ev_conv").

2) setenv DGIPRINTER <printer_name>

Setting this variable causes the 3D Viewer to bypass the pop-up menu of available printers and use the specified printer instead. For example, DGIPRINTER could be set to "tekpr" so that the 3D Viewer uses the printer command: lp -dtekpr test.rgb.

3) setenv DGI_DEFAULT_BOLD_WIDTH <num>

Changes the default bold width for annotation lines, in plot page units. For example, DGI_DEFAULT_BOLD_WIDTH could be set to 0.03 inches. The line widths are drawn as follows:
line width        pixel width
----------        -----------
<= 0.01               1
> 0.01 && <= 0.02     2
> 0.02 && <= 0.03     3
> 0.03                4

4) setenv DGI_DEFAULT_LINE_WIDTH <num>

Changes the default line width for annotation lines, in plot page units. For example, DGI_DEFAULT_LINE_WIDTH could be set to 0.03 inches. The line widths are drawn as follows:
line width        pixel width
----------        -----------
<= 0.01               1
> 0.01 && <= 0.02     2
> 0.02 && <= 0.03     3
> 0.03                4

5) setenv EV_DISABLE_OVERLAY

If a machine has overlay capabilities, setting this environment variable disallows the 3D Viewer from making use of these. Occasionally, hardware bugs involve overlay planes, and this environment variable allows the 3D Viewer to forgo using them (primarily used for testing purposes).

6) setenv EV_DISABLE_SLICE

When loading an unsliced faces file, the ev_slice program is called for calculating the exterior slices of the model. If ev_slice returns an error due to bad polygons being generated (e.g., concave), normally, the 3D Viewer indicates that slicing failed and does not load the file. Setting this variable allows the 3D Viewer to continue anyway, at the expense of possibly rendering some polygons incorrectly.

7) setenv EV_ENABLE_EQFOCI

Setting this variable enables the Earthquake Foci menu and two associated toggle buttons. It also allows scattered data files with the following fields to be read and drawn as "beach balls", or bi-colored spheres, oriented in the direction as specified by these six fields:
TPLUNGE, TAZIM, PPLUNGE, PAZIM, NPLUNGE, NAZIM

8) setenv EV_ENABLE_HI_RES_OUTPUT

This environment variable must be set in order to have the high-resolution output function. On Sun Ultra Creator3D systems, the high-resolution output function requires a large amount of swap space, and can be quite slow.

9) setenv EV_STEREOINWIN_FORMAT <format>

On SGI systems that allow for separate stereo buffers (also known as "Stereo-in-window"), this environment variable specifies the video format to use when entering stereo mode. The default format is 1024x768_96s, which indicates a change of screen resolution to 1024 x 768 and a frequency rate of 96 HZ.

10) setenv EV_STEREONONE_FORMAT <format>

On SGI systems that allow for separate stereo buffers (also known as "Stereo-in-window"), this environment variable specifies the video format to return to after leaving stereo mode. The default format is 72HZ.

11) setenv EV_ZBUF_PRIORITY

If the eye point is very close to the look point (i.e., the 3D Viewer is zoomed way in on a surface or point), setting this parameter will give the best Z-buffer resolution at the expense of possible clipping objects far in the distance.

12) setenv PRINT_SCRIPT <directory_path>

Setting this variable will cause the 3D Viewer to call the specified program when printing the screen image to a printer, instead of using the default directory $DGIHOME/bin/printer_script.

8. Running the 3D Viewer on Dual-headed Workstations

The 3D Viewer can be started to automatically set up the program to run on a dual-headed workstation. By default, all EarthVision modules as well as the 3D Viewer model and menu windows appear on the screen to which the DISPLAY environment variable is set. The -dual command-line option can be used to indicate that the workstation has two heads, in which case the 3D Viewer model window will appear wherever DISPLAY is set and the menus will appear on the other screen. Since, by default, all other EarthVision modules also appear on the DISPLAY screen as well, the evview -display command-line option can be used to set the model window to appear on the second screen (with the menus appearing on the same window as the other EarthVision modules). Some aspects of setting up the 3D Viewer to run on a dual-headed workstation are machine-dependent. The instructions for each of the following cases follows.

a. Dual-headed SGI or Sun Ultra with two Creator3D or Elite3D boards

b. Dual-headed SGI with one 24" (1600x1200 resolution) screen

c. Dual-headed Sun Ultra with one Creator3D or Elite3D board

a. Dual-headed SGI or Sun Ultra with Two Creator3D/Elite3D Boards

In general, dual-headed SGIs have both screens attached to 3D graphics boards so that the 3D Viewer can be displayed on either screen. The same is true for Sun Ultras when they have two Creator3D or Elite3D boards. So, to set DISPLAY to screen 0 and have the 3D Viewer model window display on one screen and the 3D Viewer menus (and all other EarthVision modules) on the other screen, the following commands are used:

setenv DISPLAY :0.0

evview -dual -display :0.1

These commands temporarily set all EarthVision modules and the 3D Viewer menus to appear on one screen (screen 0) and the 3D Viewer model window to appear on the other screen (screen 1).

To make these changes "permanent," these commands can also be added to the $DGIHOME/ev5/etc/dgi.evrc.custom file (a copy of the $DGIHOME/ev5/etc/dgi.evrc file must be made and renamed as $DGIHOME/ev5/etc/dgi.evrc.custom if a dgi.evrc.custom file does not already exist). The following line can be either edited or copied and renamed (as shown below; the 3D Viewer option name is changed):

"3D Viewer" _V f.checkexec "evview"

"3D Viewer" _V f.checkexec \ "evview"

"3D Viewer Dual Display" _D f.checkexec \ "evview -dual -display :0.1"

When using the 3D Viewer Dual Display function, the DISPLAY would have to be set to :0.0.

These changes cause the 3D Viewer to come up on the second screen only when the 3D Viewer is started from the Visualization pull-down menu in the main EarthVision window. To have the 3D Viewer model window start up on screen 1 whenever any 3D View push button in EarthVision is selected, the $DGIHOME/ev5/app-defaults/EarthVisionCommon file must be edited and the following line must be changed from

*evviewr: evview

*evviewr: evview -dual -display :0.1

b. Dual-headed SGI with One 24" (1600x1200 Resolution) Screen

When one of the screens is 24 inches with 1600x1200 resolution, the screens have a letterbox opening making the EarthVision menus squished. Many possible solutions are available for solving this issue; one solution follows; however, contact Technical Support for more examples.

If the MXI board is screen 0 and is physically on right of the SI board, and the SI board is screen 1 (and physically on the left of the MXI board, as shown below),

then the Xsgi command (in /usr/var/X11/xdm/Xservers) can be changed to specify the following:

-hw board=0,right=1 -hw board=1,left=0

In other words, board 0 is at the right of board 1, and board 1 is at the left of board 0.

The /usr/var/X11/xdm/Xservers file must be edited and the line similar to the one below:

:0 secure /usr/bin/X11/X -nobitscale -c \-pseudomap 4sight -solidroot sgilightblue \ -cursorFG red -cursorBG white

must be changed to

:0 secure /usr/bin/X11/X -nobitscale -c \ -pseudomap 4sight -solidroot sgilightblue \ -cursorFG red -cursorBG white -hw \
board=0,right=1 -hw board=1,left=0

c. Dual-headed Sun Ultra with One Creator3D/Elite3D Board

Some dual-headed Sun Ultras have one head operating from a Creator3D or Elite3D graphics board and another head operating from a simple 2D TGX board. The result is that the 3D Viewer and its menus can only be displayed on the head attached to the Creator3D or Elite3D graphics board. The Creator3D or Elite3D graphics board can be either screen 0 or screen 1, depending on how OpenWindows is started. In order to set which screen is the Creator3D or Elite3D and which is the TGX board, before logging in, you must select the Command Login function from the Options menu. At the prompt, type

/usr/openwin/bin/openwin -dev /dev/fb0 \ -dev /dev/cgsix0

(to have the Creator3D/Elite3D on screen 0 and the TGX board on screen 1)

/usr/openwin/bin/openwin -dev /dev/cgsix0 \ -dev /dev/fb0

(to have the Creator3D/Elite3D on screen 1 and the TGX board on screen 0)

By default (as discussed earlier), all EarthVision modules and the 3D Viewer come up on the screen to which the DISPLAY is set. In order to have all EarthVision modules appear on one screen (with the TGX board) and the 3D Viewer to appear on the other screen (with the Creator3D or Elite3D board), the following commands must be typed:

setenv DISPLAY :0.0 (where screen 0 has the TGX board)

evview -display :0.1 (where screen 1 has the Creator3D/Elite3D board)

If screen 0 has the Creator3D or Elite3D board, then the "0.0" and "0.1" in the above commands must be reversed.

Note: On this type of dual-headed workstation, the 3D Viewer model window and menus will be on the same screen; they cannot be separated as when running on a dual-headed SGI or a Sun Ultra with two Creator3D or Elite3D boards. As such, the -dual command is not used.

These commands temporarily set all EarthVision modules and the 3D Viewer menus to appear on one screen (screen 0) and the 3D Viewer model window to appear on the other screen (screen 1).

To makes these changes "permanent," these commands can also be added to
the $DGIHOME/ev5/etc/dgi.evrc.custom file (a copy of the $DGIHOME/ev5/etc/dgi.evrc file must be made and renamed as $DGIHOME/ev5/etc/dgi.evrc.custom if a dgi.evrc.custom file does not already exist).

The following line can be either edited or copied and renamed (as shown below; the 3D Viewer option name is changed):

"3D Viewer" _V f.checkexec \ "evview"

to:

"3D Viewer" _V f.checkexec \ "evview"

"3D Viewer Dual Display" _D f.checkexec \ "evview -display :0.1"

When using the 3D Viewer Dual Display function, the DISPLAY would have to be set to :0.0.

(Again, the above commands assume that the Creator3D or Elite3D board has been set to screen 1.)

These changes cause the 3D Viewer to come up on the second screen only when the 3D Viewer is started from the Visualization pull-down menu in the main EarthVision window. To have the 3D Viewer window start up on screen 1 whenever any 3D View push button in EarthVision is selected, the $DGIHOME/ev5/app-defaults/EarthVisionCommon file must be edited and the following line must be changed from

*evviewr: evview

*evviewr: evview -display :0.1

(Again, the above commands assume that the Creator3D/Elite3D board has been set to screen 1 and would have to be changed from "0.1" to "0.0" if the Creator3D/Elite3D board is set to screen 0.)

[Home] [Corporate] [Events & News]
[EarthVision] [Support] [Services] [Contact Us]

Last updated: March 22, 2007