Quake

Run GLX quake2 with the +set _windowed_mouse 1 option. GLX Quake2 is running in a window,
even though it appears to take up your whole screen. If you move the mouse while the WM is in
Linux Quake HOWTO
When I try to run Quake II with the GL renderer, it fails and says "LoadLibrary("ref_gl.so") failed: Unable to resolve 39
focus−follows−mouse mode, you're likely to move the pointer outside this window, and then Quake II will
stop responding to mouse and keyboard input. +set _windowed_mouse 1 makes Quake II grab the
mouse exclusively.
Why can't I change to some of the SVGA modes that are in the Quake II
Video menu?
SVGAlib probably doesn't know how to create the modes on your card. When Quake II starts up with the
SVGA renderer (ref_soft.so), it prints a list of all the modes that SVGAlib tells it are available:
−−−−−−− Loading ref_soft.so −−−−−−−
Using RIVA 128 driver, 4096KB.
mode 320: 200 1075253220
mode 320: 240 1075253220
mode 320: 400 1075253220
mode 360: 480 1075253220
mode 640: 480 1075253220
mode 800: 600 1075253220
mode 1024: 768 1075253220
mode 1280: 1024 1075253220
These are the only modes you will be able to successfully switch to from the Video menu. If say, 512x384
isn't on the list, selecting it from the Video menu won't work.
SVGAlib does let you define new video modes for some chipsets in libvga.config, so you may be able
create your own video mode this way. See the SVGAlib documentation for more detail on this topic.

Quake

If the renderer in question is ref_gl.so, did you install the glide libraries? •
When I update the brightness while using the GL renderer, and hit
"apply," nothing happens!
Type vid_restart in the console to make the changes take affect.
Note about the 3.17 distribution
As of this writing, the most recent Quake II version is 3.20. If for some reason, you're running version 3.17
instead, the following information may be helpful to you.
Two text files (quake2.conf and fixperms.sh) in the 3.17 distribution were inadvertently saved in
MS−DOS CR/LF text−file format instead of the unix LF format. This means there's an extra carriage return
character at the end of each line in these files and they're not going to behave right until you fix them.
We'll run them through tr(1) to strip out the CR's.
for i in fixperms.sh quake2.conf
do
mv $i $i.bak
tr −d '\r' < $i.bak > $i
done
When I run Quake II with +set vid_ref glx fullscreen from X, I can't
use my mouse or keyboard.

Quake II
Linux Quake HOWTO
When I run Quake/QuakeWorld/Quake II under X, the image only takes up half the window and/or the colors 38
When I try to run Quake II with the GL renderer, it fails and says
"LoadLibrary("ref_gl.so") failed: Unable to resolve symbol"
If immediately prior to the "Unable to resolve symbol" line, you have messages like "can't resolve
symbol 'fxMesaCreateContext'", your Mesa library doesn't have glide support compiled in. See
section The GL renderer in the Quake II installation section for information on installing Mesa and glide.
Quake II fails with the message LoadLibrary("ref_XXX.so")
failed: No such file or directory
/etc/quake2.conf doesn't have the correct path to your Quake II directory in it. This file should
contain one line that is the directory Quake II lives in.
•
If /etc/quake2.conf does contain the correct path, try removing the file and re−creating it by
hand. Some versions of Quake II for Linux included an incorrectly formatted quake2.conf file.
•
Do you have SVGAlib installed? Check /lib, /usr/lib and /usr/local/lib for a file called
libvga.so.1.X.X, where the X's are some numbers. If nothing turns up, you need to get and
install SVGAlib to run Quake II outside of X.
•
If the renderer in question is ref_gl.so, Mesa may not be properly installed. Did you copy
libMesaGL.so.2.6 to a library directory like the installation instruactions told you to?

Quake/QuakeWorld

Quake dies at startup with a segmentation fault.
This usually means your network setup isn't right. Try starting quake with the −noudp option and see if the
error goes away. If that fixes it, check your /etc/hosts file and verify there's an entry for your machine in
it. Use 127.0.0.1 for your IP address if you have a dialup account that gives you a different address each time
you connect.
What's the difference between glqwcl, glqwcl.3dfxgl, and
glqwcl.glx?
glqwcl is the standard GL Quakeworld client you've seen in previous versions. It's linked against
libMesaGL.so.2.
•
glqwcl.3dfxgl is a script that runs glqwcl after preloading the 3Dfx GL miniport library,
lib3dfxgl.so. Preloading the minport library causes its GL functions to get used instead of
Mesa's. Since the GL minport is optimized for Quake, this is a good thing.
•
glqwcl.glx is linked against standard OpenGL libriaries instead of Mesa. This will allow glquake
to run on other 3D hardware that is supported by some other OpenGL implementation. This is an X
application and so must be run from X.
•
When I run glqwcl.glx fullscreen from X, I can't use my mouse or
keyboard.
Run glqwcl.glx with the +_windowed_mouse 1 option. GLX Quakeworld is running in a window,
even though it appears to take up your whole screen. If you move the mouse while the window manager is in
focus−follows−mouse mode, you're likely to move the pointer outside this window, and then Quake will stop
responding to mouse and keyboard input. +_windowed_mouse 1 makes Quakeworld grab the mouse
exclusively.