summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Bucciarelli <davibu@tin.it>1999-02-25 19:10:30 +0000
committerDavid Bucciarelli <davibu@tin.it>1999-02-25 19:10:30 +0000
commit672f8ffe92841042c8d1268c8ece30d3e922516e (patch)
tree984c49a1449871af5a37058ecfbb73824b24c206
parent31edff1b5243aade7c2ff14de656876311960b4d (diff)
Updated to Voodoo driver v0.30
-rw-r--r--docs/README.3DFX36
1 files changed, 18 insertions, 18 deletions
diff --git a/docs/README.3DFX b/docs/README.3DFX
index 4431516e78..37f2d0cc67 100644
--- a/docs/README.3DFX
+++ b/docs/README.3DFX
@@ -1,5 +1,5 @@
- 3Dfx Glide device driver for Mesa 3.0
+ 3Dfx Glide device driver for Mesa 3.1
(see below for FAQ)
@@ -17,10 +17,10 @@ What do you need ?
under Linux (more information in the "Useful Glide Environment
Variables");
- - Mesa 3.0;
+ - Mesa 3.1;
- The 3Dfx Glide library 2.3 or later for your OS (the 2.4 works fine).
- The Voodoo2 requires the Glide library 2.51. The Glide 3.0 is not
+ The Voodoo2 requires the Glide library 2.51. The Glide 3.1 is not
compatible with the Glide 2.x so it doesn't work with the current
version of the driver;
@@ -81,18 +81,18 @@ Linux:
If your Glide libraries and headers are in a different directory
you'll have to modify the Mesa-config and mklib.glide files.
- - Unpack the MesaLib-3.0.tar.gz and MesaDemos-3.0.tar.gz archives;
+ - Unpack the MesaLib-3.1.tar.gz and MesaDemos-3.1.tar.gz archives;
- If you're going to use a newer Mesa/Glide driver than v0.27 then
unpack the new driver archive over the Mesa directory.
- - In the Mesa-3.0 directory type "make linux-glide"
+ - In the Mesa-3.1 directory type "make linux-glide"
- Compilation _should_ finish without errors;
- Set your LD_LIBRARY_PATH environment variable so that the
libglide2x.so and Mesa library files can be found. For example:
- setenv LD_LIBRARY_PATH "/usr/local/glide/lib:/SOMEDIR/Mesa-3.0/lib"
+ setenv LD_LIBRARY_PATH "/usr/local/glide/lib:/SOMEDIR/Mesa-3.1/lib"
- You'll have to run Glide-based programs as root or set the suid
bit on executables;
@@ -104,7 +104,7 @@ Linux:
./gears (hit ESC to exit)
- You can find the demos especially designed for the Voodoo driver in
- in the Mesa-3.0/3Dfx/demos directory (type "make" in order to compile
+ in the Mesa-3.1/3Dfx/demos directory (type "make" in order to compile
everything).
MacOS:
@@ -121,13 +121,13 @@ MS Windows:
- You must have the vcvars32.bat script in your PATH;
- - Go to the directory Mesa-3.0 and run the mesafx.bat;
+ - Go to the directory Mesa-3.1 and run the mesafx.bat;
- - The script will compile everything (Mesa-3.0/lib/OpenGL32.{lib,dll},
- Mesa-3.0/lib/GLU32.{lib,dll}, Mesa-3.0/lib/GLUT32.{lib,dll} and
+ - The script will compile everything (Mesa-3.1/lib/OpenGL32.{lib,dll},
+ Mesa-3.1/lib/GLU32.{lib,dll}, Mesa-3.1/lib/GLUT32.{lib,dll} and
Voodoo demos);
- - At the end, you will be in the Mesa-3.0/3Dfx/demos directory;
+ - At the end, you will be in the Mesa-3.1/3Dfx/demos directory;
- Try some demo (fire.exe, teapot.exe, etc.) in order to check if
everything is OK (you can use Alt-Tab or Ctrl-F9 to switch between
@@ -140,7 +140,7 @@ MS Windows:
to work with other kind of compilers;
- To discover how open the 3Dfx screen, read the sources under
- the Mesa-3.0/3Dfx/demos directory. You can use the GLUT library or
+ the Mesa-3.1/3Dfx/demos directory. You can use the GLUT library or
the Diego Picciani's wgl emulator.
NOTE: the MSVC++ 5.0 optimizer is really buggy. Also if you install the
@@ -389,7 +389,7 @@ Hints and Special Features:
- The Voodoo driver support multiple Voodoo Graphics boards in the
some PC. Using this feature, you can write applications that use
multiple monitors, videoprojectors or HMDs for the output. See
- Mesa-3.0/3Dfx/demos/tunnel2.c for an example of how setup one
+ Mesa-3.1/3Dfx/demos/tunnel2.c for an example of how setup one
context for each board.
- The v0.19 introduces a new powerful texture memory manager: the
@@ -407,13 +407,13 @@ Hints and Special Features:
- The Voodoo driver supports the GL_EXT_paletted_texture. it works
only with GL_COLOR_INDEX8_EXT, GL_RGBA palettes and the alpha value
is ignored because this is a limitation of the the current Glide
- version and of the Voodoo hardware. See Mesa-3.0/3Dfx/demos/paltex.c for
+ version and of the Voodoo hardware. See Mesa-3.1/3Dfx/demos/paltex.c for
a demo of this extension.
- The Voodoo driver directly supports 3Dfx Global Palette extension.
It was written for GLQuake and I think that it isn't a good idea
to use this extension for any other purpose (it is a trick). See
- Mesa-3.0/3Dfx/demos/glbpaltex.c for a demo of this extension.
+ Mesa-3.1/3Dfx/demos/glbpaltex.c for a demo of this extension.
- The Voodoo driver chooses the screen resolution according to the
requested window size. If you open a 640x480 window, you will get
@@ -484,12 +484,12 @@ version of GLQuake with works with the Mesa/3Dfx/Glide combo.
Here's what you need to run GLQuake on Linux:
PC with 100MHz Pentium or better
a 3Dfx-based card
- Mesa 3.0 libraries: libMesaGL.so libMesaGLU.so
+ Mesa 3.1 libraries: libMesaGL.so libMesaGLU.so
Glide 2.4 libraries: libglide2x.so libtexus.so
GLQuake for Linux.
Also, the windows version of GLQuake works fine with the Mesa OpenGL32.dll,
-you have only to copy the Mesa-3.0/lib/OpenGL32.dll in the GLQuake directory
+you have only to copy the Mesa-3.1/lib/OpenGL32.dll in the GLQuake directory
in order to test 'MesaQuake'.
@@ -584,7 +584,7 @@ the Mesa mailing list and my driver WEB page
(http://www-hmw.caribel.pisa.it/fxmesa/index.shtml)
-David Bucciarelli (tech.hmw@plus.it)
+David Bucciarelli (humanware@plus.it)
Humanware s.r.l.
Via XXIV Maggio 62