Add the following to your console!!
seta cg_drawFPS "1"
seta cg_drawLagometer "1"
seta cl_maxpackets "100"
seta com_hunkMegs "512" - or half your RAM
seta com_maxfps "125" - set to "333" for high end cards
seta rate "25000"
seta snaps "30"
The first two are for seeing your FPS and the lagometer. Use them if you like.
HunkMegs ( the amount of memory COD2 is allowed to use.
The game automatically caps the fps at 91. This will try to push it to 125.
For a more advanced approach!!
You will need to either uninstall the game or clean out your cod2 folder and delete the "players" file as well..
Autoexec.cfg
Create a new text file in your Program FilesActivisionCall of Duty 2main directory, and rename it to autoexec.cfg (not autoexec.cfg.txt). Now you can add custom commands and key bindings to this file, and they will not be overwritten or altered by the game engine. However, unlike most games using .cfg files, Call of Duty 2 doesn't automatically run the autoexec.cfg file, regardless of where it is placed in the COD 2 directory structure. So to have it run automatically each time you launch COD 2, you must place it in the directory above, and you will need to add "+exec autoexec.cfg" (without quotes) to your relevant COD 2's launch icon Target box (See Command Line/Target Box below). This works for either multiplayer or singleplayer. In fact you may want to have separate autoexec_sp.cfg and autoexec_mp.cfg files, and execute the relevant one when launching single-player or multi-player.
Note that some of the commands you add to autoexec.cfg will be added to the main config.cfg/config_mp.cfg file by the game when it executes them. If you want to undo any of your custom commands, just removing them from autoexec.cfg may not work. You might have to manually reset the setting to its original or default value in the game console. To see any command's default value, just type the name of the command in the console without anything else and its current and default values will be shown.
Command Line/Target Box
Another place to enter command is in your Call of Duty 2 launch icon's Target box. You can access this by going to the desktop icon you use to launch COD2, right-clicking on it and selecting Properties, then in the properties box which opens, look at the 'Target' box. You should see something like this (the value shown below is for launching singleplayer COD2):
"C:Program FilesActivisionCall of Duty 2CoD2SP_s.exe"
Your path may vary, depending on where you installed the game - that's fine, don't edit the path text inside the quotes; add commands at the end of this line to force Call of Duty 2 to do various things at launch. All you need to do is insert a space to separate each command, and insert the words +set in front of the command. For example, to skip the startup movies (com_introplayed 1) and automatically execute a custom .cfg file (exec autoexec.cfg) the target box should look similar to this:
"C:Program FilesActivisionCall of Duty 2CoD2SP_s.exe" +set com_introplayed 1 +exec autoexec.cfg
Note that the first command lies outside the quote marks ("") and is one space away from the last " mark. For each additional command, make sure there is a single space between it and the previous character in the box. Most commands can be inserted into the Target box in this way, however this is best used for options which need to be implemented at launch time for the game, such as removing the intro movie, setting memory sizes, altering resolutions, etc. Also keep in mind that if you want to apply custom tweaks to COD 2 multiplayer, you need to do the same thing for the COD 2 Multiplayer launch icon.
/COM_maxfps and /CL_maxpackets
You may actually find how the whole fps thing works quite interesting actually. Because the Quake 3 engine, which CoD2 uses, bases its timings from your fps, certain rounding errors cause weird effects.
When you run on com_maxfps 125, and have your cl_maxpackets set at 60, the rounding causes your actual cl_maxpackets to be at 41.67. When you set it to 100, your actual cl_maxpackets is then 62.5
When you run on com_maxfps 250/333, and have your cl_maxpackets set at 60, the rounding causes your actual cl_maxpackets to be at 50. When you set it to 100, your actual cl_maxpackets is then 83.34
So basically, higher fps 'magic values' will result in your computer sending more packets per second.
Other effects are 250/333 give you faster shooting with nearly every mg, or gerand. 333 fps will reduce your recoil as well. 125 and 250 are the same in jump height, 333 gives you even higher jumps. 333 fps will give you an appeared ping of 48, even at lan.
If you want a setting to "stick", even without your custom config file being run again, I recommend using the seta command in front of the command (e.g. seta r_glow 0). This makes the change permanent by inserting into your main config.cfg (or config_mp.cfg) file.
r_autopriority [0,1] - I'm not certain what this option does, it may prioritize objects in the z buffer. Regardless, when set to 1 (enabled) it seems to provide slightly better performance without a noticeable drop in image quality.
r_drawSun [0,1] - If set to 0, disables the sun effect in the sky - the sun disappears. This can improve performance slightly, and also removes the 'sunblind' effect when starting at the sky.
r_gpuSync [0,1,2,3] - This setting determines the synchronization of the GPU (graphics processing unit) and CPU. The values for the various modes are 0 for Off, 1 for Beginning, 2 for beforePresent, and 3 for Adaptive. Importantly, this setting currently defaults to 3 for all users which is a conscious decision by Infinity Ward to balance performance and responsiveness. This is because if set to 0, you may gain performance however your control input (keyboard and/or mouse input) may become laggy as the CPU and GPU go slightly out of sync in places (See Conclusion section). If you are desperate for extra FPS, set this to 0, however if you notice mouse/keyboard lag even at 30+ FPS, then reset to the default value 3 (Adaptive) which keeps the CPU and GPU in sync.
sys_SSE [0,1] - Should be set to 1 on all systems as it enables COD 2's SSE Extension support on SSE CPUs (both Intel and AMD support SSE), which increases performance. Just check this to make sure it is set to 1, and if not set it to 1 for optimal performance.
com_hunkMegs [80 - 512] - Determines the amount of memory (in MB) to allocate to the game to help smooth out in-game loading. You should not allocate any more than half your system RAM to this option (i.e. if you have 1GB of RAM, set this cvar to 512).
r_aasamples [1-4] Determines the level of Antialiasing (AA) applied in the game.
You can set this using the Anti-Aliasing option in the in-game settings. Note
that a value of 1 turns AA Off.
r_anisotropy [0-16] - If Anisotropic Filtering is enabled in the in-game
settings, this cvar sets the level of Anisotropic Filtering used. The default is
8x, however you can set a value between 1x and 16x, with the higher the sample
rate, the better texture quality but the lower your performance. Anisotropy can
have a significant impact on performance on certain systems.
r_aaAlpha [0,1,2] - This setting determines the type of alpha blending used for
antialiasing (if AA is enabled). 0 is off, which gives the best performance, 1
is dither mode which is the default, and 2 is Supersampling which provides
better image quality but reduces performance.
You'll need to enter an UNMODDED server , make sure your settings are the way you want them..then go into whatever server you'd like ( most mods will then copy theses settings".
If any of you have questions or need help...just ask us.
Copyright © by Shock'N'Awe All Right Reserved.
