For GL Quake and Quake World

Go to "edit" then "find" (Ctrl+F) to enter key words for search.

1. DirectX from the CD-ROM that came with your 3DFX Voodoo video card or go to your video card manufacturer driver webpage and get the latest DirectX that they recommend. (If your 3DFX Voodoo drivers include DirectX then skip to #2) Win98 users don't need to install Direct X as Win98 installs it during the installation of the Win98 operating system

2. Latest Video Card drivers from your video card manufacturer.

GL Quake Version .97 "glq1114.exe" (or latest)

These new versions have self installers. Just double click on the GLQ1114.EXE or QW221 .EXE file after download and follow the instructions. Make sure and check the box to install the opengl32.dll for 3DFX during the install if you are using a 3D-video card from 3DFX.

SETTING THE COLOR PALETTE:

Before attempting to run GL Quake/QW, you must set your color palette to: "16bit". To set: Go to "control panel", then "display", then the "settings" tab. Change the color palette to "16bit", hit "apply", then "OK" and restart.

• Failure to do this will give the error: "no RGB fullscreen modes available"
• DO NOT select "16 color". "High Color 16 bit" is the correct one.
• Setting this to "24 bit" MAY give an error "video mode not available" when starting GL Quake.

Note: Pure3D users adjust the screenrefresh, Gamma (brightness) and Clock Mhz speed from your Pure3D control panel/display tab.

Note: In the batch file adjust "-heapsize" to your available RAM.

-heapsize 24000 : (24mb) this sets the alloted MB of RAM used by GL Quake. "-heapsize 16000" would be 16mb. (same command as "-winmem" in regular quake) Don't exceed 50% of your ram. 32mb heapsize should be plenty if you have 64mb or more.

• Remove "-nojoy" from the batch file if you use a joystick.
• Remove "-nocdaudio" from the batch file if you listen to music while playing. (not recommended if you like to win, hehehe!)
• For GLQW. Change "glquake.exe" to "glqwcl.exe" and remove the "-game ctf".

You can make a short cut on your desktop by right clicking on the GlqV1.bat file and select "create shortcut". Then drag the shortcut to your desktop.

Note: voodoo II users change gl_playermip to "1" in the included autoexec.cfg

You can make a short cut on your desktop by right clicking on the GlqV1.bat file and select "create shortcut". Then drag the shortcut to your desktop.

Note: In the batch file adjust "-heapsize" to your available RAM.

-heapsize 24000 : (24mb) this sets the allotted MB of RAM used by GL Quake. "-heapsize 16000" would be 16mb. (same command as "-winmem" in regular quake) Don't exceed 50% of your ram. 32mb heapsize should be plenty if you have 64mb or more.

• *Remove "-nojoy" from the batch file if you use a joystick.
• *Remove "-nocdaudio" from the batch file if you listen to music while playing. (not recommended if you like to win, hehehe!)
• *For GLQW. Change "glquake.exe" to "glqwcl.exe" and remove the "-game ctf".

Anything you put in your GL Quake/QW batch file (GlqV1.bat or GlqV2.bat) or autoexec.bat starting with the "SET " statement is a variable. There's only a finite amount of space available for these variables in DOS called Environment Space. You can make this space larger by adding this line to your C:\CONFIG.SYS file:

shell=c:\command.com /e:512 /p

Open the "config.sys" file (its on your C drive) with your notepad to add the line, after adding the line, click "file" and "save". Then restart the computer for the new setting to take effect. If you need more space in the future, increase the number from 512 to 1024

*If you have a shortcut to the "GlqV1.bat" or "GlqV2.bat" file, then delete it prior to performing the below steps. Then create your shortcut again after you finish. It will not create the MSDOS .pif file in the Quake folder if you have a short cut to the batch file at the time you perform the below steps.

2. Select "program" tab.

3. In the space next to "run", select "minimized".

4. Put a check next to "close on exit".

5. Hit "apply" then "OK"

2. Select "program" tab.

3. Hit the "advanced button" and uncheck all the boxes then hit "OK" all the way out.

1. Before starting QW for the first time, make a folder named "qw" in your quake directory. The directory path should be "quake/qw". GL Quake World will create an inverse palette and mesh all your MDL files the first time you run the game. If you have a problem with GLQW trying to create an inverse palette every time you start GLQW. Do This: delete all sub folders in all Quake subdirectories named "glquake". Then install regular GL Quake (not GLQW) and start the game and let it mesh the files. Then GLQW should run fine.

2. Don't use a game switch (-game ctf). QW Servers know where to find the map files. The pak files must be in the proper folder. CTF3 & 4 and Thunder Walker must be in the quake/ctf folder. Rocket Arena goes in the quake/arena folder.

3. Go here and download the QW skin pack file name qws_9729.zip (or latest)

Then unzip the file into the "quake/qw/skins" folder. This will save you time on skin download when you sign onto a server.

If you use Gamespy. After installing the GLqV1.bat or GLQV2.bat, put the name of the batch file in the Gamespy command line box. Go here to download the latest version of Gamespy. Quake World Version 2.10 comes with an old version 1.01 of GameSpy. Gamespy has updated it's version several times since the last Quake World was released.

This will display your FPS in real time in lower right corner as you play the game. Only works on QW version 2.10

One of QuakeWorld's key features are the provisions it has for dealing with reducing the effects of "lag" over the Internet. They are rate and pushlatency .

*Can be set in GameSpy options.

On QW version 2.10 "rate" is a dual function command. It controls the bytes per second recieved on your net connection and also the cap on your FPS (frames per second).

"Rate 2500" (default) caps framerate at no higher than 30FPS.

"Rate 6000" caps framerate at no higher than 72FPS .

The cap on FPS is infinitely adjustable between 30FPS and 72FPS using the "rate" command. The FPS cap on the Old QW Ver 2.0 was set at 30FPS regardless of the "rate" setting.

Use the following approximate "rate" settings:

*26.4- rate 2300

*28.8- rate 2500 (default)

*33.6- rate 3000

ISDN/CABLE MODEM/T1- rate 3000-6000

*this is your connection speed and not your modem capabilities.

If you wish to override the framerate cap that the "rate" command issues, then you can separately use the cl_maxfps command. Let's say you wanted to set your "rate" to 2500, which would normally cap your framerate at 30fps, but you want a 40fps cap. Just add cl_maxfps 40 to your autoexec.cfg. Framerate cap is adjustable from 30-72 fps using cl_maxfps.

This displays a graph of your net connection. Very helpful in adjusting your "rate" setting.

The height of the white lines towards the bottom is your latency on received packets. Red lines are lost packets. (bad) Yellow lines are from the rate command kicking in, it's data that wasn't sent to you because you didn't have the bandwidth for it. Blue lines are very bad, they are invalid delta's. They mean your ISP is overloaded or has configuration problems and are related to the U_REMOVE warnings. If you can't get rid of the blue lines by lowering your "rate". It means your ISP sucks. Find a better ISP.

By typing "r_netgraph 1" at the console, you will be presented with a thin bar graph that occupies the lower quarter of the Quake view port. A series of colored bars will immediately begin scrolling by. The white bars represent delivered packets, yellow bars represent deliberately dropped packets, red bars represent packets dropped by the net, and blue bars indicate that the client has received a bad delta compression offset (this is a bad thing). The goal is to reduce the number of red and yellow bars to a point where the data stream between your PC and the QuakeWorld server is as steady and uniform as possible.

Leaving the display up, play on the server for a while. Get into some firefights, and keep an eye on the graph. If you start to see a lot of red bars, bring down the Quake console, and set the rate command to a lower value. For example, if you're getting a lot of red bars on your 28.8 connection to your favorite server, you may want to try "rate 2400". Conversely, if you're receiving a steady stream and want to try and increase the rate setting, you can do that as well. Be aware that while you want to get rid of red lines if you can, it isn't always best to get rid of all the yellow lines. Setting the rate high enough to avoid any yellow lines may cause the operating system or modem to buffer up data, actually increasing your ping time. If you see any blue bars, you may want to consider getting a new ISP.

The downside of the "rate" command is that by lowering it you won't receive updates as often as a machine capable of a higher rate, meaning that, once again, your client will rely on simulation to smooth out the game. The good news is a well tweaked rate and pushlatency setting can effectively make playing Quake on a modem seem more like a very good ISDN line!

When you have adjusted the rate to your liking, you can remove the netgraph from the display by typing "r_netgraph 0" at the Quake console.

I have the below alias in a config.cfg as a 1 button toggle to turn on and off the r_netgraph function:

bind "x" "net1"

alias net1 "r_netgraph 1;echo Graph ON...;wait;bind x net2"

alias net2 "r_netgraph 0;echo Graph OFF...;wait;bind x net1"

Default -50

Pushlatency determines the amount of prediction that your client will use. Simply stated, your QuakeWorld client will make educated guesses as to condition changes in the gaming world in the moments it loses contact with the server between game packets. The result of this is smoother gameplay on the client end.

Pushlatency preferences vary from user to user, but in general, you want to try it in a range from 0 to -100 before trying anything larger. Always use a negative (-) value. The default is "-50". Some players have had favorable results with setting the pushlatency to the negative of their average ping. To do this, press the "tab" key while connected to a server, and watch your ping. Make a judgment as to it's average value, then press the " ~ " key to bring down the Quake console and set pushlatency to the negative of that value. For instance, if your average ping to a server is 240ms, set pushlatency to -240 by typing "pushlatency -240" at the Quake console.

Pushlatency is not without its downsides. The higher you set pushlatency, the more likely it is for a prediction error to occur. For example, you may think that you are shooting at a target, but if your client makes a bad guess at to the action of the opposing player and makes an incorrect prediction of his movement, he may not be there when your rocket is. The best thing to do is to tweak pushlatency to suit your style. In most cases a value of up to "-100" will not have substantial prediction errors.

I have the below alias in a config to adjust pushlatency on the fly. Just hit the "F6" key to cycle thru all the pushlatency values. It will display the new value each time you hit the "F6" key. Change the values to suit your connection.

bind F6 "push1"

alias push1 "pushlatency -125;echo pushlatency -125;bind F6 push2"

alias push2 "pushlatency -150;echo pushlatency -150;bind F6 push3"

alias push3 "pushlatency -175;echo pushlatency -175;bind F6 push4"

alias push4 "pushlatency -200;echo pushlatency -200;bind F6 push5"

alias push5 "pushlatency -225;echo pushlatency -225;bind F6 push6"

alias push6 "pushlatency -250;echo pushlatency -250;bind F6 push7"

alias push7 "pushlatency -275;echo pushlatency -275;bind F6 push8"

alias push8 "pushlatency -300;echo pushlatency -300;bind F6 push1"

DEFAULT: cl_nodelta 0

Toggles delta compression on and off, related to the U_REMOVE warning.

0 - Allows delta compression to take place (preferred).

1 - Does not allow delta compression to take place (eliminates U_REMOVE warnings).

Can be set in gameSpy. If you have to use the cl_nodelta 1 to get rid of the "U_Remove On Update" error messages. Your ISP sucks. Get a better ISP.

If during your play, you frequently see a string of messages with the term "U_REMOVE" in them, and your play seems to freeze for several seconds, use the console command cl_nodelta 1. This is a slightly less efficient way for QuakeWorld to work, but if your ISP is overloaded or has some configuration problems, it may not pass packets to QuakeWorld properly and cause difficulty. The easiest way to get rid of this error and improve your gameplay is to find a better ISP. This error can also be caused by setting your "Rate" too high, giving too high a FPS for your available bandwidth. Remember, each frame sends a packet of information. Higher FPS= More Packets Sent. Lower your "rate" to lower your FPS.

Regular netquake players know that teams were set by pants color. It is different in QuakeWorld however, a new console command "team" exists. You may set this to any value up to 4 characters, note that it is case sensitive. This is not for team color in CTF. You type a team name. Everyone who has their team set to "none" will be on the same team, regardless of pants color or anything else. If you want to join the "blue" team, just bring up the console, and type "team blue". If you wish to not be on a team at all type team "". This feature is useful for DM. Whereas 2 players may type the name "team nuke" or whatever and they can't kill each other if the DM server has Teamplay turned on.

DEFAULT: 0

Toggles prediction of your movement.

0 - Enables prediction of your movement

1 - Disables prediction of your movement.

Always enable prediction. It will be enabled by default.

DEFAULT: cl_predict_players 1

Toggles prediction of other players in the game.

0 - Disables prediction of other players.

1 - Enables prediction of other players.

DEFAULT: cl_sbar 0

Toggles the style of the status display.

0 - New HUD style display.

1 - Old style weapon status bar.

*using the old style weapon bar can give about a 10% FPS boost in FPS as it displays less game image screen area.

Swaps QW Weapon Tool Bar from left to right. 0/1. You must also use cl_sbar 0 (new hud display).

DEFAULT: noaim 0

Toggles autoaiming help.

0 - Enables any autoaiming.

1 - Disables any autoaiming.

Can be set in GameSpy. I have the below alias in a config to toggle autoaim on and off. If the server has autoaim set to the maximum aim correction, it can be quite annoying sometimes.

bind "HOME" "aim5"

alias aim5 "noaim 1;echo AUTO AIM OFF...;wait;bind HOME aim6"

alias aim6 "noaim 0;echo AUTO AIM ON...;wait;bind HOME aim5"

0 is no crosshair.

1 is old style crosshair.

2 is new Red LED crosshair. (latest version QW only)

DEFAULT: msg 1

Limits what game messages the server will send to you. " 0 " prints everything, and "4 " showing no messages. Reducing server messages can reduce bandwith requirements a small amount, and reduce clutter in busy games. "1" , "2" & '3" are degrees in between.

DEFAULT: noskins 0

Toggles download and displaying skins while playing.

0 - Enables the downloading and viewing of the non-default Quake Skin.

1 - Disables the downloading and viewing of the non-default Quake Skin.

2 - Disables the downloading of skins you don't have, but will display any skins you do have.

Can be set in GameSpy.

DEFAULT: <none>

Sets what skin your player wears. Get the skin file name from the quake/qw/skins folder.

Can be set in GameSpy.

DEFAULT: base skin

Default skin that other players not using a skin will be viewed as. Get the skin file name from the quake/qw/skins folder.

This command will update/download the skins being worn by other players in the game.

Toggles spectator mode, must reconnect for option to take effect.

1- Spectator mode is enabled. Then connect to a server.

0 - Spectator mode is disabled.

GameSpy offers the spectator mode for connection to a server. If you are on a server and want to become a spectator. Type at the console: spectator 1 <enter> then type: reconnect <enter>

(Example: record mydemo underworld.idsoftware.com or I.P.)

Records a client side demo, the first parameter is the file name to save the demo under, the second is the server to connect to.

Can be directed from GameSpy.

Reconnects to the server you were last on, and starts recording a new demo.

Stops the recording of the demo currently being recorded.

Connects to the last server you played on.

Disconnects from the current server.

DEFAULT: 0

Sets your shirt color (0-15).

DEFAULT:0

Sets your pants color (0-15)

Sets which highest weapon that it will change to when picking up a weapon. Use weapon impulse #.

Can be set in gameSpy.

Sets which highest weapon it will change to when picking up a backpack. Use weapon impulse #.

Can be set in GameSpy.

2 is shotgun.

3 is double barrel shotgun.

4 is double nail gun.

5 is super nail gun.

6 is grenade launcher.

7 is rocket launcher.

8 is lighting shaft.

If you are unsure about what GameSpy settings to add in the frontend.cfg. Just make all your settings in GameSpy as normal, then start the game with Gamespy and then close it. Then open the frontend.cfg and use the settings in it. Then just add all your other binds, aliases etc. to the frontend.cfg file, leaving the settings that GameSpy placed in it. To make the frontend.cfg a "read only" file. Just right click on the frontend.cfg file and choose properties. Then put a check mark besides "read only". Hit "apply" then "OK". Now it will load all the settings in the frontend.cfg just like an autoexec.cfg when you start Quake World WITH GameSpy. If you don't start the game with GameSpy it won't load the frontend.cfg settings. Then you would have to type at the console after starting the game: exec frontend.cfg

---------------------------------------------------------------------------------------------------------------------------

Makes water, lava and slime surfaces translucent, so you CAN see what's underneath. With normal maps, the vis info isn't there, so you have to turn on "r_novis 1" to actually see through unless you vis'ed your maps. (0.3 looks like fog!)

If you vis your maps with the above utility, it will cost you about 15% in FPS on the timedemo2 test. The timedemo2 is just a test. It the real world it won't matter that much.

Note: Even though you can see thru the surface of the water, you will not be able to see players, ammo, armor, packs etc., as the server does not transmit that info to you. Because the server doesn't think you can see it. Just a few servers are currently running with the information beings sent to the player so you can see the players below the surface when your above the surface. The server must be running vised maps also for you to see the players, ammo, armor, weapons, packs etc. thru the water surface. However in Monster play all the info is send to you.

Note: It will run amazingly slow with the "r_novis 1" command (1/2 speed or less). This is just a workaround so you can see the effect. To actually run a map with transparent water, you need a map which has been VIS'd with the new VIS utility.

DO NOT LET IT MAKE backup copies. If you let it make backup copies, it will leave your orignal Pak files unaltered and make new pak files that have been vised. If you let it make backups, you will need to remove the Pak files and rename the new vised ones. Pak files must start with "0" (zero) and go up from there. (0,1,2,3 etc.) After saying "y" to overwriting your maps, it will ask your Quake directory. It will then detect all the pak files that you have vis patch files for in the "water" folder, and ask the directory of the "ID1, CTF3, etc." Just follow the on screen instructions. Its very easy. The whole vis process only take 5 minutes or less.

*Then use the "r_wateralpha 0-1" (in .1 increments) to adjust the transparency of the water surface. I like ".3"

----------------------------------------------------------------------------------------------------------------------------------

The new versions of GL Quake .97 and QW 2.21 allow you the option of which resolution size of tool bar and messages you want. So if you are running GL Quake at 640x480 and want the same size tool bar and message font as the old 320x200 Quake (big tool bar and message font). Using the 320x200 tool bar with 640x480 video resolution will add 3-6 FPS as it displays less game image screen area. Add this to your command line:

-conwidth 320 -conheight 200

I prefer: -conwidth 512 -conheight 384 (while using 640x480)

*512 size console will give a 2-3 FPS Boost in the 640x480 video mode.

Here is an example of the command line:

The height is automatically determined by the default 4:3 aspect ratio. You can also specify the height directly with "-conheight" as I did in the example above. But if all you placed in the command line was "-conwidth 320", It would by default use a "conheight" of "200".

In higher resolution modes such as 800x600 and 1024x768, glquake will default to a 640x480 console, since the font becomes small enough at higher resolutions to become unreadable. If you wish to have a higher resolution console and status bar, specify it as well, such as: glquake.exe -width 800 -height 600 -conwidth 800

1 turns on dynamic shadows. Weapons, powerups, projectiles and armor have shadows. Firing the lighting gun, gives a very annoying shadow effect. It appears that your screen is tearing badly. Turning on the "r_shadows 1" will cost you 1.5 FPS.

This command shows the lightmap without the textures, with textures just on the entities. Everything looks like white sheetrock. It's cool! Kinda like a Miami Vice drug dealers house. Can be used in Net Play.

This command removes all the shadows and dark corners in a map. If you want to see your timedemo2 test blaze at twice the speed or your scared of the dark, enable this setting. Servers won't allow this setting on Net Play as no one could hide from you.

Setting "0": This replaces the dynamic colored ball with the old dynamic light. This setting will cost you a few FPS, especially on slower systems.

Setting "1": Makes an annoying flash ball around explosions etc. ("1" gave me an increase of 1.7fps on timedemo2)

bind "INS" "plf4"

alias plf4 "gl_flashblend 1;echo FLASH BALL ON...;wait;bind INS plf3"

alias plf3 "gl_flashblend 0;echo FLASH BALL OFF...;wait;bind INS plf4"

"0 " turns off palette shifting.. This means your screen color doesn't change underwater or when you have quad, ring or take damage etc..(water will be crystal clear when your in it.) Setting of "0" gives a few extra FPS. Set it to '1" and everything looks normal. (water will be cloudy when your in it, and your screen will change color when your being shot, get quad, ring and pentagram). I have the below alias in my autoexec.cfg to turn the gl_polyblend on and off with a 1 button toggle.

alias ft4 "gl_polyblend 1;a5;echo Colored Screen ON...;wait;bind PGUP ft3"

alias ft3 "gl_polyblend 0;a5;echo Clear Screen ON...;wait;bind PGUP ft4"

bind "PGUP" "ft4"

alias a5 "play buttons/airbut1.wav"

"1" turns on the filter. This really smoothes out mouse movement. This setting is a must for mouse users. See also "-dinput".

This setting is a must for mouse user. It is the default setting in the quake/id1 config.cfg

_snd_mixahead ".14"

There is no way to flush already loaded textures, so it is best to change these below texture options in the command line or autoexec.cfg and not at the console, or they will only take effect on some of the textures until you change levels.

Command line example: glquake.exe -game ctf +gl_ztrick 1 +gl_playermip 1 -zone 1024 %1 %2 etc.

This is the setting for the "sky fix" which should dramatically improve gameplay in some of those open area maps with lots of sky. The default setting "128" is automatically placed in the GL Quake & QW config.cfg. Use "gl_subdivide_size" at the console or place it in your autoexec.cfg to set the sky subdivision if it's still too slow with the default setting of "128". "256" or "512" are good values to try, with higher values being better for smoother gameplay. The higher the value setting, the more the distortion of the sky up close. To be honest, I don't notice any difference in the way the sky looks with higher settings. Valid settings are: 128, 256, 512, 1024, 2028

This variable drops the resolution of each player's texture to save on total texture memory. The player's skin will be more blurry with higher values. Important variable for cards with only 2 MB of texture memory in multi-player games. This setting has no effect on monster skins. Setting this to "0" or "1" on video cards with only 2mb of texture memory (Orchid R3D or Monster 3D etc.) can cause some buggy wierd texture effects or game crashing. Pure 3D owners can use any gl_playermip setting without fear, as the Pure3D has 4mb of texture memory. If you are a Voodoo1 user and serious about your multi-player game I would use gl_playermip 2 regardless of your texture memory. Voodoo II users can use any playermip setting w/o a loss in performance. If you change this during the game, it will take effect as soon as a player changes their skin colors.

This avoids clearing the z buffer at the expense of half the precision. You may occasionally see some things poking through where they shouldn't with this enabled. If the status bar and console are flashing every other frame, clear this variable.

* gl_ztrick 0 will lower timedemo2 FPS about 15%.

Multitextures support allows certain hardware to render the world in onepass instead of two. GLQuake uses two passes, one for the world textures and the second for the lightmaps that are blended on the textures. On some hardware, with a GL_SIGS_multitexture supported OpenGL implementation, this can be done in one pass. On hardware that supports this, you will get a 60% to 100% increase in frame rate. Currently, only 3DFX dual TMU cards (such as the Obsidian 2220 or the Voodoo 2) support this extension, but other hardware will soon follow. This extension will be autodetected and used. If for some reason it is not working correctly, specify the command line option "-nomtex" to disable it.

This causes all textures to have one half the dimensions they otherwise would. This makes them blurry, but very small. You can set this to 2 to make the textures one quarter the resolution on each axis for REALLY blurry textures. The setting "2" will only adds .5 FPS to speed. Definately not worth the blurr.

*gl_picmip 0 is default

*If you get an "Illegal Operation Error, Invaild Page Fault" set gl_picmip back to default of "0".

--------------------------------------------------------------------------------------------------------------------------------

*Commands are case sensitive. Use caps where indicated.

*Canopus Pure3D and Voodoo II users adjust the screenrefresh in the your control panel/display properties.

If you use the default screenrefresh settings on your 3DFX card, then in general, raising the vertical refresh will adversely affect your frame rate in GLQuake2. You'll have to decide if the performance hit is worth the improvement in the image quality. Generally, there's no noticeable frame rate penalty between running at 75 Hz as opposed to 60 Hz. As a matter of fact, the 3DFX Card won't even run at 60 Hz in 512 x 384 resolution - 75 is the lowest. I know some people get eyestrain when staring at a monitor with a 60 Hz refresh for long periods of time, but 75 Hz is usually sufficient to eliminate the problem. Setting it higher will start to bring your frame rate down a bit.

There is a way you can run the refresh up to 120 Hz without much of a performance hit: by disabling the vertical refresh sync on the 3DFX card by adding these lines to your Quake2.bat file: SET FX_GLIDE_SWAPINTERVAL=0, SST_SWAP_EN_WAIT_ON_VSYNC=0

Voodoo II users must set the monitor refresh rate for each video mode resolution with the below variables if you do not wish to set it in your Voodoo II control panel:

Example: SET SSTV2_REFRESH_800x600=75

Default: 1

With "0" setting, the 3DFX Card will ignore the refresh rate and always redraw the screen as soon as it can. As a bonus, this setting will usually gain you 5 -7 fps, however it can cause some image tearing which some people may find unacceptable. It will be very subtle and look as though the image is folding slightly when you spin around. With my Pure3D, "0" setting raised the speed a whopping 7FPS for me, over a setting of "1"(default). Nice!!! To use SET FX_GLIDE_SWAPINTERVAL "0" you must also use: SET SST_SWAP_EN_WAIT_ON_VSYNC=0

If you don't like the tearing associated with not waiting for Vsync, increase your monitor vertical refresh rate.

Voodoo II users go to your Voodoo II control panel (control panel/display/voodoo II/advanced) and place a check mark in the "Don't synch buffer swaps to monitor refresh rate for glide" and hit "OK". Voodoo II users will get a huge increase in FPS. This is same as using SET FX_GLIDE_SWAPINTERVAL=0

"0" Turns off syncing to the monitors vertical refresh rate so the screen gets refreshed before its fully written on the monitor.

Normally your Voodoo will wait for the electron gun to finish sweeping the screen before switching between the visible data and the in work data. Setting to "0" this means that the voodoo will not waste any time waiting, it will switch immediately.

The Orchid voodoo defaults to 50. You can gain approximately a 15% speed increase by overclocking to 55. Do not go beyond 57. In any event keep an eye out for corruption artifacts - flat shaded polygons, texture map corruption etc. You will see little flickering triangle shaped tears in the screen if you set the clock speed to high. This setting will almost certainly make the Voodoo Chip run hotter so beware! How high you can go on the setting is solely dependent on how much cool air circulation you have in your computer case. When picking a PCI slot for your Voodoo Card , choose a slot that will give maximum air circulation to the Voodoo chips. With my Orchid (no fan) my screen started slight tearing at "57". "60" gave extreme tearing. Also note that the Monster 3d's default performance setting is "57", so that can be taken as a safe setting. Be forewarned, any setting over "57 "will certainly shorten the life of your card. If your image locks and the sound is looping, your overheating the chip. Turn down the clock speed if this happens.

*Get a cooling fan to increase performance and card life.

*After installing a fan on my Orchid Voodoo Card. I could go to "60" w/o tearing. But I still leave mine at "54"

** The Pure3D needs to have the clock speed adjusted from the Pure3D control panel in display properties. The Pure3D uses 35ns RAM and can be successfully over-clocked to higher numbers than the 45-50ns RAM on the Monster and Orchid. I have been running my Pure3D at 60mhz for months and hundreds of hours of Online Quake play with no problems at all. I also have 2 extra fans on the Pure3D. See below taken from the Pure3D help guide:

-------------------------------------END PURE 3D HELP GUIDE INFO------------------------------------------

Default: 90 (for Voodoo II, and must be overclocked in the registry)

One important note. The Monster Voodoo II allows overclocking in the Monster Voodoo II control panel to 95 MHz. Since the Creative Labs Voodoo II and the Monster 3D Voodoo II are identical, this can be taken as a safe speed to overclock your Creative Labs Voodoo II. Anything higher and your sailing into uncharted waters. Your success in overclocking depends highly on how much cool air you have circulating around in your computer case. If you plan on exceeding 95 MHz, get a cooling fan on your Voodoo II. If you see corruption in your game image or your game image locks up, turn the clock speed back down a notch or 2 until it disappears.

Start the Registry Editor by going to "start/run" and type "regedit" in the box and hit "OK". Once into the registry, choose "Edit", "Find" and do a search for "SSTV2". This will lead you directly to where you want to be: "HKEY_LOCAL_MACHINE\SOFTWARE\3Dfx Interactive\Voodoo2\". This key has 2 subkeys, by the name of:

"HKEY_LOCAL_MACHINE\SOFTWARE\3DfxInteractive\Voodoo2\D3D" and "HKEY_LOCAL_MACHINE\SOFTWARE\3Dfx Interactive\Voodoo2\Glide".

You will have to add the new string to both folders (D3D & Glide) if you want to change the clock speed of the Voodoo2 for Direct3D as well as Glide games. Quake is a "glide" game. Now right click on either the "D3D" folder or "glide" folder and select "New" and then "String Value". Then type the new variable "SSTV2_GRXCLK" (caps & no quotes) in the box. Then double click on the new variable you just added and enter the clock speed you want the Voodoo2 to run at. Default is "90'" for 90 MHz, so you obviously want to go higher than 90. So if you want to set it at "97" just type in the box "97" w/o quotation marks and hit "OK" and then hit the "X" in the top right corner. All done. If you want to set it back to the default just change the value back to "90".

Default: 0

"1" Removes the 3DFX logo on startup.

Default: 0

"1" tells the Voodoo you have EDO RAM and to access the RAM on your board faster. This may or may not have any perceptible difference.

Default: 0

"1" Fast PCI read. 1 or 2 more FPS.

This may not have any perceptible effect.

This line must also be in your batch file on some Voodoo 1 boards to adjust the gamma (brightness):

SET SST_VIDEO_24BPP=1

*Canopus Pure3D and Voodoo II users adjust the "RGB" gamma in the control panel/display/voodoo properties. If the screen refresh rate is set higher than 75 on the Pure3D, your gamma may not work.

*Adjustable in .1 increments. "1" is the default

*Canopus Pure3D users adjust the color gamma in the Pure3D control panel/display properties.

Default:0

"1" sets the bits per pixel to 24. Which does nothing. READ ON!!!! If you want to adjust gamma on some Voodoo 1 boards, you must have it set to "1" in the batch file or autoexec.bat. Don't use it "1" unless you have to.

• "-heapsize 16000" would be 16mb. (same command as "-winmem" in regular quake)
• Don't exceed 50% of your ram. 32mb heapsize should be plenty if you have 64mb or more.

Example of command line: glquake.exe -game ctf -width 640 -height 480 -bpp 16 etc……..

400x300 *extremely fast FPS, but very small image on screen makes it useless.

512x384 *fastest FPS in a useable video mode, was 20fps faster than default for me. Set refresh rate to 75 or higher

640x480 *default and highest supported by Voodoo 1 and 6mb Voodoo II

1024x768 *highest supported by (2) Voodoo II cards run in SLI mode. 8mb or 12mb

1152x864

1280x1024

To use a three button mouse with GLQuake, your Windows mouse driver must support three buttons. Use the Logitech PS/2, Serial or Bus driver instead of the Microsoft or Standard PS/2, Serial or Bus driver. Also, make certain that your Mouse control panel sets the middle button to "middle" and not "double click".

*I had to use the Logitech drivers that came with my mouse to get my 3 button Logitech to work correctly. The 3 button drivers on the Win95 CD-ROM would not work.

A game port is on your system, however a joystick is not connected, or if connected it isn't calibrated. You can ignore joystick input by typing "joystick 0" at the console or adding "joystick 0" to your config.cfg. You can also disable the joystick port by entering -nojoy at the command prompt.

example: GLQUAKE.EXE -nojoy

• Remove the "-nojoy" command, if you use my included batch file.

HOW TO CHECK YOUR "FRAMES PER SECOND":

*To perform the upgrade, unzip "q101-106.zip" into your quake folder and say "yes" to overwriting all files. Then double click on the "patch.exe" file in the Quake folder. The update to version 1.06 is complete at that point.

To perform the Timedemo2 test. Start GL Quake and bring down the console and type:

timedemo demo2

When the demo starts, immediately raise the console where you can see the full screen. (a lowered console affects the "FPS") As soon as the demo2 completes, bring down the console and look for the number with "FPS" beside it. This is your "frames per second". The higher the better. Only use "demo2" for this test, as it contains a good combination of water and land travel. Some of the settings (gl_polyblend "1") will affect your FPS only in the water.

Note: If you run the game without the ammo, score and health bar showing this will cost you about 3 FPS.

I was able to get 39.7 FPS-v.97 (Orchid 3Dfx) with the recommended batch file and autoexec settings included with this document. I ran the test with the ammo, score and health bar showing and used the default video mode(640x480).

*I have my maps vis'ed which reduced my Timedemo2 FPS by 7 FPS.

My system is:

PPro 200 w/ 128mb

STB Virge 3D 8MB PCI Graphic Accelerator (this card handles 2D applications)

Orchid Righteous 3Dfx 4MB Video Card (this card handles GL Quake and other 3dfx open gl games)

CANOPUS PURE 3D TIMEDEMO RESULTS:

Just installed my Pure 3D (11/22/97) and thought I would include the timedemo results on the same system as above with the recommended batch file and autoexec.cfg settings, except I used gl_flashblend 1, 512x384 console resolution and set the Pure3D clock at 60 MHz . Maps are not water vised for these timedemo tests. 3 Fingers' Anti-Slowdown Missile and Grenade mdls were installed.

GL Quake version .97

Drivers:

DirectX5 Core Distribution Drivers

Pure3d 1.30 drivers (includes Pure3D version of glide 2.43)

Bigass1 Demo Test Timedemo2 Test

512x384- 43.4 FPS 512x384- 72.4 FPS

640x480- 39.1 FPS 640x480- 51.0 FPS

My system is:

PPro 200 w/ 128mb

STB Virge 3D 8MB PCI Graphic Accelerator (this card handles 2D applications)

Maps are NOT vised and included autoexec.cfg and GlqV2.bat was used with default viewsize and toolbar.

V Sync Disabled

75MHz Monitor Refresh Rate

3 Fingers' Anti-Slowdown Missile and Grenade mdls were installed and gl_flashblend 1 was used.

GL Quake version .97

Timedemo Demo2

800x600- 85.5FPS

640x480- 102.3FPS

Timedemo Bigass1

800x600- 50.8FPS

640x480- 51.4FPS

The bigass1 demo is a 16 player DM demo to 50 frags. This test will run about 20-30% slower in FPS than the timedemo2 test. The reason is, there is much more activity (more shooting & explosions) in the bigass1 demo test. The Bigass1 Demo is much closer to real Internet play than the wimpy timedemo2 test. If you are not getting at least 25FPS on the Bigass1 demo test, you should consider some upgrades if you want to be competitive in online multi-player games. Just for your information, I ran approx. 200 or more Bigass1 timedemos when writing this Tweak Guide. Also when checking your Voodoo overclocking speed for image corruption, you should run 4 or 5 Bigass1 timedemos in a row to really put it to the test.

The "Bigass1 Demo" can be downloaded at:

Just unzip the file into your quake/id1 folder and type at the console:

timedemo bigass1

You can easily make your own fan mount to keep your 3DFX video card running cool. Go buy a CPU fan at Radio Shack ($12). Then take a blank plate from the back of your computer like the one you removed when you installed your 3D-video card. Go outside to a concrete surface and smash the plate's 90-degree bend out flat with a hammer. Then lay the fan on the plate and mark 2 mounting holes to be drilled to secure the fan to the plate. Drill the holes and mount the fan onto the plate using 2 sheet metals screws, or even better use threaded screws with nuts. Put a drop of Lock-Tite on these for more security. File or cut off any protruding screw tips that could touch any electrical components. Then attach the mount to an empty slot mounting hole over or near the 3D video card. Make sure the (2) fan mounting screws cannot possibly touch any electrical component in your computer. Bend the mount to whatever angle you need to point the airflow on the 3DFX Voodoo Chips. I can't give you specific instructions, as each system is different. I also added a 3 1/4" fan in an empty fan slot in the front of my computer case behind the 1" speaker.

I just finished playing a 1 hour online Quake World CTF game with the Dual Voodoo IIs overclocked to 105 MHz and then I ran 5 Massive1 timedemos in a row. No problems at all. This fan is the shit. And inexpensive too. Total cost to cool (2) Voodoo II boards: $13.48.

Power Connector and Wiring Information

Retail Store: Radio Shack

Catalog Number: 278-766A

Description: 10" (254mm) DISK DRIVE Y-ADAPTER POWER CABLE (allows 2 devices to be powered from one cable)

Go here to download the "3Fingers Quake Anti-Slowdown Missile & Grenade MDLs" (filename: missile_fix3.zip)

These missile.mdl and grenade.mdl files will help counteract the slow down in FPS when you are in Multi-player Rocket and Grenade battles. Several players all firing glowing rockets with smoke trails within your field of view will slow your FPS down alot. The 3 Fingers' missile.mdl file does not glow or have a smoke trail in transit to the target and will boost your FPS in Multiplayer Rocket battles as much as 10FPS.

I have removed the smoke trail in the Grenade.mdl which will help also. But since the standard grenade.mdl only had a smoke trail and did not glow, it won't help as much as the missle.mdl. However the grenade.mdl does help some to reduce lost FPS.

The combination of the 2 mdls will give you a much higher FPS in Multi-player when the rockets and grenades start flying.

*If you can't find the missile_fix file, email me (bjacobs@home.com) and I will send it to you. It's about 14kb.

•Right click on "My Computer", click on "Properties", click on the "Performance" tab, then click on the "Virtual Memory" button.

•Click on "Let Me Specify MY Own Virtual Memory" then click "Disable virtual memory" then click "OK". The computer will reboot.

•When it reboots run the Disk Defragmenter and do a Full Defragmentation of your drive. At this point do not reboot after defrag.

•Go back into the Virtual Memory settings window and uncheck "Disable Virtual Memory" then select "Let me specify my own virtual memory settings". Set the "Minimum" to 150 (200 for Unreal) and the "Maximum" to 150 (200 for Unreal). Windows will reboot again to allow the settings to take effect.

If you have more than one drive on your system, you should select the fastest drive for your swap file.

The setting labeled "Typical Role of This Machine "determines how much space is set aside in main memory to handle path and filename caching. The default "Desktop Computer" choice allocates space for a paltry 32 paths and 677 filenames, whereas the "Network Server" choice bumps those settings up to 64 paths and 2,729 filenames.

If you have 32 mb or more of ram, you can improve performance by increasing your disk cache size:

•Right click on "My Computer", click on "Properties", click on the "Performance" tab, then click on the "File System" button.

•Select the "Hard Disk" tab and in the box labeled "Typical role of this machine:" select "Network Server". The click on "OK" and Win95 will reboot to allow this setting to take effect.

*This works fine on the new Win95B OSR2 (ver. 4.00.950 B). To check your Win95 version, go to "control panel/system". Older versions of Win95 will need to modify their registry as instructed below before changing the "typical role of this machine" setting.

HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Windows\CurrentVersion\ FSTemplates\Server\NameCache

To: a9 0a 00 00, and \PathCache to 40 00 00 00.

Anyone running GL Quake on a 32 mb system should really consider upgrading their ram to at least 64mb. Then use "-heapsize 32000". GL Quake could easily use up to 32mb and more in some situations. Ram just dropped in 1/2 on price in the last 2 weeks. I bought an additional 64MB EDO 60ns recently (10/20/97) for $250. So now I have 128mb. I noticed a big difference going from 64mb to 128mb as now I get absolutely no disk thrashing during gameplay. With 64MB I would get occasional hard drive thrashing during quake net play. Also all my programs open up and close out instantly now on my PPro200. GL Quake loads twice as fast now. So I would say for the true Quake enthusiast, 96mb would be ideal. Then use about "-heapsize 36000".

-nocdaudio -nojoy -noipx

For the best performance when playing Quake always disable any applications you have running in the background like Anti Virus programs, IE 4.0 active desktop and Microsoft Office 97 active desktop etc. If you have less than 64MB of RAM, go to the Gamespy options menu and set Gamespy to "close Gamespy after launching Quake".

MS Fast Find in Office 97 will cause you to have extreme slowdown in Quake2 as well as slowing down your whole system. To keep MS Fast Find from running in the background, go to your windows/start menu/programs/start up folder and delete the "Microsoft Fast Find" shortcut. Basically I delete everything from my windows/start menu/programs/start up folder. I don't want any programs running in the background to slow me down while I'm playing. To play it safe, just keep a backup of the shortcuts you remove from the "startup" folder in case something does not work right, then you can put them back. My system runs perfectly with all the shortcuts removed from the "startup" folder.

I use and highly recommend the excellent Quake Marines Neon Crosshair. Its about half the size of the new QW2.10 red crosshair and comes in 3 colors to choose from (red, blue, or green). I use the blue. I prefer the Quake Marines Crosshair over the RED LED QW2.10 crosshair 2. Sorry Zoid, nothing personal!!!(:(: It works in Regular and GL Quake and also Quake World. Go to the below Quake Marines webpage to download it. You won't be sorry.

NOTE: The Quake Marines Crosshair Program is a 4MB Installer program. It also will optionally install player skins with neon stripes that don't work with GL Quake or GL QW. The player skins are supposed to glow in the dark, but don't glow in the GL versions of Quake or QW. If you want to avoid downloading the installer and skins. I have extracted the 3 different color crosshairs and zipped them into a 139kb file with full easy instructions. Get the 139kb crosshairs file here:

Once the mods are installed, they will work on any server you play on. Get them here:

Quake/QW non-glowing missile and grenade mdls which boost frame rate in multiplayer rocket and grenade battles as much as 10FPS.

For Quake/QW. Makes all runes, backpacks, powerups, bio-suit, armor and weapons glow like a spot light is shining on the objects. You can spot these items when no one else can see them in darkness.

No crossdressing skin for Quake/QW. Only the shoulder patches change color when a player selects a top color. Great for CTF.

Never worry about a cross-dresser again. See screenshot in zip file.

Makes the nails from the nail gun and super nail gun glow red in transit to the target. You can see them in the dark.

I'm going to stray off of the GL Quake/QW topic for a minute and discuss what is probably the most important issue to online gamers there is. So let's get to the meat of the matter. Why does my NET Quake game have fluctuating pings and high packet loss?

First of all I want to say I have tried every trick, lag fix, Max Mtu, delagger, gadget, setting, special phone line wire, different modems and any other supposed fix for lag known under the sun. The bottom line is, if your poor connection is a result of any problem which happens AFTER your signal gets to your ISP. Nothing that you do on your end will help. It is absolutely impossible for your computer to some how magically create a packet(s) of information that were lost or held up. Lost packets cause freezing gameplay, held up packets cause high ping. You can spray all the perfume on a pile of doodoo you want, and you will still have a pile of doodoo. Quake World does an excellent job of filling in small packet loss (1-7%) with its movement prediction. But higher packet loss than 7% is beyond the ability of Quake World's prediction to keep the game smooth. Quake World predicts the games progression in the event of packet loss/delayed packets and then corrects it to the true state when the packets catch up. This is what causes you or other players to appear and reappear in 15ft. jumps or gaps. To someone looking at a webpage while surfing the net. Packet loss/held packets translates into a webpage loading in slightly more time.

So lets do a little INTERNET 101. The Internet began in the 50's as a source for the military to send top secret information broken up into packets so they could split up classified information into separate parts along separate routes. So some of the equipment is getting very old now. The whole Internet revolves around sending a stream of small packets of information from your computer to other computers and back to you. When your computer sends a packet, which it sends and receive many packets a minute. The packets travel through a series of Hops. Usually about 8 to 40 hops before it reaches its final destination. The first hop is from your computer to your ISP. The packet then hits a router and will hit 1 or 2 more routers within your ISP. This would be hop 2 and 3. Your ISP leases a T1or T3 (equivalent to 30 T-1 lines) line from a company like Bellsouth.net, MCI.NET or Sprint.NET etc.. A T1 line can transfer about 5mb per minute and a T-3 line about 150mb per minute to another T-3. The packet is then sent to a Backbone Hub from your ISP's T1 or T3 line. This is hop 4 and would be the Backbone Hub which your ISP uses. A Backbone is a major transfer station for packets. Everything your ISP sends and receives is going to pass through this Backbone Hub. A few hundred ISPs may send and receive packets from this backbone. Within each Backbone there are usually 2 or 3 routers. These are more hops. After your packets leave the Backbone Hub, which your ISP uses, your signal will branch out to any number of Backbones to get to its destination. There are many Backbones though out the world. Most of them are in major cities. The packet could then be sent on to another Backbone and even another before it reaches its final destination. In Quake Net Play, most servers that give you a decent ping are about 8-15 hops from you. So the bottom line is, if any of these hops are overloaded or has equipment problems, you will see packet loss and fluctuating ping. A chain is only as strong as it's weakest link.

If you can't find it, Email me and I'll send it to you. It is about 35kb. What UO Trace does, is trace all the hops from your computer to the IP Number you enter. For our purposes it would be the Quake server IP. It will then continuously display each hop and tell you what the packet loss is and the current ping/lowest ping/highest ping values on each hop. UO Trace is much more superior to the DOS tracert/ping method, as DOS Tracert only pings 3 times. And with DOS Ping, you would have to ping each HOP IP separately. With UO Trace constantly pinging all hops simultaneously, you will be able to quickly identify which hop or hops are causing your bad connection. You can even save the UO Trace info by clicking on "edit" then "copy" and paste it to Notepad.

For Example: If your favorite server is 12 hops away and you see hop number 4 has pings constantly fluctuating from 125 to 800. This would have a serious affect on your gameplay. If you get wildly fluctuating pings and packet loss on all quake servers, the problem will most likely lie between you and the end of the first backbone hub that your ISP uses. So this means its one of these factors:

[1] Your phone line or an overloaded ISP router (hop 1)

[2] Your ISP is overloaded (probably hop 2 and 3 or could be hop 4).

[3] Or the Backbone that your ISP uses is overloaded (probably hop 5,6 and 7).

If you see that the problem lies on the 1st hop (your phone line to your ISP), and you connect at 28.8 or higher all the time. Its not your phone line and the problem lies in your ISP's overloaded or piece of crap router. If you cannot connect any higher than 21.6-26.4bps. Bug the hell out of your Phone Company and make them install a new phone line to your house from the box at the street. Tell them your are sending sensitive computer data/faxes and you are getting many errors and failed transmissions. Also tell them that you hear occasional static on your line. Trust me, the Phone Company Techs do not understand anything about computers/internet or how it works. The Phone Companies mentality is, if you can talk on your phone the line is OK. Tell them what ever you need to say to get a new phone line so you can connect at 28.8 or 31.2. Also if you determine your phone line is a problem. You can request that the Phone Company " put your phone line on another pair". What this means is, your phone line to the main Telephone Office will just take a different route. It is worth a try sometimes.

So what can be done to fix the fluctuating pings and packet loss? Sadly your ISP won't care and will most likely just tell you what you want to hear to get you off the phone. Most ISP's owners are happy if a webpage loads in 45 seconds or less and considers this acceptable. Online gamers are an extremely small percentage of their customer base. And they won't spend the large sums of money to upgrade their equipment or take the time to try to sort out the problem with their Backbone that they use, just to help out less than 1% of their customers. Even if an ISP system administrator is willing to try to solve the problem. The facts are 99% of ISP system administrators lack technical knowledge beyond setting up new accounts, Dial Up Networking settings and resetting modems.

OK, on to solving this dilemma. For Example: If you saw while using UO Trace, that hop 4 with wildly fluctuating pings was MCI.NET in Greensboro, N.C. Then you must try another ISP that does not use MCI.NET Greensboro, N.C. as their Backbone. Ask the prospective new ISP who their Backbone hub is. Don't think getting ISDN service from your current ISP that gives you a poor connection on a 33.6 modem will improve anything. Your signal will still travel the same route after it gets to the ISP as your 33.6 dial up service. You will just get a lower ping with a shitty connection. If the ISP you are talking to about new service does not have their own in-house T1 or T3 line, don't even consider them. This means that they are routing your dial in phone call to some other place that has a T1 line, maybe another city. This is very bad. AOL, IBM.Net, Bellsouth.Net and other large ISPs handle it this way to keep from installing T1s in every small town they provide Internet service to. Some small ISP's do this also if they can't afford to pay for their own T1 or if they have a satellite office in a nearby town. I even spoke to an ISP owner that when asked if he had a T1 line in-house. He responded he uses an ISDN (128k) line to run his ISP. This would yield pathetic results for his customers that play Net Quake, unless he only has 2 customers.

You will have to dig for info on what ISPs are available in your town, as they pop up monthly and are not listed in the phone book yet or choose not to list themselves. Keep trying new ISPs till you find one that gives you a good stable connection. I tried 9 ISPs in my town before I finally found one that gave me excellent net gameplay. The general rule of thumb with ISPs is: the smaller they are, the better they will be for Net Quake . But this is not always true. One other point. People are signing up with ISPs like crazy to get on the Internet. An ISP that is good today may not be good for Net Quake in 2 months if they double their customers or take on more customers than their equipment can handle. One thing I have learned from dealing with many ISPs, is they all lie and tell you their service is wonderful and never admit they have a problem. Always negotiate a free trial period to test them out.

This webpage has all the latest tips for USR X2 users to help you stabilize and lower your ping during Quake 2 Internet play.

Here is another trick for USR X2 users to eliminate the fluctuating pings associated with X2 connections. Go to Start->Settings->Control Panel->Modem->Properties->Connection->Advanced and in the "extra settings" box, add this: S32.5=1

56K connections have been proven to cause high fluctuating pings with some users. This disables X2 connections and makes your modem connect at only 33.6. Or if your ISP has a 33.6 dial in number. You can just dial into your ISP's 33.6 modem bank when you want to play online Quake 2 instead of adding the extra setting.

A very comprehensive page with all the tricks to get good pings in Quake. This page comes highly recommended by my good friend "The Flying Penguin".

Just thought I'd throw this one in here. Gives packet loss info for Regular Quake and Regular GL Quake. By typing "net_stats" at the console you will presented with a packet loss chart. Look at the "dropped data grams". This is the important value to check. It is dropped packets and this is what causes freezing gameplay. Each packet that is lost will cause you to freeze for a second or 2. It will keep a running total of the values from the time you sign onto the server. If your packet loss is high. Get a better ISP.

The current version .97 of GL Quake does not offer the option of "direct" or "modem play". Only TCP/IP (internet, the one we love) and IPX are offered in the multi player menu.

---------------------------------------------------------------------------------------------------------------------------------------

A. Memory is usually the problem: Make sure you have at least 16 megs of RAM (32mb for netplay) and a 100MB swapfile allocated in Windows '95. If you do have both, try defragmenting your machine to make sure the swap file isn't fragmented. If this doesn't work, check your drivers for the latest versions.

A. If you have a 3Dfx card, check to make sure you have the correct OpenGL32.dll that came with GL Quake installed in your QUAKE directory. If you do not have a 3Dfx card it is likely that your card does not support the features necessary to run GLQuake, or your drivers are not correctly installed.

A. Try this:

1. Right click on your GLQW batch file and select properties.

2. Select "program" tab.

3. In the space next to "run", select "minimized".

4. Put a check next to "close on exit".

5. Hit "apply" then "OK"

A.. For instance, during multi-player games when there are a lot of players on the screen all shooting rockets. Or when running "mods" such as ThunderWalker CTF or PainKeep, Quake will run somewhat slower, thus reducing the frame rate. Also, the Quake engine slows down considerably in maps with large open areas. This happens in several places in the Quake Mission Packs. Having a higher available FPS prevents the game from bogging down in these situations. Essentially, the higher the available frame rate, the better.

A. This simply means you need to set your desktop color palette to at least "16-bit high color". Go to "control panel/display/settings" to set the color palette.

*setting to "24 bit" MAY give the error message "specified video mode not available".

A.. S3 968 and 868 chipsets may mis-report the mapped memory used. There is a chance that your Voodoo Graphics card will be assigned by Plug and Play a memory range that is used by the S3 card, but not reported. The Voodoo Graphics card can be relocated by:

Windows NT Users: An NT service called NTREMAP is installed when Glide is added to an NT system. NTREMAP can change the memory address of a Voodoo Graphics board and prevent a conflict with an S3 card.

To use NTREMAP, add the following registry values to:

\HKLM\Software\3Dfx Interactive\NTRemap

EnableNTRemap DWORD 1 (HEX)

ForceAddress DWORD 12000000 (HEX)

The Force Address setting will vary, in this example 0x12000000 is used. This is normally free on most systems.

NOTE: If you use an address that over-writes another device, Windows NT may not boot. If such a problem occurs, power off the system and remove your Voodoo Graphics. Alter the registry to use a different memory range (or remove the ForceAddress setting). Then Reinstall the Voodoo Graphics card into your system.

A .This is usually caused by trying to run an invalid video mode, i.e. 800x600 or too high a bit depth. You can try running with "-window" in the command line. In addition, using the older OpenGL32.DLL with the newer clients can cause this error. Make sure you're in at least 16 bit color on your desktop, and try running without command-line options. If your using Quake World add a folder in your quake directory and name it "qw". So the path will be "quake/qw". GLQW will set-up the inverse palette in the "qw" folder the first time you run GLQW. Also, as a last resort, set your 2d card refresh to 60hz.

Q. My image locks up immediately or after a small amount of time. I am not overclocking my 3DFX card, so I don't think it is a heat issue. I have reinstalled my 3DFX Video card drivers several times and I cannot eliminate this problem.

Some of the early Orchid R3D cards had RAM Chips that say "SEC" on the RAM Chips. The early cards had problems with lock up especially if they were overclocked the least bit. All you have to do is look at the RAM chips and if they say "SEC", then call Orchid customer service and they will send you a new R3D no questions asked. This was widely publicized on the Internet around June/July 97.

-----------------------------------------------------------------------------------------------------

Problem: I have a Mystique/Millenium and a Monster 3d/Orchid Righteous etc., and when I start a 3dfx game, demo or benchmark, OR when I want open Win95 display properties by right clicking on the desktop, my computer locks up and I have to reboot.

Solution: Try moving your 3dfx card to PCI slot 1 and the Matrox card to PCI slot 4. When you restart your computer, Windows95 should notice the changes and assign resources accordingly. People have also had success with putting the cards in the opposite configuration: Matrox card in PCI slot 1 and 3dfx card in PCI slot 4.

Q. Can I use two different manufacturer's Voodoo2 boards in SLI mode? (ie. One Diamond card and one Creative card?)

A. No. They must be the same Voodoo II cards from the same manufacturer. (ie. two Creative Labs 12mb Voodoo IIs)

Q. Can I use two different configurations of the same manufacturer's Voodoo2 board in SLI mode? (ie. One 8MB and one 12MB board?)

A. No. They must be the same Voodoo II cards from the same manufacturer. (ie. two Creative Labs 12mb Voodoo IIs)

Q. What is Triple Buffering?

A. What triple buffering does is improve the frame rate up to a maximum of the monitor refresh rate - triple buffering will not get you results higher than monitor refresh, though. It just smoothes out the drawing time to approach the monitor refresh rate and allows the Voodoo II to get framerate (FPS) as high as the refresh rate. It allocates additional framebuffer memory to use for image storage. Normally you have 2 color buffers and 1 zbuffer. With these settings, you have an additional color buffer that the Voodoo2 will use to store an image it has already created but which has not yet been sent to the monitor. Otherwise, if all the buffers were full, the card would have to wait until it sent an image to the monitor before working on the next image. Older versions of the miniGL driver for Voodoo2 do not enable triple buffering by default – future releases will. The next release of the miniGL driver is scheduled 3/23/98. If you are using the latest 3DFX Voodoo II drivers, you will have a box to check in your Voodoo II control panel/advanced tab to enable triplebuffering. If you are using the latest drivers with this "check box for triple buffering" and want to enable triple buffering, just check the triple buffering box and add only the below autoexec.cfg lines and REMOVE the check from "Don't synch buffer swaps to monitor refresh rate for glide" in the Voodoo II control panel/advanced tab.

Add this to your Quake 2 autoexec.cfg

set gl_triplebuffer "1"

set gl_ext_swapinterval "1"

set gl_swapinterval "1"

The SET FX_GLIDE_ALLOC_COLOR=3 is not needed as checking the triple buffering box performs the same function.

Add this to your Quake 2 Voodoo II Batch File or Autoexec.bat (only if your drivers don't allow triple buffering to be checked from the Voodoo II control panel/advanced tab):

SET FX_GLIDE_ALLOC_COLOR=3

REMOVE the check from "Don't synch buffer swaps to monitor refresh rate for glide" in the Voodoo II control panel/advanced tab.

Now your FPS can go up as high as your refresh rate and you get no tearing that is associated with disabling sync, but you get the advantage of your FPS going as high as the refresh rate.

Q. What will give me better performance, "triple buffering" or "Don't synch buffer swaps to monitor refresh rate for glide"?

A. If you don't mind the slight image tearing associated with "Don't synch buffer swaps to monitor refresh rate for glide" then this will give better performance as your framerate is not restricted by the monitor refresh rate setting. With triple buffering enabled your framerate can never exceed your monitor refresh rate.

Q. What causes my toolbar to flicker?

A. The new 3/23/98 mini gl enables triple buffering by default. So add "set gl_triplebuffer 1" to your autoexec.cfg and it will stop.

Q. Can I use the Monster 3D Voodoo II drivers with my Creative Labs Voodoo II.

A. The latest Monster 3DII drivers prevent. The latest version of the Monster 3DII drivers won't allow any Voodoo II except the Monster 3DII to work. The Monster drivers have a detection utility and if it detects any card other than the Monster it won't work.

Q. My Voodoo II won't install correctly and I am getting errors when trying to run games.

A. To install your Voodoo II drivers. First remove your Voodoo II from your device manager. If it is not listed under "sound, video and game controllers" in the device manager, look under "other devices" in your device manager and remove the "PCI multimedia device". Then go to your "windows/inf/other" folder and delete any .inf files that are related to any old 3D cards you have removed and any current drivers for your Voodoo II. Then reboot and Win95 will detect the Voodoo II. Direct (browse) Win95 to the folder where you have the Voodoo II drivers. Then it may ask for your Voodoo II CD for a Direct X file. If it does, just direct it again to the folder where the Voodoo II drivers are located.

Q. After installing two Voodoo II boards for Scanline Interleave (SLI), I only see a black screen (or a black screen with occasional horizontal streaks) on my monitor when the Voodoo2 is activated.

A. The solution to this problem is to switch which Voodoo2 board your monitor is connected to (also move the pass-thru cable from your 2D card to the same Voodoo2 board that is connected to your monitor).

The way the Voodoo2 initialization code currently works is the first board the 3Dfx PCI library finds is setup to be the video/monitor "Master." The other board in the SLI set is setup to be the video/monitor "Slave," and will not generate valid video output. The difficulty is that there is no way by looking at your system to determine which board will be found first by the PCI library (in some systems, it's the board closest to the CPU -- in other systems, it's the board furthest from the CPU). So, for early releases of the Voodoo2 drivers, you may have to manually swap which board is connected to the monitor for proper SLI functionality.

Q. Can I disable "vsync to monitor refresh rate" with Voodoo2 running in SLI mode?

A. Yes, although your results may vary. If you are running Voodoo2 in SLI mode with vsync disabled and experience visual anomalies (notably the appearance that every other scanline is missing, or one scanline being a frame ahead of the other) turn vsync on, which will force the boards to swap buffers together.

Q. How can I adjust my monitor refresh rate in a batch file with the Voodoo II if I don't want to set it in my Voodoo II control panel?

A. The monitor refresh rate must be set for each video mode resolution with the below variables:

SET SSTV2_REFRESH_512x384=60/75/85/120
SET SSTV2_REFRESH_640x400=60/75/85/120
SET SSTV2_REFRESH_640x480=60/75/85/120
SET SSTV2_REFRESH_800x600=60/75/85/120
SET SSTV2_REFRESH_1024x768=60/75/85/120

Example: SET SSTV2_REFRESH_800x600=75

Q. I have installed my new Voodoo II video card and I don't have a Voodoo II tab in my Control Panel/Display.

A. You can only have up to a TOTAL of 12 tabs in your under "control panel/display".

1) First back up the registry in case you screw up something.

2) Go to "start/run" and then type in "regedit". Then find the below key in your registry:
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Controls Folder\Display\shellex\PropertySheetHandlers\"

Check how many entries for display tabs you have in the above key. Under Win95, you are stuck with 4 tabs (Background, Screen Saver, Appearance, and Settings) which do not show up here. If you have more than 8 under this registry key, you won't see anymore than 8 plus the 4 you are stuck with in your display tab. These 8 plus the 4 you are stuck with equals 12 tabs. If there is a tab you never use, you can remove it here. If there is a tab for hardware you replaced or removed, but didn't delete it from Control Panel\System\Device Manager before removing from your system, delete that tab here.

3) Then reboot for your new display tab to take place.

Q. I am having problems trying to run my Voodoo II with my S3 Virge 868/968.

-------------------------------------------------------------------------------------------------------------------------------

You Can Download The Latest Version Of "The 3 Fingers' Quake 2 Tweak Guide" At:

For The Latest Version Of The 3 Fingers' Ultimate Tweak Guide For GL Quake & GL QW

Thanks go out to all the GL Quake gurus (Zoid, John Carmack, Zanshin, The Flying Penguin and 3DFX) for helping me with much of the information contained in this guide.

Also thanks sCary for making the Bigass1 Demo.

bind "`" "toggleconsole "

bind "*" "echo Commit Suicide;kill"

bind "ESCAPE" "togglemenu "

bind "0" ""

bind "1" "impulse 1 "

bind "2" "impulse 2 "

bind "3" "impulse 3 "

bind "4" "impulse 4 "

bind "5" "impulse 5 "

bind "6" "impulse 6 "

bind "7" "impulse 7 "

bind "8" "impulse 8 "

bind "9" ""

bind "/" "impulse 10"

bind "=" "say Thanks!!!"

bind "+" "say YES..."

bind "-" "say NO...."

bind "a" "say_team I'm Going For Armor Or Something, BRB!!"

bind "b" "say_team NEED HELP AT BASE (NOW)!!!!"

bind "c" "say_team IS OUR BASE CLEAR????"

bind "d" "say_team I'll Help Defend The Base!!!!"

bind "e" "say Oooooops!!!!!"

bind "f" "say_team I'm Going After Their Flag.(or ours)"

alias hel0 "say Hello!!!;bind h hel1"

alias hel1 "say Shalom!!!!!;bind h hel2"

alias hel2 "say Bon Jour!!!;bind h hel3"

alias hel3 "say Mon Ami!!!;bind h hel0"

bind "i" "say_team INCOMING ENEMY HAS QUAD!!!!"

bind "j" "say (: (: (: (: (:"

bind "k" "say_team PLEASE Give Me Rockets!!!(impulse 20)"

bind "l" "say_team STAY CLEAR OF FIRING ROCKET LAUNCHER!!!"

bind "m" "bas0"

alias bas0 "say_team The Enemy Has Our Base!!;bas1"

alias bas1 "say_team We Must Retake Our Base, NOW!!;bind m bas0"

bind "n" ""

bind "o" "say OUCHIE, Nice Shot!!!"

bind "p" "users;echo PLAYER NUMBERS......"

bind "q" "say_team Keep QUAD, PENTAGRAM and RING From Enemy!!!"

bind "r" "say_team WE NEED OUR FLAG PLEASE!!!!!"

bind "s" "say_team MOVE YOUR ASS GRAMPA!!!!!!"

bind "u" "say See Ya..."

bind "v" "say_team GOOD JOB MEN!!!!!!!!!!"

bind "w" "say_team MY HEALTH IS CRITICAL (Flag Carrier)!!!!"

alias net1 "r_netgraph 1;b4;echo Graph ON...;wait;bind x net2"

alias net2 "r_netgraph 0;b4;echo Graph OFF...;wait;bind x net1"

bind "z" "say_team I NEED A RUNE!!!!!;wait;wait;wait;wait;say_team IF YOU SEE ONE LET ME KNOW!!!"

bind "," "say_team HOW BOUT SHARING SOME OF THOSE PACKS!!!"

bind "UPARROW" "+forward "

bind "DOWNARROW" "+back "

bind "LEFTARROW" "+moveleft"

bind "RIGHTARROW" "+moveright"

bind "SHIFT" "+speed"

bind "ENTER" "+jump"

bind "ALT" ""

alias +cr "cl_forwardspeed 180;+moveright;+left"

alias -cr "cl_forwardspeed 500;-moveright;-left"

bind "." "+lookdown"

bind ";" "+lookup"

bind "SPACE" "say_team Extend The Defense For Flag Carrier!!!!"

bind "]" "say_team BASE IS CLEAR!!!!!!!!!"

bind "[" "say_team I Can't Get An RL!!!! Need Cover Fire!!!!"

bind "F4" "impulse 181;echo RUNE DROP"

alias water1 "r_wateralpha 1;a5;echo CLEAR WATER SURFACE OFF...;wait;bind F5 water2"

alias water2 "r_wateralpha .3;a5;echo CLEAR WATER SURFACE ON...;wait;bind F5 water1"

alias push1 "pushlatency -125;echo pushlatency -125;bind F6 push2"

alias push2 "pushlatency -150;echo pushlatency -150;bind F6 push3"

alias push3 "pushlatency -175;echo pushlatency -175;bind F6 push4"

alias push4 "pushlatency -200;echo pushlatency -200;bind F6 push5"

alias push5 "pushlatency -225;echo pushlatency -225;bind F6 push6"

alias push6 "pushlatency -250;echo pushlatency -250;bind F6 push7"

alias push7 "pushlatency -275;echo pushlatency -275;bind F6 push8"

alias push8 "pushlatency -300;echo pushlatency -300;bind F6 push1"

bind "F7" "say_team THE TEAM WITH THE BEST DEFENSE WINS!!!;wait;wait;wait;wait;say_team NO DEFENSE = WE LOSE!!! "

bind "F8" "say_team KEEPING OUR FLAG IS THE MOST IMPORTANT THING!!!;WAIT;WAIT;WAIT;WAIT;say_team NO POINT IN GETTING ENEMY FLAG W/O DEFENSE!!!"

bind "F9" "say_team TEAM, Everyone Attack Enemy Base Now!!!;wait;wait;wait;wait;say_team Haste & BM RUNE, Stay On Defense!!!!"

alias col1 "topcolor 666;b4;echo NEON COLORS;wait;bind F10 col2"

alias col2 "topcolor 3;b4;echo GREEN TOP COLOR;wait;bind F10 col1"

bind "F12" "echo RED TEAM;color 3 4"

bind "PAUSE" ""

bind "\" "echo ROCKET LAUNCHER selected.; impulse 7;wait;impulse 7"

bind "END" "echo GRENADE selected.; impulse 6;wait;impulse 6"

bind "PGDN" "echo SHAFT selected.; impulse 8;wait;impulse 8"

alias bes1 "impulse 2;wait;impulse 2"

alias bes2 "impulse 3;wait;impulse 3"

alias bes3 "impulse 5;wait;impulse 5"

alias -grap "-attack"

alias jattack "+attack;wait;-attack"

lookstrafe "0"

v_kickpitch "0.0"

v_kicktime "0.0"

gl_triplebuffer "1"

cl_crossy "0"

cl_crossx "0"

alias ft4 "gl_polyblend 1;a5;echo COLORED SCREEN ON...;wait;bind PGUP ft3"

alias ft3 "gl_polyblend 0;a5;echo COLORED SCREEN OFF...;wait;bind PGUP ft4"

alias aim5 "noaim 1;b4;echo AUTO AIM OFF...;wait;bind HOME aim6"

alias aim6 "noaim 0;b4;echo AUTO AIM ON...;wait;bind HOME aim5"

alias plf4 "gl_flashblend 1;a5;echo FLASH BALL ON...;wait;bind INS plf3"

alias plf3 "gl_flashblend 0;a5;echo FLASH BALL OFF...;wait;bind INS plf4"

alias a5 "play buttons/airbut1.wav"

\\\\\ *(GL) applies to GL versions of Quake and QW. *(QW) applies to regular Quake World and GL Quake World \\2.10

----------------------------------------------------END FRONTEND.CFG-------------------------------------------------------------------------

OPTION #2 GRAPPLE HOOK BIND

The below alias will select and fire the grapple hook with one press of the key and when you release the grapple key, It will change back to what ever weapon you had selected prior to firing the grapple hook. If you want to hang, then just change to a weapon as normal while holding in the grapple hook key.

Its works great for me in Quake World with 100% reliability, but since Regular Quake is more sensitive to complicated binds, it may not be reliable in Regular Quake. Regular Quake users may have to add some "waits" here and there to get it to work just right. Just change "MOUSE3" to whatever key you want to bind it too.

bind "MOUSE3" "+grap"

alias +grap "impulse 22;wait;wait;wait;+attack"

alias -grap "-attack;wait;wait;impulse 69"