README.Linux 14 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353
  1. +----------------------------------------+
  2. | Q3Test |
  3. | The Official Quake 3: Arena TEST |
  4. | Linux version |
  5. | Revision 1.08 |
  6. | Released Aug 3, 1999 |
  7. | Copyright (C) 1999 id Software, inc. |
  8. +----------------------------------------+
  9. | Documentation: Paul Jaquays |
  10. | Dave Kirsch |
  11. +----------------------------------------+
  12. Outline:
  13. 1. Introduction
  14. 2. Bug Reporting
  15. 3. Installing Q3Test
  16. 4. Running Q3Test. Operating Instructions
  17. 5. Known Issues
  18. ==================
  19. == Section 1. ==
  20. == INTRODUCTION ==
  21. ==================
  22. This is the Linux version of the test.
  23. Before proceeding onward, please read the README.EULA file. This is
  24. the End User License Agreement. It's the agreement between you and id
  25. regarding this test. Read it. Understand that the acts of loading or
  26. running the software, or placing it on your computer hard drive, RAM,
  27. or other storage, you are agreeing to be bound by the terms of the End
  28. User License Agreement. So it's best to know what you are agreeing to.
  29. The operating instructions for the test are included in the
  30. separate "README.Q3Test" file. For the most part, the game functions
  31. are the same across all platforms. Differences will be noted when necessary.
  32. +----------------+
  33. | THIS IS A TEST |
  34. +----------------+
  35. We want to set the record straight from the outset. This is neither a
  36. demo nor an ALPHA version of the final game and should not be expected
  37. to behave as such. Q3Test is a test of Quake3: Arena's network technology
  38. and graphics compatibility. While many of the game features that you will
  39. see in this test are in a highly polished state, do not confuse this with
  40. being anything other than what it is intended to be: a test. By running
  41. this test openly on the Internet and on a multitude of local networks,
  42. we hope to expose problems that could not otherwise be discovered on the
  43. limited number of in-house systems and computer. That's why we need your
  44. assistance for this test.
  45. Furthermore, it is anticipated that there may be revisions and additions
  46. made to the test that will make it incompatible with earlier versions.
  47. +---------------------+
  48. | SYSTEM REQUIREMENTS |
  49. +---------------------+
  50. There is no software-only version of the game. If your computer is not
  51. hardware accelerated with a game compatible graphics card, you will NOT be
  52. able to run Q3Test. Currently, 3DFX based cards are the only
  53. tested compatible cards. If your computer does not meet the
  54. minimum requirements, you are unlikely to be able to run a satisfactory
  55. game experience.
  56. A glibc compatible Linux installation is required. An easy to determine
  57. if you have glibc support is to type this:
  58. ls -l /lib/libc*
  59. If you get a report of libc6 (you may also have libc5), you have a
  60. glibc based system.
  61. The Linux version requires a supported hardware 3D acceleration card. The
  62. following are currently supported:
  63. o 3Dfx Voodoo Graphics based cards
  64. o 3Dfx Voodoo2 based cards
  65. Other cards of similar make and model may work, but are not supported.
  66. Other X11 OpenGL libraries may work with a supported hardware
  67. accelerator, but have not been extensively tested. Performance on
  68. untested OpenGL configurations may not produce acceptable game
  69. speed.
  70. For 3Dfx based products, Linux Q3Test is distributed with a version of Mesa
  71. 3-D specifically compiled for Voodoo support. You must have 3Dfx Linux Glide
  72. drivers installed however. These drivers are available from:
  73. http://glide.xxedgexx.com/3DfxRPMS.html
  74. Make sure that you download and install the glibc versions of the drivers
  75. (found at the bottom of the page).
  76. Mirrors for this site are can be found at:
  77. http://glide.mirrors.sonic.net
  78. http://glide.samiam.org
  79. Please follow the installation instructions presented there for adding the
  80. correct drivers for your 3D-acceleration card. Note that there are two ways
  81. to install the 3DFX drivers-one with support for a /dev/3dfx device that
  82. does not require root permissions in order to use the card. If you choose to
  83. not use the /dev/3dfx method, you will have to run Q3Test as the root user.
  84. NOTE: Linux Q3Test will try to load "libGL.so" before using 3Dfx drivers.
  85. This can cause problems if you have a software or third party OpenGL driver
  86. installed. You can specifically target the included 3Dfx based Mesa driver
  87. by using the following command line:
  88. ./linuxquake3 +set r_glDriver libMesaVoodooGL.so.3.1
  89. For 3DFX users, you may disable the vertical sync refresh. This can improve
  90. proformance at the cost of some visual tearing of the image. Entering the
  91. following command into your shell before running Q3Test will turn off
  92. the vertical sync:
  93. export FX_GLIDE_SWAPINTERVAL=0
  94. Then run Linux Q3Test from the same command line normally.
  95. +-----------+
  96. | X11 Setup |
  97. +-----------+
  98. Linux Q3Test requires X11 to run. There is no console-based version as in
  99. previous id products such as GLQuake and Quake2. XFree86 version 3.2 or
  100. later is required.
  101. There are two ways that mouse input is handled under XFree86:
  102. o By default, Q3Test will attempt to use DGA mouse handling. DGA
  103. support features direct reading of the mouse motion and provides
  104. more accurate control while playing the game. By default this
  105. support is enabled, but can be disabled by adding "+set
  106. in_dgamouse 0" to the command line at startup.
  107. o The non-DGA method of mouse input uses pointer grabbing and warps
  108. the pointer to the middle of the window on each mouse update. On
  109. systems with a slow frame rate and a lot of mouse user input, the
  110. motion can get "clipped" to the window boundaries. This method of
  111. input is more compatible however.
  112. Q3Test uses the XFree86 VidModeExtension facilities if available to provide
  113. fullscreen play. This does not apply to 3Dfx passthrough based cards, since
  114. the passthrough cable takes over the video display upon activation anyway.
  115. When configuring your X11 server, make sure that you include lower
  116. resolution modes such as 640x480 and 800x600. Q3Test will auto-switch to
  117. these modes using the VidModeExtension if you select fullscreen from the
  118. graphics options menu. If the lower resolution modes are not listed in the
  119. XFree86 configuration file, Q3Test will be unable to switch to the desired
  120. resolution for fullscreen play.
  121. +-------------------------+
  122. | Sound Support and Setup |
  123. +-------------------------+
  124. Q3Test uses the /dev/dsp sound device for sound support under Linux. This is
  125. the default device provided by the sound drivers included with the Linux
  126. kernel. Please note that at the time of this writing, PCI based sound cards
  127. such as the SoundBlaster Live and Diamond Monster MX series were not
  128. supported. They may be supported in the future. Check
  129. http://www.opensound.com/ for support in the future.
  130. If you do not run Q3Test as root (recommended), you may need to make sure
  131. the permissions for the /dev/dsp device are read and write by the user
  132. running Q3Test. The cheap and easy way to make this happen is to do "chmod
  133. o+rw /dev/dsp" as root. For the more security conscious, a special sound
  134. group could be created and Q3Test could be made setgid to the sound group to
  135. access the device.
  136. Q3Test uses mmap() to map the sound buffers on /dev/dsp directly in order to
  137. provide responsive sound needs. Sound cards must be able to support this
  138. feature in order to work. SoundBlaster 16, AWE32 and AWE64 cards are known
  139. to work.
  140. +----------------------+
  141. | WHAT'S IN THIS TEST? |
  142. +----------------------+
  143. We have included three maps with this test version of Quake3: Arena. They
  144. are q3test1, q3test2, and q3tourney.
  145. q3test1 for 4-8 players on Internet or LAN play Best with 6 players
  146. q3test2 for 3-8 players Primarily for LAN play Best with 3 players
  147. q3tourney is the tournament map
  148. ===================
  149. == Section 2. ==
  150. == BUG REPORTING ==
  151. ===================
  152. What we would like from our testers are emails with descriptions of
  153. problems that are encountered, particularly those involving video or
  154. network bugs. Do NOT send reports to individual id employees. All bug
  155. reports should go to the following e-mail address:
  156. q3feedback@idsoftware.com
  157. In your subject line, please describe the system the game is being played
  158. on (Mac, Linux, Win32) and the type of problem you are reporting: video,
  159. network, sound or game. Example Subject Line: "Mac/video problem" or
  160. "Linux/network connection problem."
  161. In the body of your letter (no attached files please), briefly list and
  162. describe the problems. Detailed descriptions of problems are good, but
  163. remember that brevity is best. Please do NOT send screen shots unless
  164. they are the ONLY way to show a problem.
  165. While we realize that you may have comments and suggestions regarding
  166. specific game play features, please refrain from submitting such along
  167. with bug reports. Comments on game play can be made on the official
  168. Quake 3: Arena message board at:
  169. http://www.quake3arena.com
  170. ========================
  171. == Section 3. ==
  172. == INSTALLING Q3TEST ==
  173. ========================
  174. After you have installed the needed hardware drivers for your 3D
  175. acceleration and sound hardware, you need to install the Q3Test package.
  176. Q3Test is available as a Red Hat RPM file or as a tar file. To install the
  177. RPM file, enter the following when logged in as the root user:
  178. rpm -Uvh q3test-1.00-glibc-1.i386.rpm
  179. The rpm installs the game and data files in /usr/local/games/q3test.
  180. [ Note: If you have not installed (or do not wish to install) the Linux
  181. glide drivers, you may get an error message about not having libglide2x.so
  182. installed. This can be ignored and installation can be forced by adding
  183. the --nodeps option to the rpm command line as follows:
  184. rpm --nodeps -Uvh q3test-1.00-glibc-1.i386.rpm ]
  185. If you are going to install the tar version, make a directory for
  186. installation, untar the file as follows:
  187. tar xzvf q3test-1.00-glibc-i386.tar.gz
  188. This will untar the files into a q3test subdirectory under the current
  189. directory.
  190. ====================
  191. == Section 4. ==
  192. == RUNNING Q3TEST ==
  193. ====================
  194. It is recommended that you do not run Q3Test using the root account or with
  195. root privileges. There are two exceptions to this:
  196. o If you are using a 3Dfx based accelerator card and do not install
  197. the /dev/3dfx configuration option. (You will have to run as root
  198. in order to access the card).
  199. o If you do not have access to the /dev/dsp device and do not wish
  200. to change the mode of the device so that non-root accounts can
  201. access it.
  202. You will have to be running under X11 or have the DISPLAY variable pointed
  203. to a OpenGL glX capable X Server.
  204. By default, Q3Test tries to find the following OpenGL libraries in this
  205. order:
  206. o libGL.so.1
  207. o libMesaVoodooGL.so.3.1
  208. You can override the library name by entering, "+set r_glDriver <libname>"
  209. on the command line. This may be needed if you are using a non-standard set
  210. up and have a different name for the OpenGL shared library.
  211. If everything proceeds successfully, you should have a Q3Test window on your
  212. desktop with a menu displayed (3DFX owners will get a full screen view). If
  213. you want to use full screen, go to the System Configuration, Graphics
  214. Options, Fullscreen, change the value to Yes, and hit enter to apply it.
  215. If you intend to connect to the Internet to play Q3Test, make certain
  216. that your net connection is open and working first.
  217. ======================
  218. == Section 5. ==
  219. == KNOWN ISSUES ==
  220. ======================
  221. Q. My mouse is erratic. My player is constantly looking up or down and
  222. I can't seem to move him.
  223. A. This happens with two issues. Some versions of XFree86 have a bug in
  224. DGA mouse handling that confuses Q3Test. You can try turning off DGA mouse
  225. support by entering "+set in_dgamouse 0" on the command line when you
  226. start Q3Test. This problem can also occur after a restart of the video
  227. system (such as after a graphic setting change). This is because some
  228. sort of event occurred to jam up the mouse. Restarting the video system
  229. another time and not moving the mouse during the restart should clear it.
  230. Q. When I do a video restart (for example, selecting Apply in the Graphics
  231. Options menu), Q3Test exits with a Sig11.
  232. A. This is a driver related problem.
  233. On 3DFX hardware that is using the /dev/3dfx device and you are NOT running
  234. as root, it seems that the restart doesn't clear some sort of permission.
  235. Running Q3Test as root will fix this problem.
  236. Q. Performance is so slow I can't play! The frame rate looks like one
  237. frame per second!
  238. A. Most of the current drivers for Linux do not support hardware
  239. acceleration at any bit depth other than 15 or 16 bit color. Make sure
  240. that you specify 16 bit color when you run your X11 Server, such as:
  241. startx -- -bpp 16
  242. Q. I have a Voodoo3. When I start the game, I send up at a low resolution
  243. version of my desktop.
  244. A. The current Voodoo3 X11 Servers have problems with DGA Mouse support.
  245. This is a known driver issue and will be fixed in newer revisions of the
  246. Voodoo3 X11 Server. Run the game with the following to disable it:
  247. ./linuxquake3 +set in_dgamouse 0
  248. Q. I'm running Gnome with Englightenment and sound doesn't work.
  249. A. If you are using the Enlightenment Sound Daemon (esd), it will not release
  250. the sound hardware for Quake3 Test's usage. You can disable it before running
  251. the test as follows:
  252. esdctl off # turn it off
  253. start q3test the normal way
  254. esdctl on # turn it back on
  255. Q. I try to run Q3Test, but sound doesn't work. The console says "Can't
  256. open /dev/dsp. /dev/dsp: Can't allocate memory."
  257. A. This can happen if the vmware kernel modules are loaded. You can unload
  258. them by typing when logged as root:
  259. /etc/rc.d/init.d/vmware stop
  260. Assuming you are using a RedHat system.
  261. Q. I was playing Q3Test and suddenly it quit and reported a signal error.
  262. A. This is probably a bug. Please report it.