FuhQuake General FAQ
Make sure there is no opengl32.dll in your quake folder!
Turning on fullbright skins is easy. Just use "r_fullbrightskins 1" to turn them on. If this is too bright for you then you can try "r_fullbrightskins 0.3" etc for 30% fullbright skins.
You set your enemyskin and teamskin with the "enemyskin" and "teamskin" variables. If you have a skin called red.pcx you wish to use for teammates and white.pcx you wish to use for enemies, then put the two pcx files in qw/skins and use "teamskin red" and "enemyskin white".
You can also use powerup skin forcing by setting the variables "teamquadskin", "teampentskin", "teambothskin" (for pent+quad) and simarly for "enemyquadskin", "enemypentskin" and "enemybothskin".
To disable skin forcing just reset the appropriate variable to "" (or just use "cvar_reset teamskin" etc).
FuhQuake can also do colour forcing. Use "teamcolor x y" to set team topcolor to x and team bottomcolor to y. Use "enemyskincolor" for enemy colour forcing. "teamcolor off" and "enemycolor off" disable colour forcing.
You can download some sample skins for skin forcing over here. Instructions are included inside the zip.
Yes, "impulse 7 5 3 2" will first try to change your weapon to the rl, then the sng, then the ssg and finally the sg. Make sure you put spaces between the numbers!
In FuhQuake GL Version 0.26 Build 300 and earlier font smoothing is enabled by default and can be disabled with "+set gl_smoothfont 0" on the command line.
In FuhQuake GL Version 0.26 Builds 330 and 335 font smoothing is disabled by default and can only be enabled with -smoothfont on the command line.
In FuhQuake GL Version 0.27 (any build) and above font smoothing is disabled by default and can be turned on with 'gl_smoothfont 1'. 'gl_smoothfont 0' will turn font smoothing off. You can use the gl_smoothfont variable on the commandline, by typing it in console or by putting it in your configs.
In GL FuhQuake, use "+set vid_displayfrequency x" on the command line to set your refresh rate to x Hz (your drivers must support that refresh rate).
If you play software FuhQuake with -dibonly, then the command "vid_modelist" should display a list of possible resolutions and refresh rates like "#5 [email protected]" which means 320x200 resolution with 75Hz refresh rate. You can switch video modes with "vid_mode x" where x corresponds to the entry number given by "vid_modelist". Some people however may not have refresh rates listed in their 'vid_modelist' even though they are using -dibonly with software FuhQuake. These people can still set their refresh rate by using "+set vid_displayfrequency x" in the same way as GL (read above).
In short you use "cfg_save config_name" to save all your configuration settings and then "cfg_load config_name" to reload them at a later date. Of course you can change config_name to something more meaningful.
FuhQuake has a very customisable config manager which you can and should read about over here.
Put locs in qw/locs or id1/locs (if you play teamfortress you'll probably want to put them in fortress/locs). Set "tp_loadlocs 1" to load them automatically (this is default). If you don't want them loaded automatically then you can use the "loadloc" command to load them in game ("loadloc dm4" to load dm4.loc etc).
Set "cl_keypad 1" firstly and then bind things to "KP_0, KP_1, KP_2, ... , KP_9" or to "KP_DOT, KP_DEL, KP_ENTER, KP_PLUS, KP_MINUS, KP_STAR, KP_SLASH". You can also use alternative names for the keypad numbers like "KP_UPARROW" instead of "KP_8" and "KP_INS" for "KP_0".
In software FuhQuake use "v_quadcshift 0" to disable quad screen blending and simarly for v_pentcshift, v_ringcshift and v_suitcshift. "v_contentblend 0" will disable screen blending when under water (or slime etc).
In GL FuhQuake you can disable all screen blending in one go with "gl_polyblend 0". However you may want to set "gl_polyblend 1" and customise which blends are disabled using v_quadcshift, v_pentcshift, v_ringcshift, v_suitcshift and v_contentblend. In GL there is another variabled called v_dlightcshift which can be used to disable screen blending when inside a "gl_flashblend 1" type bubble.
Note that these variables are more than just 0/1 variables. For example "v_quadcshift 0.3" will still use quad screen blending, but only by 30% as much as "v_quadcshift 1".
Set "cl_staticSounds 0" and "s_ambientlevel 0" to disable ambient/static sounds.
You bind things to MWHEELUP and MWHEELDOWN to use the mosuewheel. In win32 clients, if you're mouse wheel isn't working with the -dinput command line parameter, then "m_forcewheel 1" should fix it.
You can get the mouse wheel working in linux x11 and glx clients too. Read linux.txt for more info on this.
Yes, firstly set your rate to as much as your limited bandwidth can handle, and cl_maxfps to 72 or however much fps you want. Then set "cl_c2spps 30" to turn on netlimit ("cl_c2spps 0" turns it off). You can try increasing "cl_c2spps 30" to "cl_c2spps 35" and even higher, but at some point you will start getting a lot of PL.
Basically the way it works is "cl_maxfps x" gives you x fps but "cl_c2spps y" limits your net connection to only receive as much data as you'd receive with y fps (actually this isn't totally correct but it will do).
Basically this happens because you are using the GL client and your computer can't load the 24bit textures from your hard drive fast enough. It mostly happens when connecting to old quakeworld servers playing maps that have lots of large 24bit textures (eg dm3 on small.edome) . You can fix this by i) playing on servers running zquake >= v0.12 or mvdsv, or ii) not using 24bit textures (-no24bit on command line) or iii) rescaling all the 24bit textures for problematic maps to half their size (so 512x512 images are converted to 256x256). The third option will make the textures only 1/4 of the size on your hard disk and so they will load 4 times faster.
Quakeworld has always been restricted to 72fps, unless the server specifically allows a higher fps. This is because higher fps changes the gameplay, it makes you jump further etc. Servers however can allow people playing on them to use more fps. The "serverinfo maxfps 120" command for example will allow 120 fps. If you are playing on FuhQuake's inbuilt server (eg single player), typing "serverinfo maxfps x" will let you use up to x fps (so use 999 for unlimited etc). Of course if you have vsync on then you can't get more fps than your refresh rate no matter what. You can turn off vsync possibely in your drievr properties or with "vid_vsync 0".