readme.glquake 6.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163
  1. Linux Glquake v0.98, Quake v1.09 release notes
  2. Requirements
  3. ------------
  4. For 3DFX based hardware, you must download and install Linux GLIDE from
  5. http://glide.xxedgexx.com/3DfxRPMS.html and install as per the
  6. instructions.
  7. Running GLQuake
  8. ---------------
  9. There are three different ways to execute GLQuake:
  10. 1. The binary "glquake" requires Mesa 3-D 2.5 or later installed and compiled
  11. with 3DFX support (fxMesa..() function interface). It also requires
  12. svgalib 1.3.0 or later for keyboard/mouse input. This binary is a console
  13. application. Mesa 3-D requires GLIDE to be installed.
  14. 2. The shell script "glquake.3dfxgl" runs the "glquake" binary after
  15. preloading the lib3dfxgl.so library. This is a port of 3DFX's Win32
  16. OpenGL MCD (Mini Client Driver) to Linux. It is faster than Mesa 3-D
  17. since it was written specifically with supporting GLQuake in mind.
  18. lib3dfxgl.so requires that GLIDE be installed.
  19. 3. The binary "glquake.glx" is linked against standard OpenGL libraries.
  20. It should run on many different hardward OpenGL implementations under
  21. Linux and X11. This binary is an X11 application and must be run under
  22. X11. It will work with Mesa 3-D as a standard glX based OpenGL
  23. applications. If the Mesa 3-D library is compiled with 3DFX support,
  24. you can have Mesa 3-D support 3DFX hardware under X11 by setting the
  25. enviroment variable "MESA_GLX_FX" to "fullscreen" for fullscreen mode
  26. and "window" for windowed mode.
  27. You must also have SVGALib 1.3.0 or later installed. GLQuake uses SVGALib
  28. for mouse and keyboard handling.
  29. If you have gpm and/or selection running, you will have to terminate them
  30. before running GLQuake since they will not give up the mouse when GLQuake
  31. attempts to run. You can kill gpm by typing 'killall gpm' as root.
  32. You must run GLQuake as root or setuid root since it needs to access things
  33. such as sound, keyboard, mouse and the 3DFX video. Future versions may not
  34. require root permissions.
  35. resolution options
  36. ------------------
  37. glquake -width 512 -height 384
  38. Tries to run glquake at the specified resolution.
  39. Only highend VooDoo cards support such high resolutions (most
  40. cards on the market right now do not). Another popular and supported mode
  41. is 512x384 (-width 512 -height 384) which can offer a faster speed than
  42. the default 640x480.
  43. You can also specify the resolution of the console independant of the screen
  44. resolution.
  45. glquake -conwidth 320
  46. This will specify a console resolution of 320 by 240 (the height is
  47. automatically determined by the default 4:3 aspect ratio, you can also
  48. specify the height directly with -conheight).
  49. In higher resolution modes such as 800x600 and 1024x768, glquake will default
  50. to a 640x480 console, since the font becomes small enough at higher
  51. resolutions to become unreadable. If do you wish to have a higher resolution
  52. console and status bar, specify it as well, such as:
  53. glquake -width 800 -height 600 -conwidth 800
  54. texture options
  55. ---------------
  56. The amount of textures used in the game can have a large impact on performance.
  57. There are several options that let you trade off visual quality for better
  58. performance.
  59. There is no way to flush already loaded textures, so it is best to change
  60. these options on the command line, or they will only take effect on some of
  61. the textures when you change levels.
  62. OpenGL only allows textures to repeat on power of two boundaries (32, 64,
  63. 128, etc), but software quake had a number of textures that repeated at 24
  64. or 96 pixel boundaries. These need to be either stretched out to the next
  65. higher size, or shrunk down to the next lower. By default, they are filtered
  66. down to the smaller size, but you can cause it to use the larger size if you
  67. really want by using:
  68. glquake +gl_round_down 0
  69. This will generally run well on a normal 4 MB 3dfx card, but for other cards
  70. that have either worse texture management or slower texture swapping speeds,
  71. there are some additional settings that can drastically lower the amount of
  72. textures to be managed.
  73. glquake +gl_picmip 1
  74. This causes all textures to have one half the dimensions they otherwise would.
  75. This makes them blurry, but very small. You can set this to 2 to make the
  76. textures one quarter the resolution on each axis for REALLY blurry textures.
  77. glquake +gl_playermip 1
  78. This is similar to picmip, but is only used for other players in deathmatch.
  79. Each player in a deathmatch requires an individual skin texture, so this can
  80. be a serious problem for texture management. It wouldn't be unreasonable to
  81. set this to 2 or even 3 if you are playing competatively (and don't care if
  82. the other guys have smudged skins). If you change this during the game, it
  83. will take effect as soon as a player changes their skin colors.
  84. run time options
  85. ----------------
  86. At the console, you can set these values to effect drawing.
  87. gl_texturemode GL_NEAREST
  88. Sets texture mapping to point sampled, which may be faster on some GL systems
  89. (not on 3dfx).
  90. gl_texturemode GL_LINEAR_MIPMAP
  91. This is the default texture mode.
  92. gl_texturemode GL_LINEAR_MIPMAP_LINEAR
  93. This is the highest quality texture mapping (trilinear), but only very high
  94. end hardware (intergraph intense 3D / realizm) supports it. Not that big of
  95. a deal, actually.
  96. gl_finish 0
  97. This causes the game to not issue a glFinish() call each frame, which may make
  98. some hardware run faster. If this is cleared, the 3dfx will back up a number
  99. of frames and not be very playable.
  100. gl_flashblend 0
  101. By default, glquake just draws a shaded ball around objects that are emiting
  102. light. Clearing this variable will cause it to properly relight the world
  103. like normal quake, but it can be a significant speed hit on some systems.
  104. gl_ztrick 0
  105. Glquake uses a buffering method that avoids clearing the Z buffer, but some
  106. hardware platforms don't like it. If the status bar and console are flashing
  107. every other frame, clear this variable.
  108. gl_keeptjunctions 0
  109. If you clear this, glquake will remove colinear vertexes when it reloads the
  110. level. This can give a few percent speedup, but it can leave a couple stray
  111. blinking pixels on the screen.
  112. novelty features
  113. ----------------
  114. These are some rendering tricks that were easy to do in glquake. They aren't
  115. very robust, but they are pretty cool to look at.
  116. r_shadows 1
  117. This causes every object to cast a shadow.
  118. r_wateralpha 0.7
  119. This sets the opacity of water textures, so you can see through it in properly
  120. processed maps. 0.3 is very faint, almost like fog. 1 is completely solid
  121. (the default). Unfortunately, the standard quake maps don't contain any
  122. visibility information for seeing past water surfaces, so you can't just play
  123. quake with this turned on. If you just want to see what it looks like, you
  124. can set "r_novis 1", but that will make things go very slow. When I get a
  125. chance, I will probably release some maps that have been processed properly
  126. for this.
  127. r_mirroralpha 0.3
  128. This changes one particular texture (the stained glass texture in the EASY
  129. start hall) into a mirror. The value is the opacity of the mirror surface.