Time for some few explanations about the config:
-----------------------------------------------

For those who just wants to try the config already; copy all files into OSP folder.
Run the game and write /exec autoexec.cfg in the console to run the cfg. I suggest that
you take a look at the config before however. Since it will probably make the screen black
for some users. R_displayrefreshrate is 100 in 1024*768 (r_mode 6). Not all monitors
support that. And the gfx is probably not the same. 


For the monitor:
----------------

seta r_displayrefresh "100"

This one is the most important for how many frames the graphics card is actually 
displaying on the monitor.
If you can put it on 120, then do it with you current resolution. That means it will run at
120 hz, the monitor will then show 120 frames from the game each second.
If you got 125 fps running in the game "forcefps 125" or "com_maxfps 125", it will then show
all the frames being drawn. There is the same handling of 120 and 125 in quake 3.
This means all the mousemovements(USB) and the frames will be shown. If you didn't see this 
before, you will then see the whole game as much smoother (if the fps is stable).
If not it will be a little choppy. 

seta r_swapInterval "1"

This is the q3 engines answer on vsync. That means the all the frames will be drawn before a
new one can be drawn into display. Making the game totally smooth to look at and move in.
But make sure you got enough fps to turn that option on. Otherwise you may end up running the
game at 50 fps. 

These two rendering options are the ones I see as the most important. R_mode is the resolution
of the game however. Aiming in 800*600(r_mode 4) is a little faster, and it seems you get a 
little more time to kill the enemies. Not true ofc, but it can feel like it because the frames
runs smoother over the screen, but also makes long distance shooting harder, bigger pixels. 
1024*768 (r_mode 6) gives you both short and long range shooting, But it may add some more 
choppy feeling to many gamers playing at this resolution. If you decrease the resolution, 
increase the refreshrate of your monitor. The goal is to try getting 120 hz. 

r_picmip 0 also makes the texture more sharp, I have myself always seen it as an advantage
to make headshots easier. The playermodels looks a lot more sharp and standing out of the 
background.

The mouse settings themselfs are in two different files. Long and close:

Close.cfg:
seta m_pitch "0.016" - makes vertical aim slower, headshots are a bit easier
seta m_yaw "0.022" - default horisontal speed
seta m_filter "0" - fake software mousesmoothing (always disabled)
seta cl_mouseAccel "0" - no accel (move the crosshair the distance you move your mouse)
seta sensitivity "1.2" - low kickass sensitivity, but corresponding to player movements
seta cg_fov 112 - makes the screen narrow in the sides, so you will also see more in the perifery
seta cg_drawgun "0" - no gun thx

//Crosshair
seta cg_crosshairHealth "0" - Has to be 0 , or crosshaircolors won't show. 	
seta cg_drawCrosshair "3" - the dot with the sircle, why? so I don't actually have to watch it to aim fast
seta cg_crosshairSize "42" - so the crosshair is just small enough that I got a clear black sircle around it
seta cg_crosshairAlpha "0.9" - make it a bit more transparent, makes the outer sircle less visible, not covering up details
seta cg_crosshairAlphaAlt "1.0" - the transpearacy of the dot (default)
seta cg_crosshairColor "0xA0FFC0" - color of the outer sircle (Hex value, can be used to specify any custom color)
seta cg_crosshairColorAlt "red" - color of the dot

I change between these two (long/close) according to the distance of the enemy.
On long distance I get smaller crosshair, other color, lower sens, lower fov.
So the enemy looks bigger, and is easier to hit. Making it possible to give headshots, on
rather far distances. Also makes it possible to take out snipers far away.

Ok, over to hardware settings, look in the "hardware" folder.

(c) [<<]RaZiel - 28/11-2003
