CoD2 Performance Tweaks

[~N3U~AŽ†3ck™]

Every thing you need to know about performance tweaks for CoD2.
Had this in the forums already but I'll re add and go into more detail.

Chapter 1

Optimizing CoD2

Just like every other game you may play, there are certain commands that you can enable/disable that allow you registration to be better than the out-of-the-box defaults. Most of these commands follow suit to the quake series, since the game itself was built on the quake 3 engine. In my personal experience, I have seen so many players using the wrong settings in their config. This is mostly due to a trend that was created by someone who did not know what they were talking about. So I am going to lay it out to you straight, with an explanation of the intervals, and why some figures are good and bad.

Console Settings

First off lets show your fps

"cg_drawfps 1" - Displays your FPS (Frames Per Second) in the upper right hand corner. The higher your FPS the smoother the game runs, the lower your FPS the choppier the game runs.
In simple mode (1) shows the average and current (low and high) FPS. In Verbose mode (2), additionally shows vertex counts. In Time mode (3) shows the time taken to draw the current frame in milliseconds (ms). Setting it to 0 turns it off.

"com_maxfps" - This command puts a cap at your fps. Another words if you are fluctuating between frame rates of let's say 40- 75 fps. You want to max it at the bottom end which would be 40. Or you hitting
100-150 fps. You want to max it at 100 fps. What happens is that your games speeds up and slows down which in return makes your shots off. As you are tweaking your system raise the max a lil
higher, lets say you have it maxed at 40fps. Set it at 50 fps and tweak your system to see if you could get it at 50 fps or close to it.

"cg_drawlagometer 1" - This is a very useful utility which lets you monitor your connection on-line. With this enabled while you are playing on-line you will see 2 bouncing lines.
The first line displays the conjunction between your graphics card updating the frames in sync with the gameworld updates recieved from the server. Idealy, this should be a straight blue line. If it has bouncing yellow spikes then your display will stutter and be more difficult to view. To combat this, first ensure you have followed my tweaking techniques and then change your snaps setting. Usually, this means lowering it by until your screen is stable and you have a nice flowing blue line in your lagometer.

The second line shows if packets are being recieved from the server. This should be green. If it is yellow or red, try increasing your rate or try lowering your snaps. If this does not help, you may be on a bad server so try another. The height of the line is dependent on your current ping.

"cg_brass" [0,1] - If set to 0, disables all ejecting brass, such as expended shells from your gun. This can improve FPS slightly when firing your weapon.

"cg_marks" [0,1] - If set to 0, disables all marks made by weapons, explosions etc - such as bullet impact marks and charring on the ground. This can improve performance in heavy combat scenes. If set to 1, you can set the maximum number of marks shown with the cg_markslimit command.

"cl_mouseAccel" [0 - 100] - If set to 1 or higher, accelerates your mouse movements. This is a non-linear setting; that is, unlike what you have experienced, the mouse speed will be more responsive with very rapid mouse movements. If you move it slowly you won't notice any difference to your current un-accelerated settings. However, in a tight turning shoot'em up, you'll notice that you'll be able to rotate around much faster.

This will be hard for you to get used to. Most players set acceleration off because they can't develop a feel for it. Try it out for a few days. Most of the time - you will not notice any change whatsoever; however, you'll soon see the benefits of the high rate of movement when you are duking it out with someone in the tight confines of an alley or room or someone suddenly appears right in front of you and you need to whip your gun around to face them. The higher the value used, the quicker your movements will accelerate your mouse. This can make aiming difficult, so set to 0 if you want to disable this option.

"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_drawDecals" [0,1] - If set to 0, disables all decals - that is, marks on the wall from gunfire, explosions, etc. Similar to the cg_marks command.

"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_drawWater" [0,1] - (cheat) If set to 0, disables water effects. This improves performance in areas with water.

"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.

"sv_framerate_smoothing" [0,1] - If set to 1 this option should keep framerates smooth, however you can experiment to see if disabling it improves performance or overall framerate. I saw no difference on my system either way.

"Rate 25000" ? This command is standard and doesn?t require much of an explanation as to why it is what it is, since it is practically the rate for any game currently played.

"Snaps 20" ? This command is tied in direct relation to the sv_fps command, which is locked at 20 in cod2. The reason the interval allows you to extend to 30 snaps is because CoD1 used sv_fps 30, which increases the fps of the server, which equates to better registration, however since CoD2 has a flaw in the game that does not allow the server to be set to sv_fps 30, we are forced to stick to 20, which is what your snaps should be. If your snaps are set to 30, then it does not matter because the game will simply just recognize it as 20. Your snaps setting determines how many updates you recieve from the server. 56K modems should have a setting of around 20. ISDN modems (128K) should be around 40 as should any other fast connection devices (LAN, T1 etc....). Remember to read my cg_lagometer section for tips on "snaps

"cl_maxpackets" 100 ? This command is probably one of the most important commands, and it is important to set it right. The interval for this command is 30-100, and the higher number you select, the higher your ping will be visually to the server. The most important thing that you need to find out, is if your Internet is good or not, meaning if you have any choke/loss when you send packets to the server. The way you can check this is directly through CoD2, by using the command cg_drawlagometer 1. The blue line with the yellow dots symbolizes your packets and the less yellow that appears, the better off you are. If you do not have much loss/choke, then I highly suggest using cl_maxpackets 100, however if your Internet is very poor then you should use cl_maxpackets 30. This setting puts a limit on the maximum amount of packets that can be sent to the server via the client. This setting is useful for people with slower modems. The default setting is 30 (comparable to a 56K modem), but lower this if you have a 33.6K modem or less, and higher this setting if you have an ISDN or higher modem.

"cl_packetdup" 0 ? As the name suggests, this setting is used to send multiple packets to compensate for lost packet drops. This setting should be set at 1 unless you have a VERY good connection in which case set this to 0.This command has an interval of 0-5, and basically what it does is increase the amount of packets you send to the server from your anticipation of how much loss you have. Now with me personally, I use Comcast, Internet, so my connection is near flawless. I do not need to send more packets than necessary, because all of my packets go through on the first try. A lot of people do not know what this command does, and I hope this can shed some light on that situation. Use the lagometer to decide on which setting to use. So if you set to 0 you send 1 packet, if you set to 1 you send 2 packets, set to 2 you send 3 packets, etc....

"com_hunkmegs" 512 ? This command is basically equivalent to half the amount of ram you have inside of your computer. From my knowledge of this command, I can make the conclusion that it has something to do with the amount of ram CoD2 puts aside to use, which in turn increases your FPS by about +20. The max is 512 megs, so if you have 1 gig of ram or better set it to 512.

"r_multigpu" 1 ? This command only works for computers with dual SLI, and apparently increases the performance of your game. This should also work if your running crossfire.


Level of Detail Scaling
"r_lodscale" - Default: 1 Range: 1-4

The Call of Duty 2 rendering engine tried to support a wide range of video cards, including lower-end video cards. The rendering engine has built-in commands for dumbing-down the geometry and reducing the number of polygons for models for older, slower video cards. The problem is, they didn't restrict that feature from people with faster video cards. By simplifying the geometry, there is a further frame-rate boost gained and geometry is simplified. Moving objects are even easier to spot and bushes and vegetation are thinner, visibility through the bushes improves, and the bushes completely disappear from rendering at a much closer range. This tweak is especially beneficial (and noticeable) when snap-shooting on the bush-heavy Brecourt level. There is also a disadvantage associated with this: grenades are not rendered until they are closer to you.

Some of the newest commands to hit the shelf that are allowed on some competitive servers are:

"r_polygonoffsetbias" 16 - Default: -1 Range: -16 to 16 This tweak helps increase enemy visibility.

By cranking up the r_polygonOffsetBias we end up with cleaner textures and it becomes easier to spot an enemy. Enemies visually stand out more when they are in front of smoother textures. By increasing this value game graphics become simpler; they don't look as pretty, but they render faster (higher frame-rates), and make it easier to see your enemy.

Cranking up the the r_polygonOffsetBias all the way to 16 simplifies a lot textures. Textures look "cleaner" as if all the dirt and smudges and bullet marks were cleaned off them.

Some wall overlay textures disappear entirely. For example, many of the buildings in the French levels have signs on them that say Pharmacy or Hotel, but those textures are removed with r_polygonOffsetBias values of 4 or larger.

Bullet marks from your gun also disappear with r_polygonOffsetBias values of 4 or larger. Emptying your clip into the wall no longer leaves markes on the wall. SUCH A CLEAN WALL!

r_polygonOffsetBias values greater than zero (1 or higher) disable texture blending / smoothing between different types of ground. What used to previously be smooth transitions between different texture types (such as grass meets dirt) now become abrupt hard edges. This further contributes making the textures appear clean.

"r_polygonoffsetscale" 4 - Default: -1 Range: -4 to 4 Determines the rate at which the LOD Bias value comes into effect. That is, models closer to you will lose more details more quickly the higher the lodscale value. With it's default settings, it helps smooth and blend adjacent texture types, and helps improve the visual stability of angled geometry in the distance.

By cranking the r_polygonOffsetScale up to 4, there is a slight frame-rate increase that is gained (less than 10 frames per second by my testing). Visually, the game becomes even simpler.

The most obvious impact of increasing this is that many areas that used to be covered in dirt now appear to be made of rock. Much of angled hills in Egypt appear to be made out of solid rock now.

Another obvious issue is the stability of angled geometry. As your viewing angle of a triangle changes, the texture may abruptly flip between two types. This texture changing can be somewhat visually distracting, but helpful if you're tweaking for maximum frame-rate.

A less subtle impact of cranking this up is that textures have much more abrupt edges and less variation in light levels.

Snow especially becomes cleaner. Less rock and debris in the snow makes for smoother textures and better snow visability.


These two commands simplify the textures on the walls so that they are more vibrant and less overdone. Many occasions I find myself over-looking an opponent simply because I cannot make out his brown helmet against a brown wall, and these two commands fix that problem for me.

Options Settings

When you open up the normal options graphics menu there are multiple settings you need to configure. The first and foremost is the resolution you choose to run your game at, which should be the resolution you get the higher Hz with (my monitor is 60 Hz, and I use 1920x108). Set your Aspect Ratio to what type of screen you got which is standard,16:9 or 16:10 and your Texture Filter to ?Bilinear.? You Anti-Aliasing can be anywhere from ?off ? 4x.? Anything above 4x will be noticed drastically through your FPS (which can be seen by typing cg_drawfps ?1?.
Turn ?off? sync every frame and Optimize for SLI, since they reduce your FPS. Put Soften Smoke Edges to ?Everything,? for reasons I do not know, just my preference. Now you should be ready to frag without registration issues or laggy frame problems (unless your computer is utter trash). Good luck and most of all, have fun.

High Frame Rates

By default, the maximum frame rate is capped at 85 (or sometimes 90) frames per second by the default settings.

The default cap can be overridden in the client allowing them to achieve rates faster than 90.

Higher frame rates offer many benefits.

Fluidity (High Frame Rates)

The most obvious benefit is that the game will play more smoothly. When the rendering is fast, its much easier to take aim on a target.

Speed (High Frame Rates)

One unintuitive benefit of higher rates - is that you seem to be able to run slightly faster. Increase in speed is huge benefit, especially when you get good at jumping, dodging, and wiggling to avoid fire. Also makes it easier to run CTF flags.

Glitching (High Frame Rates)

This slight increase in speed enables the player to jump moderately farther and slightly higher than they could before. This allows jumping to places that cannot be reached by people with lower frame rates.

Kevlar? (High Frame Rates)

Completely unsubstantiated theory of mine, but I suspect that higher frame-rates somehow translate into less player damage. With high frame rates I seem to be able to survive sniper / rifle fire that kills most people. Some people ♥♥♥♥♥ about 'Kevlar', and I suspect that Kevlar syndrome is caused by higher frame rates and or low ping. -- Completely unsubstantiated theory of mine - I don't have a way to test it with any precision.


Unfair Tweaks

Light Tweak Ambient
r_lightTweakAmbient 4

Tweaks (artificially increases) the ambient lighting of game models (players, trucks, tanks, etc.)

This tweak is extremely unfair as it can make players glow-in-the-dark. This also makes player colors much more vibrant and easy to see through bushes and vegetation.

Think of the house in Burgundy with the staircase that is very dark at the top. Now imagine a player at the top of that dark staircase lit up as bright as if he was outside. That's how unfair this is.

This tweak was deemed so unfair by Activision, that in recent versions of CoD2 (1.3) this setting is now cheat protected (can only be changed if cheats are enabled)

This value is reset every map. Each time a new map loads, it sets the default value for that map.


There are so many more tweaks that you can do. This is a good start. I will add more on here as another reply other wise you could get lost on here as your trying to tweak your system.

[~N3U~AŽ†3ck™]

Chapter 2

Call of Duty 2 FPS Boost

In what happens to be an excellent (and now well-known) discovery, myshkinbob over at the NVNews Forums discovered two important facts regarding Call of Duty 2's performance under DX9. Read his thread for the full story, but basically his discovery centers around two important settings in Call of Duty 2:

# There appears to be a fault of some kind with the way the engine applies the texture settings (the r_picmip-based commands). Thus, each time a new map loads up, you can get a noticeable performance boost if you change the r_picmip value from its current value, use the r_applypicmip command, and then reset the r_picmip setting back to its desired value and again use r_applypicmip. This must be done every time a new map loads up, and myshkinbob has created a set of files you can use to do this - see his thread for details.

# There is a problem with the r_gpusync command, which should be set to 0 for single card graphics users, however it instead defaults to 3 for all users. Setting this command back to 0 should provide another performance boost for single-card graphics users (SLI users should leave it at 3). You can simply add "+seta r_gpusync 0" (without quotes) to your startup icon(s) if you want to quickly apply this fix, or insert it into your autoexec.cfg file.

Now that these issues have been identified, it should be relatively straightforward for Infinity Ward to address them in an upcoming patch. They are just a case of incorrect settings being applied at initialization of the graphics engine, and not a major bug in the course of things. However appreciation goes to myshkinbob for picking these up and letting everyone know about them, as the performance boost from these two changes can make a real difference on most peoples' machines.

Basically the game's developers are aware of the additional FPS possible when r_gpusync is disabled (set to 0), however because this setting controls the synchronization of the CPU and GPU (your graphics card(s)), disabling this can also introduce input (mouse/keyboard) lag. This is because your input can at times be processed by the CPU faster than it can be drawn on screen. So on balance they chose the default of r_gpusync = 3 to maintain synchronization while still giving good performance. The same situation (input lag) can occur if the 'Optimize for SLI' or r_multigpu setting is enabled.

Update 2: The r_picmip issue discussed above has been resolved as of the 1.2 Patch, and there is no longer any need to use the manual method to fix this issue.

Call of Duty 2 and Dual Core CPUs

As of the 1.01 Patch, Call of Duty 2 should take better advantage of Dual Core/HyperThreading systems with some performance improvements. Furthermore, this patch should also fix any issues on such systems, so it is a must-install for Dual Core/HT owners.

sys_gpu - Shows your current Graphics Processing Unit (GPU) or more commonly know as the graphics card.
Just on a Note this does not mean you activate Grandpa (AIA|GPU). So this does not mean that this will put a picture in the game of Grandpa.

cl_maxPackets and com_maxFPS



This is where your graphical framerate affects your connection.
The actual number of packets you can send to a server is either one every frame, or one every 2 frames, or one every three frames and so on.
So if you are running at 125fps, your possible packets per second are:



125/1 = 125

125/2 = ~63

125/3 = ~42

125/4 = ~32




So if you are using maxPackets 100 at 125fps, you are NOT sending 100 packets per second, you will send one packet every 2 frames, which is 62.5 packets per second.
And if your framerate drops to 100fps, then suddenly you will be able to send one per frame, and will get a jump from 62.5 to 100 packets per second.



100/1 = 100

100/2 = 50

100/3 = ~34




So if you have your cl_maxPackets set to 100 and are using 125fps then mostly you will be sending 62.5 packets per second to the server
(this is the largest achieveable value not exceeding the input cl_maxPackets limit).
However, if the framerate drops to 100fps, you will be sending 100 packets per second, as this is now the largest achieveable value that does not exceed the input cl_maxPackets limit.
If your connection cannot handle 100 packets per second, it will cause your ping to rise or spike.
Even if it can handle the jump from 63 to 100 packets, this may well cause your latency to fluctuate more than if your actual packets per second were constant.
Keep this in mind when choosing a value of cl_maxPackets for your connection. This information is only needed if you have a slow upstream and cannot use the maximum value of 125.

[~N3U~AŽ†3ck™]

Chapter 3
Setting up your system.

Command Console

Call of Duty 2 allows us to get into some advanced tweaking, because the game's command console is easily accessible, and a wide range of commands can be brought up and used to further refine the game. To access the console, under the Options screen go to Game Settings and make sure the 'Enable Console' setting is set to Yes. Now you can access the console at any time by pressing the '~' key (the key above ESC) to open and close it. To get the expanded console, press the SHIFT key and ~ key together (SHIFT+~). The expanded console is particularly useful for seeing the output of your commands, system warnings, errors, etc.

The console is the main place to input a range of Development Variables (dvars) as well as Commands, which do everything from change the way certain objects behave in the game, through to controlling all aspects of the game's graphics, audio and control settings. Note that although technically there is a difference between a command and a dvar, I generally refer to all of these as 'commands' in this guide for the sake of convenience. See the Commands section on the next page to see a list of useful commands along with descriptions of their functionality. If you simply type the first few characters of a command into the console, it will provide you with a list to choose from. For example, type "cg_" (without quotes) into the console and all the commands starting with cg_ will be shown. Typing further characters of a command's name will provide you with the full command and its current and default settings. Note that the default settings will differ on various systems depending on your hardware.

Multiplayer Note: To use console commands during multiplayer, you must place a "/" (without quotes) in front of the command. For example, the command cg_drawfps must be typed as /cg_drawfps to work in multiplayer, otherwise any text you type into the console will simply be shown as chat text on the screen and not implemented.

Now my sweet spot I have:
150 fps
140 maxpacket
This is my config:
// Generated by N3U|@zt3ck, do not modify

bind TAB "+scores"
bind ESCAPE "togglemenu"
bind SPACE "+gostand"
bind ' "say ^1xfire ^9= ^2aztecknight"
bind , "SAY ^1ARMOR [ON]"
bind - "say ^1NI^9C^2E"
bind . "SAY ^1ARMOR ^0[OFF]"
bind 0 "say ^1 you got KNOCKED the FLUFF OUT"
bind 6 "exec azteck.cfg"
bind 7 "SAY ^1TAG ^9UR ^2IT"
bind 9 "SAY ^1T^9H^2X"
bind = "SAY ^1CRACKED ^9YOUR ^2 DOME"
bind [ "name ^^00A1A^^99|^^11@zt3ck"
bind ] "name ^^11F^^00@^^11ng^^003"
bind ` "toggleconsole"
bind A "+moveleft"
bind B "+binoculars"
bind C "gocrouch"
bind D "+moveright"
bind E "+leanright; toggleads; +holdbreath"
bind F "+activate"
bind I "say ^2I PWN SO HARD, ^1IT HURTS"
bind L "SAY ^1--->^9LOL^2<---"
bind O "say ^2Awwww I think you need my ^1Anti-T Bag perk"
bind P "name ^^00N3U^^11|^^99@zt3ck"
bind Q "+leanleft; toggleads"
bind R "+reload"
bind S "+back"
bind T "chatmodepublic"
bind U "say ^4Whoopsi-Daisy Whoopsi-Daisy call m3 Cr@zy"
bind V "mp_QuickMessage"
bind W "+forward"
bind X "goprone"
bind Y "chatmodeteam"
bind Z "+talk"
bind ~ "toggleconsole"
bind PAUSE "toggle cl_paused"
bind CTRL "+melee_breath"
bind SHIFT "+melee_breath"
bind F1 "vote yes"
bind F2 "vote no"
bind F4 "+scores"
bind F12 "screenshotJPEG"
bind MOUSE1 "+attack"
bind MOUSE2 "toggleads"
bind MOUSE4 "+frag"
bind MWHEELDOWN "weapnext"
bind MWHEELUP "weapnext"

seta ai_corpseCount "10"

seta cg_blood "1"

seta cg_brass "1"

seta cg_centerPrintY "-60"

seta cg_chatHeight "8"

seta cg_chatTime "12000"

seta cg_connectionIconSize "0"

seta cg_crosshairAlpha "1"

seta cg_crosshairAlphaMin "0"

seta cg_crosshairDynamic "0"

seta cg_crosshairEnemyColor "1"

seta cg_cursorHints "4"

seta cg_descriptiveText "1"

seta cg_drawBreathHint "1"

seta cg_drawCrosshair "1"

seta cg_drawCrosshairNames "1"

seta cg_drawFPS "Simple"

seta cg_drawLagometer "1"

seta cg_drawMantleHint "0"

seta cg_drawSnapshot "0"

seta cg_drawTurretCrosshair "0"

seta cg_gameBoldMessageWidth "60"

seta cg_gameMessageWidth "70"

seta cg_headIconMinScreenRadius "0.015"

seta cg_hintFadeTime "100"

seta cg_hudChatPosition "5 150"

seta cg_hudCompassMaxRange "1500"

seta cg_hudCompassMinRadius "0"

seta cg_hudCompassMinRange "0"

seta cg_hudCompassSize "1"

seta cg_hudCompassSoundPingFadeTime "2"

seta cg_hudCompassSpringyPointers "0"

seta cg_hudDamageIconHeight "64"

seta cg_hudDamageIconOffset "128"

seta cg_hudDamageIconTime "2000"

seta cg_hudDamageIconWidth "128"

seta cg_hudGrenadeIconHeight "25"

seta cg_hudGrenadeIconOffset "50"

seta cg_hudGrenadeIconWidth "25"

seta cg_hudGrenadePointerHeight "12"

seta cg_hudGrenadePointerPivot "12 27"

seta cg_hudGrenadePointerWidth "25"

seta cg_hudObjectiveMaxRange "2048"

seta cg_hudObjectiveMinAlpha "1"

seta cg_hudObjectiveMinHeight "-70"

seta cg_hudProneY "-160"

seta cg_hudSayPosition "5 126"

seta cg_hudStanceHintPrints "0"

seta cg_marks "0"

seta cg_marksLimit "1024"

seta cg_noTaunt "0"

seta cg_predictItems "1"

seta cg_scoreboardBannerHeight "24"

seta cg_scoreboardItemHeight "18"

seta cg_scoreboardScrollStep "3"

seta cg_scriptIconSize "0"

seta cg_subtitleCharHeight "12"

seta cg_subtitleMinTime "3"

seta cg_subtitlePosX "120"

seta cg_subtitlePosY "400"

seta cg_subtitles "1"

seta cg_subtitleWidthStandard "80"

seta cg_subtitleWidthWidescreen "80"

seta cg_teamChatsOnly "0"

seta cg_viewsize "100"

seta cg_voiceIconSize "0"

seta cg_voiceSpriteTime "6000"

seta cg_weaponCycleDelay "0"

seta cg_youInKillCamSize "6"

seta cl_allowDownload "1"

seta cl_anonymous "0"

seta cl_freelook "1"

seta cl_maxpackets "100"

seta cl_maxPing "800"

seta cl_mouseAccel "0"

seta cl_packetdup "0"

seta cl_pitchspeed "140"

seta cl_punkbuster "0"

seta cl_voice "0"

seta cl_wwwDownload "1"

seta cl_yawspeed "140"

seta com_hunkMegs "512"

seta com_introPlayed "1"

seta com_maxfps "140"

seta com_recommendedSet "1"

seta con_inputBoxColor "0.25 0.25 0.2 1"

seta con_inputHintBoxColor "0.4 0.4 0.35 1"

seta con_minicon "0"

seta con_miniconlines "5"

seta con_minicontime "4"

seta con_outputBarColor "1 1 0.95 0.6"

seta con_outputSliderColor "0.15 0.15 0.1 0.6"

seta con_outputWindowColor "0.35 0.35 0.3 0.75"

seta con_restricted "0"

seta fx_sort "1"

seta g_allowvote "1"

seta g_antilag "1"

seta g_banIPs ""

seta g_clonePlayerMaxVelocity "80"
seta g_deadChat "0"

seta g_deathDelay "1"

seta g_dropForwardSpeed "10"

seta g_dropUpSpeedBase "10"

seta g_dropUpSpeedRand "5"

seta g_log "games_mp.log"

seta g_logSync "0"

seta g_oldVoting "1"

seta g_playerCollisionEjectSpeed "25"

seta g_useGear "1"

seta g_useholdspawndelay "1"

seta g_voiceChatTalkingDuration "500"

seta g_voteAbstainWeight "0.5"

seta hud_deathQuoteFadeTime "1000"
seta hud_enable "1"

seta hud_fade_ammodisplay "0"

seta hud_fade_compass "0"

seta hud_fade_healthbar "0"

seta hud_fade_offhand "0"

seta hud_fade_stance "1.7"
seta hud_fadeout_speed "0.1"

seta hud_flash_period_offhand "0.5"

seta hud_flash_time_offhand "2"

seta hud_health_pulserate_critical "0.5"

seta hud_health_pulserate_injured "1"

seta hud_health_startpulse_critical "0.33"

seta hud_health_startpulse_injured "1"

seta in_mouse "1"

seta input_viewSensitivity "1"

seta loc_forceEnglish "0"

seta loc_language "0"
seta m_filter "0"

seta m_forward "0.25"

seta m_pitch "0.022"

seta m_side "0.25"

seta m_yaw "0.022"

seta mss_3d_provider "Miles Fast 2D Positional Audio"

seta mss_khz "44"

seta name "^^00N3U^^11|^^99@zt3ck"

seta net_noipx "0"

seta net_noudp "0"

seta net_sock
sEnabled "0"
seta net_socksPassword ""

seta net_socksPort "1080"

seta net_socksServer ""

seta net_socksUsername ""

seta r_aaAlpha "dither (fast)"

seta r_aaSamples "1"

seta r_anisotropy "8"

seta r_aspectRatio "wide 16:9"

seta r_autopriority "0"

seta r_depthPrepassModels "0"

seta r_displayRefresh "72 Hz"

seta r_distortion "1"

seta r_dlightLimit "8"

seta r_drawDecals "1"

seta r_drawSun "0"

seta r_fullscreen "1"

seta r_gamma "1.42857"

seta r_glow "1"
seta r_gpuSync "adaptive"

seta r_ignorehwgamma "0"

seta r_inGameVideo "1"

seta r_lodBias "0"

seta r_lodScale "1"

seta r_mode "1920x1080"
seta r_monitor "0"

seta r_multiGpu "0"

seta r_overbrightBits "1"

seta r_picmip "0"

seta r_picmip_bump "0"

seta r_picmip_manual "1"

seta r_picmip_spec "0"

seta r_polygonOffsetBias "16"

seta r_polygonOffsetScale "4"

seta r_portalBevels "0.7"

seta r_railCoreWidth "1"

seta r_rendererPreference "dx9"

seta r_swapInterval "0"

seta r_textureMode "bilinear"

seta r_zFeather "0"

seta rate "25000"

seta sc_enable "1"

seta sensitivity "1.92063"

seta server1 ""

seta server10 ""

seta server11 ""

seta server12 ""

seta server13 ""

seta server14 ""

seta server15 ""

seta server16 ""

seta server2 ""

seta server3 ""

seta server4 ""

seta server5 ""

seta server6 ""

seta server7 ""

seta server8 ""

seta server9 ""

seta snaps "20"

seta snd_bits "16"

seta snd_errorOnMissing "0"

seta snd_khz "44"

seta snd_slaveFadeTime "500"

seta snd_stereo "1"

seta snd_touchStreamFilesOnLoad "0"

seta snd_volume "1"

seta sv_allowDownload "1"

seta sv_floodProtect "1"

seta sv_hostname "CoD2Host"

seta sv_maxclients "20"

seta sv_maxPing "0"

seta sv_maxRate "0"

seta sv_minPing "0"

seta sv_punkbuster "0"

seta sv_reconnectlimit "3"

seta sv_voice "0"

seta sv_wwwBaseURL ""

seta sv_wwwDlDisconnected "0"

seta sv_wwwDownload "0"

seta sys_configSum "128026549"

seta sys_cpuGHz "3.08038"

seta sys_gpu "NVIDIA GeForce GTX 275"

seta sys_SSE "1"

seta sys_sysMB "1024"

seta ui_bigFont "0.4"

seta ui_browserFriendlyfire "-1"

seta ui_browserKillcam "-1"

seta ui_browserMod "-1"

seta ui_browserShowDedicated "1"

seta ui_browserShowEmpty "1"

seta ui_browserShowFull "1"

seta ui_browserShowNoPassword "1"

seta ui_browserShowPassword "1"

seta ui_browserShowPunkBuster "-1"

seta ui_browserShowPure "1"

seta ui_currentMap "0"

seta ui_currentNetMap "0"

seta ui_dedicated "0"

seta ui_extraBigFont "0.55"

seta ui_gametype "3"

seta ui_joinGametype "1"

seta ui_netGametype "0"

seta ui_netGametypeName "tdm"

seta ui_netSource "1"

seta ui_serverStatusTimeOut "7000"

seta ui_smallFont "0.25"

seta vid_xpos "3"

seta vid_ypos "22"

seta voice_deadChat "0"

seta voice_global "0"

seta voice_localEcho "0"

seta winvoice_mic_mute "1"

seta winvoice_mic_reclevel "65535"

seta winvoice_mic_scaler "1"

seta winvoice_save_voice "0"

[~N3U~AŽ†3ck™]

Chapter 4

Just an outline of some of what we went through and to get you ready to do some mad gaming.

The 3 main keys of CoD2 Pwnage is:

1. Be comfortable

First of all, your setup is very important. Being uncomfortable and playing in a mess affects your game in a very negative way. Clean up your room, and make sure you take a nice and relaxed position behind your computer before playing a game. Your mom might even start enjoying your passion for gaming.Your monitor should be directly infront of you,at a distance of 1.5 to 2 feet away,so your neck is in a central position facing straight ahead. The top of monitor should be at eye level. Adjust your screen so you can get less glare.Your forearms should be parallel to the ground and your keyboard and mouse should be within arm's length.

2. The good config

You need to have the right commands in your config. Below you will find a list of some of the important things you need to know about your config. For more just look back at the other chapters.

CAUTION: If you are NOT familiar with editing configs, you shouldn't change anything! If you change something you shouldn't, the game might utterly stop running.

Try to get at least 125 fps. If you aren't able to, then an upgrade would definitely benefit your gaming. There are a lot of settings when it comes to graphics, you should take a look at some of the fps guides
that are out there, with a bit of luck you may be able to get a good fps even with a slightly older computer.

Type the following commands in the console :

* /rate 25000

* /cl_maxpackets 100

* /snaps 30

* /com_maxfps 125 or /com_maxfps 250 (If you have a high-end pc)

* Fix all the control and mouse settings the way YOU like it! There are plenty of gamers out there with configs you can copy, but that might not be the best settings for you! Experiment with the different control settings and mouse sensitivities, and remember, things such as drivers and your Windows mouse sensitivity also affect your in-game mouse movement.

Once you fixed all your settings, it?s time to get used to them. Get on those public servers, play those practice wars, frag away and build up your confidence. Getting used to new settings takes a while, so give it time!


3. Playing style

The most important thing, of course, is your gameplay style.

You should try to come up with your own play style. Below we'll sum up some of the most important things you should remember if you want to play at a higher level.

* As mentioned above, creating your own style is very important. But variations in that style are as important as the style itself. Make sure your opponent can't calculate what your next move is going to be!
Don't do the same thing, the same way, all the time.

* Following the previous tip, try to read your opponent's game and to think one step ahead of him to determine your next move. This will only work when done in the right situation and being 100% sure about it.

* CAUTION: Don't try to be ahead of your opponent all the time. They will know and this will result in the opposite of what you're trying to reach.

* When practicing on a public server, DO NOT only use the gun you play with during team games. Try and practice all weapons to become a solid all-round player. In certain situations during a team game it's
important to pick up a gun from the ground and if you can't control this weapon you might lose a very important round. Professional players can handle every weapon!

* You are the best player out there! Or well, that is the way you should be thinking. If you know that you will beat your opponent, then you will have a better chance of doing so. If you don?t, this will affect your
play in a negative way.

* Also very important is to know the maps inside out! Knowing every corner, hiding place, grenade spot, etc... will give you a huge advantage to surprise your opponent or to take cover.

* When ending up in a situation when it's you against a lot of enemies, never give up and stay focused! Try to stay calm and find a way to win the round. If you do, this will boost your self-confidence enormously.

* Use the deathcam to your advantage. When you die the camera hangs above your body for 1-2 seconds. When this happens you can see the direction your opponent is going. This is a very important last call 
you have to make to your teammates.

* CAUTION: Your opponent might anticipate the fact that you see him via deathcam so watch out for fake movements!

[~N3U~AŽ†3ck™]

SO now you have 3 options:

1. You can build you a config file and tweak it as necessary.

2. You can use my config file that I have posted and tweak it to your needs.

3. Or you can use the basics which are:

Commands:
cg_drawfps 1
com_maxfps
cl_packetdup
cl_maxpackets
snaps
In game options
run DX7
antialiasing off
Bilinear
mouse smooth

Note if you can adjust the DPI on your mouse, set it to high and lower the sensitivity in game.
Also haveing a dedicated sound card gives you a 10% increase in game performance which can be a lot - basically a 10-20 fps performance boost.

[~N3U~AŽ†3ck™]

UPDATE:
The lagometer is a tool provided to diagnose the condition of your connection, and to let you know when things are proceeding normally and when they are not. The following is a brief explanation in text and pictures of what the lagometer does and what it indicates.

First, you need to turn it on. In the console, type:

cg_lagometer 1