This is why we came up with the yitchX configs. They are meant to be used by folks with crappy computers so that they can keep up with all the sleek, speedy new systems on the cutting edge of online play.
The client-side configuration file is found in your player folder:
e.g.
C:Program FilesActivisionCall of Duty 4 - Modern WarfareplayersprofilesJockYitch
it is named: config_mp.cfg.
yitch3 can be used, with some slight modifications, in lieu of this config file.
Summary
The yitch3 config file was tested on a P4 single core, 2Gb RAM, running a 7900 nVidia card with 512Mb onboard running 169.21_forceware_winxp_32bit_english_whql.exe.
The FPS rates shown in this article are STATIC rates, with no one in the server. Your rates will undoubtedly vary from the results we have achieved. Our numbers are simply for comparison.
Note that we were running a different Forceware driver set than was used when we came up with yitch2. For that reason, the yitch2 frame rate is lower than that reported in the original yitch2 article. The absolute FPS is not that important - we are just looking for relative improvement over stock. Either way, yitch3 yields an FPS almost a factor of 4 higher than stock.
One of the biggest complaints with the yitch1 and 2 configs was that PunkBuster would kick you if your config was outside the bounds set by the server admins. In yitch2, you could get kicked from a server (NOT banned ...just kicked temporarily), if say, your picmip setting was 3 (low res), or for setting lodscale to a low res setting.
What we have done in yitch3 is to add binds to allow you to modify your settings on the fly so that you will not get kicked.
Here are some of those binds. The function keys in yitch3 act as 'toggles'. If you keep pressing the function key associated with the bind the next value written in the line is used.
e.g. hit F4 and your m_pitch will be 0.044. Hit it again and it will be 0.033 and so on. Note that as in the case for F4, when you hit the key an error message shows up saying 'Unknown Command <m_pitch'. This is done on purpose. It is a feedback message to you saying you hit the m_pitch key. No one else in the server will see this message: just you.
bind F1 'toggle cg_fov 65 80'
- toggles the Field of View. yitch3 comes with a 65 deg FOV to minimize FPS hit.
bind F2 'toggle r_gamma 1.2 1.4 1.6 1.8 2.0 2.2'
- allows you to adjust your brightness
bind F3 'toggle sensitivity 4.0 4.5 4.7 5.2 5.5 5.7'
- allows you to modify your mouse sensitivity
bind F4 'toggle m_pitch 0.044 0.033 0.022 0.015;<m_pitch'
- allows you to asymmetrically modify your mouse sensitivity in the vertical
bind F5 'toggle m_yaw 0.032 0.026 0.022 0.018;<m_yaw'
- modify the mouse sensitivity in the horizontal
bind F6 'toggle r_picmip 2 1 0 3; r_applypicmip; <picmip'
- Sets texture sizes. Equivalent to in-game menu 'Texture'. This is scaled according to hardware support. For the maximum 'texture' set to 0, lowest (ie fastest rendering) is 3. Note that bind automatically executes r_applypicmip which is needed for you to actually see the difference on screen.
bind F7 'toggle r_lodscalerigid 3 2 1 4; <lodsr'
- Level of detail for static objects (1=best to 4=worst). Usually '1' is required in competition.
bind F8 'toggle r_lodscaleskinned 3 2 1 4;<lodss'
- Level of detail for skinned objects (-1000=better to 0=lowest)
bind F9 'toggle r_detail 0 1;<det'
- Detailed Shaders (0=none 1=Activated). Draws 'detail', or pixel shader. Set to '0', scene looks more like CoD2 and will turn cammo off the guns. Set to '1' for cammo skins. This bind was added in response to the huge number of folks that were miffed that yitch2 made them lose their gun cammo skins. Get them back by toggling this bind.
bind F10 'toggle cg_marks 1 0';<cgmarks'
- Show bullet holes when set to 1. No bullet holes, set to 0.
bind KP_UPARROW 'com_maxfps 76; cl_maxpackets 39'
- Sweet spot setting used to optimize server connection. FPS is capped here at 76. For those that can only achieve a constant 76 fps rate, use this setting.
bind KP_PGUP 'exec stock.cfg; //r_applypicmip; <stock'
- copy your stock config_mp.cfg file into stock.cfg and place this file in your:
C:Program FilesActivisionCall of Duty 4 - Modern Warfaremain
folder. Now, you can run your stock config file by typing PGUP on the keypad.
*NOTE. You will notice that r_applypicmip has been commented out of this command as it is preceded by two slashes '//'. Why? Well, we are being a bit sly here. On some servers you will be booted if you do not run picmip 1 or 2. However, you can select picmip 1 or 2 on the fly, but by not running r_applypicmip, you technically can stay in mode 3 (low detail). Yes...I know...we'll burn in hell for this one.
bind KP_LEFTARROW 'r_lodscalerigid 4; r_lodscaleskinned 4; r_picmip 3; //r_applypicmip; <lod4pic3'
- select lowest detail. This is the standard setting for yitch3.
bind KP_END 'r_lodscalerigid 1; r_lodscaleskinned 1; r_picmip 0; //r_applypicmip; <lod1pic0'
- select highest detail.
bind KP_DOWNARROW 'r_lodscalerigid 2; r_lodscaleskinned 2; r_picmip 1; //r_applypicmip; <lod2pic1'
- select high detail
bind KP_PGDN 'r_lodscalerigid 3; r_lodscaleskinned 3; r_picmip 2; //r_applypicmip; <lod3pic2'
- select moderate detail
/exec yitch3.cfg
/vid_restart or /r_applypicmip
The best way to run this file is to insert it into your config_mp.cfg file.
These config files are a community effort. The thank you's start with dk05 from IW. We then go to the forum-goers at GotFrag.com (especially scot). Finally, we ask for a standing ovation to the great forum posters of BASHandSlash.com: Doctor of Quake engine configurations [DA]Flash, puller, FoX and Volatile. Thank you guys, and anyone else I may have missed, for providing the insight into this configuration file.