.if n .sp 1
.if t .sp .5
..
-.TH XScreenSaver 1 "27-Apr-99 (3.10)" "X Version 11"
+.TH XScreenSaver 1 "10-May-99 (3.12)" "X Version 11"
.SH NAME
xscreensaver - graphics hack and screen locker, launched when the user is idle
.SH SYNOPSIS
.B color
Use the best of the color visuals, if there are any.
.TP 8
+.B GL
+Use the visual that is best for OpenGL programs. (OpenGL programs have
+somewhat different requirements than other X programs.)
+.TP 8
.I class
where \fIclass\fP is one of \fBStaticGray\fP, \fBStaticColor\fP,
\fBTrueColor\fP, \fBGrayScale\fP, \fBPseudoColor\fP, or \fBDirectColor\fP.
after an hour or two even if you've told it not to. This is fixed by SGI
patches 2447 and 2537.
.TP 8
-.B OpenGL Programs and Visuals
-Some of the graphics demos included with xscreensaver make use of the
-OpenGL (or MesaGL) 3D library, if it is available. It is possible (even
-likely) that \fIxscreensaver\fP's notion of the ``\fIbest\fP'' visual is
-not quite right for these GL programs.
-
-The odd thing about GL programs is that, unlike normal X11 programs, they
-tend to work best on a visual \fIhalf\fP as deep as the depth of the screen,
-since that way, they can do double-buffering. Try it and see, but you will
-probably find that, for these particular programs, you should specify the
-deepest visual that is half as deep as the screen. (See the discussion
-of the \fBprograms\fP resource in the \fIConfiguration\fP section, above.)
-
-For example, on a screen that supports both 24-bit TrueColor and 12-bit
-PseudoColor visuals, the 12-bit visual will probably work best (this is true
-of base-model SGI Indys: the 0x29 visual is the one you want.)
-
-Oddly, on SGI O2s (machines that have serious hardware support for GL), the
-12-bit PseudoColor visual looks awful (you get a black and white, flickery
-image.) On these machines, the visual you want turns out to be 0x31.
-However, 0x31 is but \fIone\fP of the \fIeight\fP 15-bit TrueColor visuals
-(yes, 8, and yes, 15) that the O2 X server provides. This is the only visual
-that works properly: as far as
-.BR xdpyinfo (1)
-is concerned, all of the 15-bit TrueColor visuals are identical, but some
-flicker like mad, and some have deeply weird artifacts (such as hidden
-surfaces that show through, as if depth worked backwards!)
-
-I suppose these other visuals must be tied to some arcane hardware feature...
-If anyone would care to explain it to me, that would be great.
-
-Your mileage, therefore, may vary dramatically.
-.TP 8
.B MesaGL and Voodoo Cards
If you have a 3Dfx/Voodoo card, the default settings for xscreensaver will
run the GL-based graphics demos in such a way that they will not take
.BR bouboule (1),
.BR braid (1),
.BR bsod (1),
+.BR bubble3d (1),
.BR bubbles (1),
.BR cage (1),
+.BR compass (1),
.BR coral (1),
+.BR critical (1),
+.BR crystal (1),
.BR cynosure (1),
.BR decayscreen (1),
.BR deco (1),
+.BR deluxe (1),
+.BR demon (1),
+.BR discrete (1),
+.BR distort (1),
.BR drift (1),
.BR epicycle (1),
.BR fadeplot (1),
.BR flag (1),
.BR flame (1),
+.BR flow (1),
.BR forest (1),
.BR galaxy (1),
.BR gears (1),
+.BR glplanet (1),
.BR goop (1),
.BR grav (1),
.BR greynetic (1),
.BR jigsaw (1),
.BR julia (1),
.BR kaleidescope (1),
+.BR kumppa (1),
+.BR lament (1),
.BR laser (1),
.BR lightning (1),
.BR lisa (1),
.BR lissie (1),
.BR lmorph (1),
+.BR loop (1),
.BR maze (1),
.BR moebius (1),
.BR moire (1),
.BR munch (1),
.BR noseguy (1),
.BR pedal (1),
+.BR penetrate (1),
.BR penrose (1),
+.BR phosphor (1),
.BR pipes (1),
+.BR pulsar (1),
.BR pyro (1),
.BR qix (1),
.BR rd-bomb (1),
.BR sierpinski (1),
.BR slidescreen (1),
.BR slip (1),
+.BR sonar (1),
.BR sphere (1),
.BR spiral (1),
+.BR spotlight (1),
.BR sproingies (1),
+.BR squiral (1),
.BR stairs (1),
.BR starfish (1),
.BR strange (1),
.BR superquadrics (1),
.BR swirl (1),
+.BR t3d (1),
.BR triangle (1),
.BR truchet (1),
.BR vines (1),
+.BR wander (1),
.BR worm (1),
+.BR xflame (1),
.BR xjack (1),
.BR xlyap (1),
+.BR xmatrix (1),
.BR xroger (1),
.BR bongo (1),
.BR ico (1),
projects / xscreensaver / blobdiff