Set up Call of Duty 2.
Do this before your first match. The default graphics can look good, but these settings put visibility and performance first.
Switch to DirectX 7
In multiplayer, open Options → Graphics. Set Rendering Method Preference to DirectX 7 and apply the change.
This uses simpler graphics and can improve FPS. Keep your screen’s native resolution for a sharp picture.
Increase brightness
Raise Brightness in the graphics settings until dark areas are easier to see. Check it on a map and stop before the image looks washed out.
Open the console
Go to Options → Game Options and enable the console. Press the key below Esc (usually ~ or `) to open it.
Set your FPS to 250
Enter each command separately and press Enter.
/com_maxfps 250We recommend a 250 FPS cap. It won’t make your PC produce frames it can’t render.
/cg_drawFPS 1Shows your FPS so you can check performance while playing. Test during fights and around smoke, not only while standing still. Once you’re happy, hide the counter with
/cg_drawFPS 0.If your PC can’t hold 250 FPS consistently, lower the cap to a stable target, such as
/com_maxfps 125. Follow any FPS limits enforced by your server.FPS still stuck at your monitor’s refresh rate?
In Graphics, turn off Sync Every Frame (V-Sync) and apply. This can allow higher FPS, though you may notice screen tearing.
Fine-tune your setup
Optional. Change one thing at a time and keep what works for you.
Resolution, refresh rate, and clear visuals
Start at your monitor’s native resolution with the matching aspect ratio. If you need more FPS, lower the resolution and compare. Old competitive resolutions are a preference, not a requirement.
In Windows, open Settings → System → Display → Advanced display and choose a refresh rate supported by your monitor at the selected resolution. Check the in-game refresh-rate setting too.
FPS is how many frames the game renders; Hz is how often the display refreshes. A 250 FPS cap doesn’t turn a 60 Hz screen into a 250 Hz display.
If performance is still low, try reducing anti-aliasing in Graphics and compare FPS on the same map. Keep enough image detail to recognise players at a distance.
Windows refresh-rate instructionsMouse input and a sensitivity you can keep
With CoD2x installed, you can use its integrated raw mouse input:
/m_rinput 2For a simple starting point, turn off in-game acceleration and smoothing:
/cl_mouseAccel 0/m_filter 0Choose a comfortable mouse DPI and leave it fixed while you adjust in-game sensitivity. Aim at a small point, track a moving player, and check that you can turn comfortably within your mousepad space.
If you consistently overshoot, lower sensitivity a little. If turning is difficult, raise it a little. Test both close and long-range fights, then keep the setting for several sessions instead of changing it after each missed shot.
Already comfortable with your settings? Keep them. These are a baseline, not a requirement to replace a setup you know.
The raw-input command requires CoD2x. Set /m_rinput 0 to return to its Windows cursor input mode. Note your existing values before changing acceleration or smoothing.
Controls that let you keep moving
Check that you can move, aim, lean, crouch, and throw a grenade without an awkward reach or an unintended key release. Use buttons you can find without looking.
Try hold-to-aim and toggle-to-aim in the controls menu. With hold, releasing the button exits aiming; with toggle, another press does. Choose what feels comfortable rather than copying someone else’s entire keyboard layout.
Test the actions together in a quiet game: strafe while aiming, lean from cover, switch from crouch to prone, and move while preparing a grenade.
Reduce visual clutter
If blood effects, ejected shell casings, or bullet marks distract you, these optional commands turn them off:
/cg_blood 0Blood effects/cg_brass 0Ejected shell casings/cg_marks 0Bullet impact marksUse 1 instead of 0 to turn each effect back on. These are visibility preferences; any FPS benefit depends on your setup.
Keep useful information such as the compass, grenade warnings, and team messages visible. Servers or competitive rules may restrict settings.
Check stutter without guessing at network tweaks
First watch /cg_drawFPS 1 to see whether the game’s frame rate drops. The lagometer can also help you notice connection interruptions:
/cg_drawLagometer 1Compare another server before changing your configuration. A frame-rate drop and a connection interruption are different problems; changing packet settings is not a general fix for either.
Hide the graph afterward with /cg_drawLagometer 0. Follow the server or platform’s current connection guidance instead of copying an old rate, snaps, or packet preset.
Save your settings and test changes properly
Before experimenting, close the game and copy your configuration somewhere safe. Current CoD2x uses main/config_mp.cfg inside the game folder.
Note the original value of any setting you change. Use the same map, weapon, and route to compare one change at a time. Keep a change only if it repeatedly helps, not because of one good round.
Console tip: type the beginning of a command and press Tab to autocomplete. Use Page Up and Page Down to review earlier console messages.
Sources and older advice
Practical tips are adapted from the supplied TEK9 All About COD2 guide, which references 2013. Its Windows XP, registry-cleaner, PunkBuster, and speculative recoil tweaks are omitted.
Modern raw input, config location, and server FPS restrictions follow CoD2x documentation. Additional command examples: eSko’s COD2 configuration. Preferences and FPS targets are not performance guarantees.