CALL OF DUTY™ README
Last Updated: 2005-1-20

Call of Duty™ 1.5b Server Patch
Last Updated: 2005-01-04

This is the official release of the Call of Duty™ v1.5b Server Patch by Activision®.

IMPORTANT NOTES: Use of the in-game console is not supported by Activision®.  Please do not contact Activision® Customer Support with issues that arise from using console commands in-game.

It is strongly recommended that you disable any anti-virus software before installing.

NOTES FOR MOD USERS:
- It is recommended that any user modifications that have been installed to the Call of Duty™ directory be removed before installing this patch. These modifications are not supported by Activision® and may not be compatible with some of the new features that are included.
- Call of Duty™ does not support mods that have spaces in the mod's folder name.  Be sure that the folder that contains your mod does not have spaces; otherwise users will not be able to download the files.  For example, a mod in a folder called "My Mod" would be invalid, whereas "MyMod" or "My_Mod" would work.

-This patch resolves an exploit that can be used to crash servers

CALL OF DUTY™ 1.5 PATCH README
Last Updated: 2004-12-09

INTRODUCTION & IMPORTANT NOTES

This document details numerous additions, fixes, and changes to Call of Duty™ in the 1.5 patch.

IMPORTANT NOTE:  Use of the in-game console is not supported by Activision®.  Please do not contact Activision® Customer Support with issues that arise from using console commands in-game.

It is strongly recommended that you disable any anti-virus software before installing.

NOTES FOR MOD USERS:
- It is recommended that any user modifications that have been installed to the Call of Duty™ directory be removed before installing this patch. These modifications are not supported by Activision® and may not be compatible with some of the new features that are included.
- Call of Duty™ does not support mods that have spaces in the mod's folder name.  Be sure that the folder that contains your mod does not have spaces; otherwise users will not be able to download the files.  For example, a mod in a folder called "My Mod" would be invalid, whereas "MyMod" or "My_Mod" would work.

IMPORTANT NOTE: Upon installing the 1.5 patch, you may be prompted to re-enter your CD key. Please be sure to have your Call of Duty™ CD key handy.

INVALID INSTALLATION MESSAGE:  If you get a "Setup did not detect a valid Call of Duty™ CD Key" error message when installing the 1.5 patch, you can try one of two things to address this issue:
1. Exit out of the patch setup and load up Call of Duty™ Multiplayer.  In the Multiplayer Options screen, re-enter your Call of Duty™ CD key, exit the program, and then apply the patch again.  
2.  If you get the error again, exit out of the 1.5 patch installer.  Completely uninstall Call of Duty™, reinstall the game, and then apply the patch.

Either one of these solutions should correct the problem.

NEW FEATURES

Added one new Multiplayer map.  This map supports all current game types:

mp_tigertown

Tigertown is a small farm town located in Normandy, France which has been partially destroyed by a heavy artillery attack. The environment is designed for “Search and Destroy” as the American Airborne forces push their way up the town’s hillside to knock out the flak88 and Tiger tank heavily guarded by the German Waffen SS. The Allied forces need to attack strategically and gain ground quickly so as to distract the Axis from properly defending their positions. Precision flanking from both sides is a key factor when taking over and controlling the town.

Players in HQ, RE, SD, TDM, and BEL games can now call timeouts.  To call a timeout, use \matchtimeout in the console.  To end a timeout in progress, use \matchtimein.  These commands are bindable.  (Note to mod-makers: in order to allow your players to call timeouts, the players have to belong to a team.ex: Allies/Axis.)
All time measurements are in milliseconds.
Related server cvars: 
1.	g_timeoutsAllowed – The number of timeouts allowed per side. 
2.	g_timeoutLength – The length of each timeout. 
3.	g_timeoutRecovery – The length of the preparation period which occurs after a time-in is called, or after a timeout expires.  This recovery period is used to alert all players that play is about to begin. 
4.	g_timeoutBank – The total amount of time a team can spend in timeout. 
Related client cvars:
1.	ui_timeoutsAllowed – Contains the value of the server’s g_timeoutsAllowed cvar.
2.	ui_timeoutLength – Contains the value of the server’s g_timeoutLength cvar.
3.	ui_timeoutRecovery – Contains the value of the server’s g_timeoutRecovery cvar.
4.	ui_timeoutBank – Contains the value of the server’s g_timeoutBank cvar.

Added HTTP redirection for Servers running Mods or custom maps.  To enable redirection on the server, set sv_wwwDownload to 1.  Set sv_wwwBaseURL to the base directory where the files are stored. For example, if the server had a file named ‘myfile’ meant to be stored locally at \Call of Duty\Main, sv_wwwBaseURL should be set to “http://samplewebpage1.com/”. The file should be stored at http://samplewebpage1.com/Main/myfile. To prevent clients from taking up a slot on the server while downloading, set sv_wwwDlDisconnected to 1. This will free up a slot for the duration of the download and the client will attempt to autoconnect when the download is complete. Set cl_wwwDownload to 1 to enable redirection downloading on the client.

MULTIPLAYER ENHANCEMENTS

Client console lock– Servers can now opt to disable a client’s access to the console by setting sv_disableClientConsole to 1.  Mod creators should reference the “Decimal Type Field” information under Scripting and Mods support. 

Added g_deadChat – This server setting gives admins the ability to allow dead players to chat with live players.  Set this cvar to 1 to enable dead chatting.

Added extra vote options – Players can now vote to change the killcam, draw friendly icons, and friendly fire settings.  (These do not use new cvars, rather they give players the chance to change existing ones: scr_killcam, scr_drawfriend, and scr_friendlyfire.)	

Voting cvars for all vote options – Allows server admins to decide which voting options their clients have access to.  Set the cvar to 1 if you want to permit players’ votes on that option.  New Cvars: g_allowVoteKick, g_allowVoteMap, g_allowVoteMapRestart, g_allowVoteMapRotate, g_allowVoteTempBanUser, g_allowVoteTypeMap, g_allowVoteDrawFriend, g_allowVoteFriendlyFire, and g_allowVoteKillCam. 

TDM scoring– Added an option to have killing teammates or committing suicide during a TDM game reduce the team’s score as well as the individual’s. This option is controlled by a cvar (scr_teamscorepenalty) and defaults to 0, which is the original scoring method. 

Private clients - The server browser now accurately displays the total number of clients on a server-regardless of whether some of them are private clients.  The number of open private client slots is never displayed.  Instead, when a private client slot is filled, the perceived max clients value will increase.

Improved portal seams throughout the game. 

Corrected an exploit that caused some servers to shut down unexpectedly. 

Corrected an issue where screenshots sometimes appeared black on ATI® Radeon™ 9800 cards

The games_mp.log file now records and formats all information properly in games longer than 999 minutes. 

The command “updatescreen” no longer turns off the ambient sound

scr_friendlyfire, scr_killcam, and scr_drawfriend are now read only cvars and need to be setup in a config file prior to running a server. These cvars can be changed in-game by using the voting system provided voting is enabled.

SCRIPTING AND MOD SUPPORT

IMPORTANT NOTE: Several features of the 1.5 Call of Duty™ patch are intended for makers of end-user mods or to allow compatibility with certain mod features. Most of the items listed below will only function properly with scripting support from a mod. 

New Server-Side Mod functionality – Server admins now have a way to flag pak files as being “Server-Side only” and clients will never attempt to download those pak files, regardless of client or server autodownload settings.  To enable this feature, place the following text anywhere in the name of the pak file: “_svr_” (without the quotes). For instance, myservermod.pk3 would become myservermod_svr_.pk3. This allows a server admin to leave downloading on at all times without clients attempting to download the mod and will be especially helpful for modded servers that run custom maps. 

Added Squad chat - Players can now be assigned to squads from script.  In script, set the “self.sessionsquad” variable to one of the squad values:  “free”, “squad_alpha” or “squad_bravo”.  The default setting is “free”.  There is a new console command, which allows players to send a message to only their squad mates.  In the console, type “say_squad <message>”.  If the player is in a squad, his message will be sent to each of his squadmates.  If he is not in a squad, the message will be sent to each of his teammates.  Finally, if he is not on a team, it will be sent to everyone.  To bind this functionality to a key, use “\bind [key] “messagesquad””.

Increased max cvar limit for MP:  MAX_CVARS = 2048

Added Script command for player speed (The “maxspeed” script command sets a player’s speed before stance modifiers.  If this feature is not used, the game functions as normal.   
Ex:	self maxspeed(250)

Decimal Type Fields added - Menus can now be tweaked (to compensate for the loss of console access when using sv_disableclientconsole).  Print float values by using ITEM_TYPE_DECIMALFIELD in the menu files.  Pair up the decimal field with the cvar/itemdef you wish to set and make sure that, within the decimal field’s itemdef, there is a cvarfloat defining the field’s permitted numerical range.

Added Autodemo – The autodemo capability consists of two script commands: autodemostart and autodemostop.  These commands should be placed in the <gametype>.gsc and the syntax of the command is this: player autodemostart();.  To enable the autodemo capability on the server, set g_autodemo to 1.  To force a client to accept the autodemo command, set cg_autodemo to 1.  Autodemos must be enabled on the server in order for the client’s setting to matter—if g_autodemo is set to 0, clients will not receive the command.

Added Autoscreenshot - The autoscreenshot capability relies on a script command: autoscreenshot.  This command should be placed in the <gametype>.gsc and the syntax of the command is this: player autoscreenshot();.  To enable the autoscreenshot capability on the server, set g_autoscreenshot to 1.  To force a client to accept the autoscreenshot command, set cg_autoscreenshot to 1.  Autoscreenshots must be enabled on the server in order for the client’s setting to matter—if g_autoscreenshot is set to 0, clients will not receive the command.

Added a new demo fast forward command – “jumptodemoend”.

Added ‘getstance()’ – A script command which returns which stance a player is in: stance = self getstance();  Returned values will be “stand”, “crouch”, or “prone.”

CALL OF DUTY™ 1.4 PATCH README
Last Updated: 2004-4-5

INTRODUCTION & IMPORTANT NOTES

This document details numerous additions, fixes, and changes to Call of Duty™ in the 1.4 patch.

IMPORTANT NOTE:  Use of the in-game console is not supported by Activision®.  Please do not contact Activision® Customer Support with issues that arise from using console commands in-game.

NOTES FOR MOD USERS:
- It is recommended that any user modifications that have been installed to the Call of Duty directory be removed before installing this patch. These modifications are not supported by Activision® and may not be compatible with some of the new features that are included.
- Call of Duty does not support mods that have spaces in the mod's folder name.  Be sure that the folder that contains your mod does not have spaces; otherwise users will not be able to download the files.  For example, a mod in a folder called "My Mod" would be invalid, whereas "MyMod" or "My_Mod" would work.

IMPORTANT NOTE: Upon installing the 1.4 patch, you may be prompted to re-enter your CD key. Please be sure to have your Call of Duty™  CD key handy.

INVALID INSTALLATION MESSAGE:  If you get a "Setup did not detect a valid Call of Duty™  CD Key" error message when installing the 1.4 patch, you can try one of two things to address this issue:
1. Exit out of the patch setup and load up Call of Duty™  Multiplayer.  In the Multiplayer Options screen, re-enter your Call of Duty™  CD key, exit the program, and then apply the patch again.  
2.  If you get the error again, exit out of the 1.4 patch installer.  Completely uninstall Call of Duty™ , reinstall the game, and then apply the patch.

Either one of these solutions should correct the problem.

ERROR WHEN SAVING GAME:  If you get a "Short write in FS_copyfiles ()" error message when attempting to save your game, it means that your hard drive is full and there is not enough hard disk space to write the saved game file.  Please free up additional hard drive space in order to correct this issue.

PUNKBUSTER™

Call of Duty™ now includes PunkBuster™ Anti-Cheat software technology.  PunkBuster™ Anti-Cheat software technology and services combat online cheating in Call of Duty™  Internet play.

The use of PunkBuster™ Anti-Cheat software is optional and is provided without direct cost to our users.  For more information about PunkBuster™ or for PunkBuster™ support, please visit http://www.evenbalance.com/.

NEW FEATURES

- Added one new multiplayer map.  This map supports all current game types:

mp_stalingrad

Stalingrad - In the winter of 1942, Soviet infantry from the 13th Guards Division struggle to hold a small apartment complex in the southern end of the shattered city. Riflemen on both sides can cover the open ground while flanking teams armed with automatic weapons attempt to penetrate the enemy line through a deadly close-quarters maze of urban interiors.

- New PunkBuster™ functionality included (as described above). 
- Added a “PunkBuster” filter under the “Filters” section of the “Join Server” screen.
- Added a “PunkBuster” display column on the “Join Server” screen. 

GAMETYPE FIXES

- Corrected an issue in “Search & Destroy” where leaning while planting the bomb would cause the player to lean further than intended. 
- Corrected an issue where a player could spawn without a gun model if the round ended while on a ladder.

MULTIPLAYER BUG FIXES

- Fixed a possible exploit with certain spectator-specific commands. 
- Fixed a bug with the servercache.dat that caused some players to have difficulty loading the in-game browser. 
- Fixed an issue where the number of servers displayed in the in-game browser would occasionally fluctuate. 
- Fixed an issue where the pure server check would no longer ignore extraneous pak files if a demo had recently been played.
- Fixed a rare occurrence of the auto balance system preventing a player from joining either team. 

CALL OF DUTY™ 1.3 PATCH README
Last Updated: 2004-03-17

INTRODUCTION & IMPORTANT NOTES

This document details numerous additions, fixes, and changes to Call of Duty™ in the 1.3 patch.

IMPORTANT NOTE:  Use of the in-game console is not supported by Activision®.  Please do not contact Activision® Customer Support with issues that arise from using console commands in-game.

NOTES FOR MOD USERS:
- It is recommended that any user modifications that have been installed to the Call of Duty directory be removed before installing this patch. These modifications are not supported by Activision® and may not be compatible with some of the new features that are included.
- Call of Duty does not support mods that have spaces in the mod's folder name.  Be sure that the folder that contains your mod does not have spaces; otherwise users will not be able to download the files.  For example, a mod in a folder called "My Mod" would be invalid, whereas "MyMod" or "My_Mod" would work.

IMPORTANT NOTE: Upon installing the 1.3 patch, you may be prompted to re-enter your CD key. Please be sure to have your Call of Duty CD key handy.

INVALID INSTALLATION MESSAGE:  If you get a "Setup did not detect a valid Call of Duty CD Key" error message when installing the 1.3 patch, you can try one of two things to address this issue:
1. Exit out of the patch setup and load up Call of Duty Multiplayer.  In the Multiplayer Options screen, re-enter your Call of Duty CD key, exit the program, and then apply the patch again.  
2.  If you get the error again, exit out of the 1.3 patch installer.  Completely uninstall Call of Duty, reinstall the game, and then apply the patch.

Either one of these solutions should correct the problem.

ERROR WHEN SAVING GAME:  If you get a "Short write in FS_copyfiles ()" error message when attempting to save your game, it means that your hard drive is full and there is not enough hard disk space to write the saved game file.  Please free up additional hard drive space in order to correct this issue.

EAX® 3 SUPPORT

Call of Duty now supports Creative®’s EAX® 3 audio system in both Single Player and Multiplayer.  Only hardware that officially supports EAX® 3 will be able to utilize this feature.

For a list of sound cards that support EAX® 3, go to http://eax.creative.com/.

Note for Audigy® LS and NX users: You may experience some sound distortions when using the EAX® audio system.  While this has been corrected for the majority of Audigy® users through driver updates, these updates may not be available for your card.  If you encounter such an issue, please revert to the Miles™ Fast 2D Positional Audio system.

Note on New Maps:  The two new maps (Bocage and Neuville) included with the 1.3 patch do not have EAX® 3 support.  The sound will function properly on those maps, but there will be no EAX® 3 audio effects.

NEW FEATURES

- Added two new multiplayer maps, Bocage and Neuville.  Both of these maps support all current game types:

mp_bocage
 
The Normandy terrain provides a natural advantage to the defender.  Between the Orne and Vire Rivers is fifty miles of bocage; small fields surrounded by high earthen banks overgrown with shrubbery.  Visibility is limited to one field at a time and the bushes provide cover from air and ground reconnaissance, making for superior defensive terrain.  Each field is a death trap, earned with a hard fought series of firefights.  The breadth of terrain and varied tactical scenarios make this the perfect setting for the “Headquarters” game type.  When the attacks come from every direction, both teams will be put to the test.

mp_neuville

Neuville represents a destroyed town in Normandy, reduced to rubble amidst close combat between U.S. Airborne units and battle-hardened Waffen SS troops.  Soldiers can find ample cover amidst the piles of rubble and massive shell craters.  The environment is primarily designed for the “Search and Destroy” game type and provides a greater spread of attacking and flanking routes.  This keeps defenders on their toes, and prevents attackers from being completely pinned down at narrow chokepoints.
 
GAMETYPE FIXES

- Radios for Headquarters made non-solid, to fix a potential exploit.
- Improved server load in Headquarters spawning by making reinforcements spawn over multiple server frames rather than just one.  This will create less lag when reinforcements spawn.
- Headquarters now has a five second grace period.  If you spawn and die then you get to respawn immediately. (farther away so you are not as likely to die again)
- Fixed the bomb ticking sound not always working in “Search & Destroy.”

WEAPON & PLAYER FIXES

- Fixed an exploit where prone players who leaned around corners could see the enemy without being seen.
- Fixed an exploit where players could switch between prone and jumping positions to move rapidly across a map. 
- Fixed a bug with the sway animation of the sniper rifle scope on high ping servers.
- Fixed an exploit where people could get extra grenades in “Search & Destroy” and “Retrieval.”
- Fixed an exploit where reload animations could be skipped, decreasing reload times.
- Fixed the bullet path of the PPSh and Sten in Aim Down The Sight mode.
- Fixed a bug where players in all areas of the map heard the “click” of an empty weapon.
- Fixed several minor animation bugs related to stance, leaning, jumping, etc.

MULTIPLAYER BUG FIXES

- Fixed a slow update problem with the server list.
- Fixed a problem where the server list would improperly list servers with a ping of "1."
- Fixed an issue with the server list being incomplete under certain circumstances.
- When sorting the server list by a key other than ping, all entries of the same key are sorted by ping, instead of being random.
- Fixed server determination of which clients require authorization. (This corrects the issue where some Internet players received a GUID of 0)
- Autobalance was updated to prevent players from joining a team if this action would cause that team to be unbalanced. 
- Setting scr_teambalance to any number greater than 0 will balance teams to within that number of players, for example, 'scr_teambalance 2' balances the teams within 2 players. (8 vs 10 is ok, but 8 vs 11 is not)
- True spectators (not dead players) are no longer restricted by the freelook cvar. They can always freelook.
- If you are spectating a player (through their eyes) and you go into freelook, your view is no longer capped to the 180-degree arc of the ladder.
- Removed the ‘weapon’ command.
- Increased the max cfg file that can be executed to 64K from 16K.
- Unknown commands in the server console now do not print to all clients. A say command is now required.
- Fixed an issue where rcon status would occasionally not show all of the players on a server.
- Fixed an issue on some ATI cards that would cause water to render improperly. (also affects Single Player)
- Fixed an issue where too many custom pak files (maps or mods) would cause the “Pak Sum / Name Mismatch” error.  (Also affects Single Player)
- As an added security feature, your CD key will no longer be displayed in the Multiplayer Options menu.
- Fixed not being able to immediately climb on a ladder after landing from a jump.
- The "screenshot,” "screenshotJPEG,” and "record" console commands no longer overwrite existing files.
- Cheat protected r_intensity.
- Fixed player pings in the scoreboard.  Previously if you were spectating someone, your displayed ping was for the person you were spectating.
- Fixed a rare case of player stacking in multiplayer.
- The Weapon, Item, say, sayteam, and tell log prints now include client guid, id, and name. (This will be useful for logging stats by actual player GUID, rather than by player name)

CALL OF DUTY™ MULTIPLAYER PATCH 1.2 README
Last Updated: 2004-01-20

TABLE OF CONTENTS

INTRODUCTION

GAMETYPE FIXES
1.  Behind Enemy Lines
2.  Search & Destroy

WEAPON & PLAYER FIXES

NEW FEATURES
1.  New Gametype - Headquarters
2.  Killcam On/Off
3.  Disable Freelook Spectating
4.  Disable spectating enemy players
5.  Force team balancing
6.  Shared Friendly Fire
7.  Ban Abilities For Server Administration
8.  Server Hardware displayed in Server Browser
9.  New Server Filters
10.  Server Info Screen
11. Timedemo statistics
12.  New script commands
13.  Allow Downloads

MULTIPLAYER BUG FIXES

INTRODUCTION

This document details numerous additions, fixes and changes to Call of Duty™in the Multiplayer 1.2 patch.

IMPORTANT NOTE:  Use of the in-game console is not supported by Activision®.  Please do not contact Activision® Customer Support with issues that arise from using console commands in-game.

NOTES FOR MOD USERS:
- It is recommended that any user modifications that have been installed to the Call of Duty directory be removed before installing this patch. These modifications are not supported by Activision® and may not be compatible with some of the new features that are included.
- Call of Duty does not support mods that have spaces in the mod's folder name.  Be sure that the folder that contains your mod does not have spaces, otherwise users will not be able to download the files.  For example, a mod in a folder called "My Mod" would be invalid, whereas "MyMod" or "My_Mod" would work.

GAMETYPE FIXES

1.  Behind Enemy Lines

- Fixes some allies not showing up on the compass in large servers.
- Fixed a bug that would make enemy indicator on the compass not show up.
- Fixed the killcam window remaining on screen during the black screen when you are about to spawn as an allied player.
- At the end of a round all players show on the same team to make it easier to see how players ranked.

2.  Search & Destroy

- You no longer have a weapon when planting the bomb.
- Planting the bomb near the end of the round stops the round timer, so that the bomb is now the condition for victory. 
- Bombs can no longer be planted after a round has been declared over.
- Reaching the timelimit (scr_sd_timelimit) no longer ends the game mid-round.

WEAPON & PLAYER FIXES

- Adjustments made to the sniper rifles to make them balanced.
- When a player lands after jumping, his/her speed is briefly reduced, making bunny hopping a less effective tactic in multiplayer.
- Adjusted hitboxes on player models to make them more accurate and thus making rifles more effective.
- The number of grenades given to a player is now based on the weapon selected. Sniper rifles provide 1 grenade, Bolt-action rifles provide 3 grenades,  and all other weapons provide 2 grenades.

NEW FEATURES

1.  New Gametype - Headquarters

- A radio randomly spawns into a map as neutral.  Your team must capture a radio by standing near it with no enemies around.
- Your team must control a radio to gain points.  A team is awarded 45 points for every 45 seconds it holds the radio.
- Destroying an enemy radio rewards your team with as many points as are left on the reinforcement timer  (e.g. if you destroy the radio with 16 seconds left on the reinforcements timer, your team will receive 16 points). 
- If your team loses the radio, a new radio will spawn in a different location. This radio is now neutral and must be captured. 
- Spawns are regulated by a reinforcement timer, which spawns players in 45 second intervals. This reinforcement timer is displayed on the HUD and players only have to wait until the closest spawn period before rejoining the battle. 

2.  Killcam On/Off

- Added server-side cvar scr_killcam to turn on/off killcam
	
3.  Disable Freelook Spectating

- Added server-side cvar scr_freelook to turn on/off freelook spectator mode
	
4.  Disable spectating enemy players

- Added server-side cvar scr_spectateenemy to turn on/off spectating the other team while dead
	
5.  Force team balancing

- Added server-side cvar scr_teambalance to force teams to have the same number of players. Teams with an odd number of players will be as balanced as possible. 
(Round based gametypes will adjust the teams between rounds, respawn gametypes will adjust the teams every 60 seconds)

6. Shared Friendly Fire

-Setting scr_friendlyfire 3 will share damage in cases of friendly fire between the victim and attacker.

7. Ban Abilities For Server Administration

Uniquely identified players printed in stats logging:
-The log used for stat tracking now includes player unique identifiers so players can be uniquely tracked based on cdkey instead of being tracked by player name.  Note that there is no way anyone can determine your cdkey from your GUID.

- Server administrators now have the option to Ban players from their server permanently.  The banned players are stored in a “ban.txt” file on the server, which can be manually edited by the server admin.
- The commands "banUser" and "banClient" ban somebody currently playing on a server by their in-game name or client number.  This adds the player to "ban.txt,” and kicks them from the server.
- You can unban every uniquely identified player with the name "UnnamedSoldier" using "unban UnnamedSoldier" from the console.  If you want to unban a single player whose name appears more than once, you should edit "ban.txt" manually.
- Server administrators also have the option of temporarily banning a player from a server for X amount of time (in seconds).  Use the command \sv_kickBanTime to change the length of the ban.  This Temp Ban option has also been added to the CallVote menu, allowing players to kick "griefers" and prevent them from simply reconnecting immediately.

NOTE:  Ban commands are for Internet servers only.  They do not function on LAN servers.

8.  Server Hardware displayed in Server Browser

- Added a column with icons displaying what hardware each given server is (Win Dedicated, LINUX, etc).
- Added an indication whether or not the server is modded to the server browser.	

9.  New Server Filters

- Added pure server, friendly fire, killcam, server modded, and dedicated only server filters.

IMPORTANT NOTE:  The "Pure Server" filter is set to "Pure Servers Only" by default.  When the patch is installed, it will show only pure servers unless you change to another setting. This setting can be found by clicking on "Join Server" and selecting the "Filters" submenu. 

10.  Server Info Screen

- On connecting to a server you will now see a server info screen which lists the servername, message of the day, gametype, and current settings appropriate to the gametype.

11. Timedemo statistics

- Timedemos write a .csv file based on the map name and resolution that says how many milliseconds each frame took.  This can be opened directly in a spreadsheet program for benchmarking performance over time.

12.  New script commands

- Added "precacheTurret( turretinfo )" script command to MP.
- Added "spawnTurret( classname, origin, turretinfo )" script command to MP.
- Added "enableWeapon()" and "disableWeapon()" player script commands to MP.

13.  Allow Downloads

There is a new client command in the Multiplayer Options screen called "Allow Downloading."  When set to on, connecting to a server that contains a new map or mod will automatically begin downloading the files associated with the map or mod.

MULTIPLAYER BUG FIXES

- Removed music from multiplayer menus
- Fixed minefield explosion sounds not always playing correctly
- Fixed minefield explosion damage killing nearby players
- Teammate icons (scr_drawfriend) are smaller and slightly transparent now.  They are also based on nationality.
- Fixed crash that would happen for some people on start of multiplayer if "cl_motd" was set to "1".
- Fixed an exploit that would turn the world solid black.
- The "tell" command works from a dedicated console to send a message to a single client.
- You cannot "callvote" a non-existent map from the console.
- Fixed "callvote" failing as soon as one less than half the people vote no.
- Fixed some issues with mods and some issues with pure servers.
- Fixed nearby trees vanishing in large outdoor levels when lots of effects go off at once.
- Changed the draw order on the compass so that friendlies draw on top of objectives.
- Font files now try to load from the main language folder first.
- Fixed bug where if you strafed off a ladder it would repeatedly grab and drop the whole way down the ladder.
- When you fall from a ladder you no longer play the ladder climb down animation.
- Grenades no longer float in air if they planted on something that moved.
- Grenades no longer jiggle when planting on players.
- Adjusted the position of the Kar98 when aiming down the sight.
- Players no longer run in place when planting a bomb.
- Fixed case of the gun not getting placed in the right hand when you die while reloading.
- Fixed the reload animation playing after you respawn.
- Fixed some view problems with the MG42.
- Fixed cvar propagation issues seen when joining a server and then starting your own server
- Fixed ambient sounds continuing from the previous map when starting to load the next
- The scoreboard now is scrollable at the end of a map.
- The icon for password-protected games should now properly show in the server browser menu.
- Fixed a crash in the main menu that came about when users left the computer sitting at the menu for prolonged amounts of time.  
- Fixed a crash changing map and gametype via vote menu. 
- Fixed a problem with the host not being able to join a team after the map changed. 
- Fixed sporadic friendly fire message when killing an enemy player in Behind Enemy Lines. 
- Fixed a problem with cdkeys not being displayed after connecting to a server running a mod.
- The Server Info button on the Join Server screen now displays additional server information. Friendly Fire and Kill Cam settings are now displayed.
- Removed unused cl_timenudge cvar to prevent possible exploit.
- Cheat-protected r_colormiplevels to prevent possible exploit.

CALL OF DUTY™ README
Last Updated: 2003-08-23

TABLE OF CONTENTS

INTRODUCTION

INSTALLATION & SET UP ISSUES
  1.  Minimum System Requirements
  2.  CD Key
  3.  DirectX® Detection & Installation
  4.  Error Message:  “Couldn't Load Default.cfg”
  5.  Error Message:  “Hunk unable to allocate 128MB of memory”
  6.  Splash Screen Will Not Change From “Uninstall” To “Install”
  7.  Launch Problems on nVidia® nForce™2 Motherboards 
  8.  Issues With Installer Properly Switching To Disc 2 During Installation

VIDEO, SOUND, & PERFORMANCE OPTIONS
  1.  Video Mode
  2.  Full Screen
  3.  Character Textures
  4.  General Textures
  5.  Texture Filter
  6.  Texture Quality
  7.  nVidia® Distance Fog
  8.  Brightness
  9.  Subtitles
10.  Master Volume
11.  Sound Quality
12.  Sound Provider
13.  Wall Marks
14.  Ejecting Brass
15.  Dynamic Lights
16.  World Dynamic Light Quality
17.  Model Detail
18.  Sync Every Frame
19.  Show Blood
20.  Number of Corpses
21.  Optimal System Settings

SOUND ISSUES
  1.  Issues with Sound Blaster® SB PCI512 sound card
  2.  Issues with EAX® Sound Provider
  3.  Missing Sound Effects on nVidia® nForce™2 Motherboards and Windows® 98

VIDEO ISSUES
  1.  Video Cards
  2.  Multiple Monitors
  3.  16-Bit Color
  4.  16-Bit Textures 
  5.  Recommended Texture Settings for Video Cards
  6.  Setting the Video Resolution
  7.  Disabling Power Saving Features
  8.  Changing the Model Detail Option
  9.  In-game and Desktop resolutions
10.  ATI® Radeon™ 7200 Texture Corruption
11.  ATI® Radeon™ 7200 32MB Sky Texture Corruption at 1024x768 Resolution
12.  ATI® Radeon™ 8500 64MB Blinking/Dropping Textures
13.  ATI® Radeon™ 9000 Texture Popping
14.  Switching Texture Quality on ATI® Radeon™ 9000 Causes Texture Corruption
15.  Matrox® Parhelia™ Missing Geometry & Light Flickering
16.  Matrox® Parhelia™ Users Switching To Windowed Mode In-Game
17.  nVidia® GeForce4™ Full-screen Color Issues
18.  Changing Settings After Player Death In Single Player
19.  Twitchy Graphics When Turning and Strafing
20.  Running Game With Hardware Acceleration Off

GAMEPLAY ISSUES
  1.  Where Are The Autosaves For Each Level?
  2.  Saving and Mission Failure
  3.  Overwriting Saved Games
  4.  Config.cfg File
  5.  Binding the Pause Key to Other Functions

MULTIPLAYER & INTERNET ISSUES
  1.  Problems Finding Internet Games
  2.  Issues When Using Firewall Software
  3.  The Game Freezes When Selecting Multiplayer
  4.  What Are the Map Names for Multiplayer?
  5.  Problems Playing Multiplayer with More Than 32 People
  6.  Game Type Server Settings are Erased When Changing Game Types in Multiplayer
  7.  Problems Adding IP Address to Favorites List
  8.  Locking out a Game Using Password Feature
  9.  Host is booted on a password protected listen server
10.  Hosting Multiplayer on Dialup
11.  Playing Multiplayer on Dialup
12.  Host Appearing In the Vote Kick List
13.  Setting the Pure Server Variable
14.  Hosting Multiplayer on a DSL server
15.  Map Rotation and the Next Map Function

WINDOWS® SPECIFIC OPERATING SYSTEM ISSUES
  1.  Virtual Memory Warnings in Windows® 2000/XP 
  2.  Shift Key in Windows® 2000/XP Interrupts Game
  3.  Windows® Key Interrupts Game in Windows® 2000/XP
  4.  CTRL-ALT-DEL Freezes System on Windows® 2000
  5.  Game Icons Are Missing From Start Menu and/or Desktop
  6.  Admin rights needed to load and play on Windows® 2000/XP

MISCELLANEOUS ISSUES
  1.  Mouse Wheel with Logitech® Mice
  2.  Demo Recording

INTRODUCTION

Refer to this document if you encounter difficulties with one or more aspects of installation or running the Call of Duty™ game.  Many of the most commonly encountered issues are covered here.

IMPORTANT NOTE:  Use of the in-game console is not supported by Activision®.  Please do not contact Activision Customer Support with issues that arise from using console commands in-game.

INSTALLATION & SET UP ISSUES

1.  Minimum System Requirements

·	3D Hardware Accelerator Card required - 100% DirectX® 9.0b compatible 32MB hardware T&L-capable video card and latest drivers*
·	Pentium® III 600MHz or Athlon® 600MHz processor or higher for systems with Windows® 98/ME
·	Pentium® III 700MHz or Athlon® 700MHz processor or higher for systems with Windows® 2000/XP
·	English version of Microsoft® Windows® 98/ME/2000/XP 
·	128MB of RAM 
·	8x Speed CD-ROM drive (1200KB/sec sustained transfer rate) and latest drivers 
·	1.5GB of uncompressed free hard disk space (plus 400MB for Windows® 98/ME swap file, 600MB for Windows® 2000/XP swap file) plus 400mb swap file and 4MB uncompressed hard disk space for XFire™ (Optional).
·	100% DirectX® 9.0b compatible 16-bit sound card and latest drivers
·	100% Windows® 98/ME/2000/XP compatible mouse, keyboard and latest drivers 
·	DirectX® 9.0b (included)

MULTIPLAYER REQUIREMENTS
•	Internet (TCP/IP) and LAN (TCP/IP) play supported
•	Internet play requires 56 Kbps (or faster) modem and latest drivers
•	LAN play requires network interface card and latest drivers

Important Note: *Some 3D accelerator cards with the chipsets listed here may not be compatible with the 3D acceleration features utilized by Call Of Duty.  Please refer to your hardware manufacturer for 100% DirectX 9.0b compatibility.
SUPPORTED CHIPSETS:
·	All ATI® Radeon™ cards
·	All nVidia® GeForce™ chipsets 
•	Matrox® Parhelia™

2.  CD Key

A. Installation and the CD Key

When installing Call of Duty™ you will be prompted to enter your CD authentication key.  The authentication key appears on the CD packaging.  It is important that you enter the key string in its entirety exactly as it appears on the CD package.  The Call of Duty™ Master Server verifies the CD key each time you connect for online play.

B. The game tells me my CD key is invalid:

The number one problem with CD keys is mistyping.  Double and triple check the characters you have entered.

C. Some common sense about your CD key:

Each CD key is unique - protect it from loss or theft by keeping a copy of it in a safe place.  Without it, you cannot reinstall the game or play online.  You may hear of so-called "CD Key generators" being available for illicit download on the Internet.  They do not work as advertised, and often attempt to steal legitimate keys off your machine, reveal personal information or install viruses, worms and/or trojan horses on your machine.  Do not download and/or use them under any circumstances.

D. If you are confused on whether a CD key character is the letter "O" or the number "0", it will most likely be the number "0".  

3.  DirectX Detection & Installation

The Call of Duty™ installer does not check for the version of DirectX you have currently installed, it just prompts you to install DirectX 9.0b.  Activision recommends allowing the installer to proceed with the DirectX 9.0b installation, even if you think you may have 9.0b installed.  Re-installing DirectX 9.0b will not harm your DirectX configuration.  Call of Duty™ requires DirectX 9.0b to install and play.

4.  Error Message:  "Couldn't Load Default.cfg"

If you try to run Call of Duty™ and receive the error message, "Couldn't Load default.cfg,” this indicates that the program cannot find the "\main" directory that is essential to its proper function.  This error commonly occurs when you install the game with no directory specified.  For example, if you choose to install it to a hard drive or partition other than the C: drive (that is, D:,E:, etc.), but fail to specify a folder, the game will install everything to the root of the hard drive and the game will not launch. 

If you want to install the game to a hard drive other than the default setting (C:), please make sure you specify a folder when choosing the other drive (i.e.: D:\Call Of Duty). 

5.  Error message:  “Hunk unable to allocate 128MB of memory”

When a player attempts to launch Call of Duty™ with a full hard drive, the game will not launch and will display the above error message.  To resolve this situation, free up at least 200MB of uncompressed hard drive space to allow Call of Duty™ to function properly.

6.  Splash Screen Will Not Change From "Uninstall" To "Install"

Users who have uninstalled Call of Duty™ and chose to reinstall it may find that the installer splash screen will still stay "Uninstall" instead of "Install" upon relaunch.  To remedy this, use the Windows® search function to locate the "cod.ini" file in the Windows® folder and delete it.  IMPORTANT:  Do not delete any other files from this directory, as it may cause errors with other programs or the Windows® operating system.

7.  Launch Problems on nVidia® nForce™2 Motherboards 

Users who attempt to run the single player portion of Call of Duty™ on a machine with an nVidia® nForce™2 motherboard may encounter an error message that states, "Please insert the correct CD-ROM and select OK to retry."  The error message will remain, even if the proper CD is in the drive.  The solution to this problem depends on your operating system:

Windows® 98, ME and XP users:

If you encounter this problem on Windows® 98, ME or XP, installing the latest nForce™2 drivers (available from your motherboard manufacturer) will remedy the situation.

Windows® 2000 users:

There is a known incompatibility with Macrovision™'s SafeDisc® (the copy protection mechanism Call of Duty™ employs) and motherboards with the nForce™2 chipset under Windows® 2000.  To remedy the situation, do the following:

1) Locate the "My Computer" icon on your computer and right-click it.
2) Choose the "Manage" option.
3) Once the Computer Management program launches, select "Device Manager."
4) In the Device Manager, double-click "IDE ATA/ATAPI Controllers." 
5) Right-click on "nVidia nForce 2(TM) SPP/IGP ATA Controller" and select "Properties."
6) Click on the "Secondary Channel" tab.  If the Select Transfer Mode is set to "BIOS Default," click on the pull-down menu and select "PIO Mode."
7) Close all open windows and restart your machine when prompted.

Call of Duty™ should now launch without incident.

8.  Issues With Installer Properly Switching To Disc 2 During Installation

Some users may find that, when they insert Disc 2 of Call of Duty™ in their CD-ROM drive, it will try to bring up the “splash” screen and not allow the installer to continue.  If this happens, open your CD-ROM or DVD-ROM drive.  Hold down the Left Shift key.  Reinsert Disc 2 of Call of Duty™ and keep the Left Shift key depressed until the CD or DVD drive stops reading the CD.  This will disable the autoplay function of the drive and allow installation to proceed normally.

VIDEO, SOUND & PERFORMANCE OPTIONS

The "Options" menu in Call of Duty™ allows you to adjust a number of different graphic, sound, and general performance settings.  This menu is useful for fine-tuning both the visual quality and overall game performance, in order to maximize player enjoyment and insure smooth play.  Call of Duty™ automatically detects system hardware and sets all values to optimal settings, taking into account your system's processor speed, available system RAM, video card power, video RAM, sound card capabilities, and various other factors.  You may wish to modify these settings, and this section is intended to be a guide to each setting and the impact of changing it.

OPTIONS > SYSTEM > GRAPHICS

1.  Video Mode

Allows you to set the screen resolution for the game; from the minimum setting of 640x480 to the maximum setting of 2048x1536.  IMPORTANT NOTE:  You should not adjust your in-game screen resolution to a setting beyond what your monitor can support.  You should consult your monitor's documentation in order to learn about supported resolutions.

2.  Full Screen

Allows you to choose whether the game will play in full-screen or windowed mode.  When in full-screen mode (select "Yes" to choose this), the game occupies all of the available screen space.  In Windowed mode (select "No" to choose this) the game will play in a window, and the desktop will be viewable in the space around that window.  IMPORTANT NOTE:  It is not recommended to choose an in-game resolution that is higher than your desktop resolution, especially in windowed mode.  You may only be able to see as much of the game as is viewable at your desktop resolution.

3.  Character Textures

Sets the detail level for textures on all character models.  The game will choose the best setting for your system when you launch the game.  If you would like to modify this setting, you can choose from Low, Normal, High, and Extra.  Setting this value to a higher setting than the system chooses for you may hamper game performance.  Likewise, setting this value to a lower setting may improve your game performance.  See the Recommended Texture Settings for Video Cards section for further information.

4.  General Textures

Controls the detail level for all environmental and non-character textures.  As with the character textures setting, Call of Duty™ will choose the optimal setting for your system - Low, Normal, High or Extra.  The higher the setting, the more texture data your system will need to process and render, so set these values to the higher levels only if your system is extremely robust.  See the Recommended Texture Settings for Video Cards section for further information.

5.  Texture Filter

Allows you to choose between bilinear and trilinear filtering for all in-game textures.  If you have a lower-end video card, you should choose bilinear.

6.  Texture Quality

Call of Duty™ will choose the optimal setting for your system.  Please see the 16-bit Textures section for further information.  If you are experiencing performance issues, you can downgrade the texture quality to 16-bit, at the cost of visual quality.

7.  nVidia® Distance Fog

This function simulates the behavior of actual fog and/or mist. GeForce™ 3 video cards and higher support a variety of advanced fog calculations including layered fog, patchy fog and more.  This will not affect GeForce™ 1 or 2 cards, and this option will not be available with a non-GeForce™ card.

8.  Brightness

Allows you to control the brightness ("gamma") level in the game.  Move the slider to the right to increase the gamma, or to the left to decrease.

OPTIONS > SYSTEM > SOUND

9.  Subtitles

This option will enable subtitles to appear whenever other characters say things important to gameplay.

10.  Master Volume

Controls the volume for music, sound effects, and voices.  Move the slider to the right to increase the overall volume of the game.

11.  Sound Quality

Allows you to choose between 44KHz (high), 22KHz (normal) and 11KHz (low) sound quality.  The higher the sound quality, the more memory the sound files require.  If you are experiencing game performance issues, a downgrade in sound quality may help.

12.  Sound Provider

Sets the source for the sound in the game.  Miles™ Fast 2D Positional Audio is the default provider.  If your sound card supports Creative Labs' EAX™, EAX 2™ or EAX 3™audio performance systems, you may want to consider changing your sound provider to the one your card supports.

OPTIONS > SYSTEM > PERFORMANCE

13.  Wall Marks

Allows you to choose whether the game will show bullet marks on the walls.  Setting this to "Off" will improve game performance.

14.  Ejecting Brass

Allows you to choose whether the game will show bullet casings ("brass") ejecting from guns in the game.  Setting this to "Off" will improve game performance.

15.  Dynamic Lights

Allows you to control the level of dynamic lighting in the game.  The "Everything" setting will enable dynamic lights on all surfaces in the game.  "Models Only" will only display dynamic lights on models (and not environments and walls).  "None" will disable all dynamic lighting in the game.  If you want to improve game performance, consider reducing this to "Models Only" or "None."  It will improve performance at the expense of visual quality.

16.  World Dynamic Light Quality

Allows you to further tweak performance settings by giving you the options of "Fastest" or "Nicest" for world dynamic light quality.  On the "Fastest" setting, game performance takes precedent, and all dynamic light effects on world (i.e. environment & wall) textures will be of a slightly less quality.  "Nicest" renders the best dynamic lighting on world textures the game has to offer.  If you are having game performance issues, consider setting this to "Fastest."

17.  Model Detail

Allows you to set the overall detail level for all in-game models.  You can choose from Minimum, Low, Normal, High, and Maximum settings.  Low settings compromise visual quality in favor of performance, so consider changing to a lower setting if you are experiencing game performance issues.

18.  Sync Every Frame

Setting this option to "Yes" will synchronize the game's redraw rate with your monitor's refresh rate.  This will minimize graphical "tearing" at the expense of some performance.

19.  Show Blood

If you prefer not to see blood in the game from wounded or slain soldiers, set this value to "No.”

20.  Number of Corpses

Sets the number of corpses that remain on the battlefield during gameplay.  You can choose from Tiny, Small, Medium, Large, and Insane settings.  Consider reducing this setting to help improve game performance.

21.  Optimal System Settings

This setting will reset all the changes you may have made to the above settings to the values Call of Duty™ deems optimal for your particular system.

SOUND ISSUES

1.  Issues with Sound Blaster® SB PCI512 sound card

If you are using a Sound Blaster® SB PCI512 sound card and enable 22 KHz quality sound, you will experience system slowdown.  Maintain a sound quality setting of 11 KHz for optimum performance with this sound card.

2.  Issues with EAX® Sound Provider

While using a sound card that supports EAX, you may experience occasions of loud sounds while using the EAX sound provider.  To avoid this, and the potential hazard of damaging your speakers, it is recommended that you avoid using a high speaker volume on your sound system in combination with a low Master Volume setting in the Options>Sound menu of Call of Duty™.  Doing so may cause damage to your hearing or speaker hardware.

If possible, you should turn down your speaker volume on your sound system and turn up the Master Volume in the Options>Sound menu to get desired volume levels while playing the game.  If this is not possible, and you are experiencing the problem mentioned above, it is recommended that you switch sound providers in the Options>Sound menu to Miles Fast 2D Positional Audio.

3.  Missing Sound Effects on nVidia® nForce™2 Motherboards and Windows® 98

Users who play Call of Duty™ on a machine with an nVidia® nForce™2 motherboard and Windows® 98 may find that there are no in-game sound effects upon game launch.  Changing the Sound Quality setting (located in the "Options" menu under "Sound") from 44 kHz to 22kHz or 11kHz will restore sound effects in the game.

VIDEO ISSUES

1.  Video Cards

For optimum performance, Call of Duty™ will automatically detect and set your game graphics to recommended settings.  You can customize your settings by going to the "Options" menu from the main menu.

2.  Multiple Monitors

If you are running a machine with multiple monitors and the video card for each monitor is an OpenGL compliant video card (e.g., GeForce™ series cards), you may experience problems running the game, as the game will recognize both video cards.  Simply disable one of the monitors in the Windows® Display Properties.

Playing Call of Duty™ with dual monitors is not a supported feature.

3.  16-Bit Color

Call of Duty™ does not support 16-bit color depth and does not provide this option in the menu system.  Forcing the game to run in 16-bit color through other means may result in graphic corruption and other issues.  To insure you do not inadvertently force the game to 16-bit color, set your desktop's color depth to 32-bit.

1) Open the Control Panel.
2) Double-click Display.
3) Click Settings.
4) Set the color palette to 32-bit.
5) Click Apply, then OK.

NOTE: This issue pertains to 16-bit color, not 16-bit Texture Quality.

4.  16-Bit Textures

Call of Duty™ is optimized for 32-bit (high resolution) color textures.  Since most of the textures and art in the game contain a 32-bit color palette, playing the game using the 16-bit texture quality selection only displays half the color information, thus causing some loss in visual quality.

5.  Recommended Texture Settings for Video Cards

If you are experiencing performance or graphical anomalies, use the texture guidelines below, or select "Optimal System Settings" in the Game Options menu.  This may alleviate the problems you are seeing.

- Video cards with 32MB to 64MB of video RAM are able to use the Normal Character & General Textures settings.
- Video cards with 128MB of video RAM are able to use the High Character & General Textures settings.
- Video cards with 256MB of video RAM are able to use the Extra Character & General Textures settings.

* Video cards with 32MB of video RAM will see improved performance with the Low Character & General Textures settings.

6.  Setting the Video Resolution

If you set your video resolution within the game beyond what is possible for your monitor, the game may end up at a gray or black screen.

To revert to the default configuration, click on the "Play Call of Duty (Safe Mode)" shortcut found in the Start Menu.

IMPORTANT NOTE:  Call of Duty's Safe Mode resets the system settings for optimal performance for your computer.

7.  Disabling Power Saving Features

Allowing a computer to go to "System Standby" while playing or installing Call of Duty™ may cause graphical anomalies.  When playing or installing Call of Duty™, be sure to disable "Stand By" mode by right-clicking the desktop and selecting "Properties".  Click on the "Screen Saver" tab, then on the "Power" (also called "Settings") button at the bottom of the Properties box.  Once you have done this, make sure "System Stand By" is set to NEVER.

You will also want to disable any power saving features your monitor may have as it may result in issues that may prevent you from playing Call of Duty™ properly.

8.  Changing the Model Detail Option

Setting the Model Detail option (in the Performance settings screen) to "Maximum" forces the game to render all displayed geometry, taxing even the most robust computer systems.  Do not set this option to "Maximum" unless you are running on an extremely cutting-edge hardware configuration.  Note that users setting this option to "Minimum" may experience numerous graphical anomalies.  For best performance vs. appearance, this setting should be set to “Normal.”

9.  In-game and Desktop resolutions

Do not choose an in-game resolution that is higher than your desktop resolution.  You may only be able to see as much of the game as is viewable at your desktop resolution.  (For example, if your desktop resolution is set to 1024x768, and you choose an in-game resolution of 1600x1200, the game screen may stretch beyond the size of your monitor screen).  This issue may be more prevalent in windowed mode.

IMPORTANT NOTE FOR ATI® RADEON™ VIDEO CARD USERS:  Call of Duty™ was tested and certified to work on ATI® Radeon™ cards running the Catalyst 3.7 drivers.  Subsequent driver versions may cause unforeseen issues.

10.  ATI® Radeon™ 7200 Texture Corruption

Users playing Call of Duty™ on an ATI® Radeon™ 7200 video card, with settings to Low detail and 16-bit textures, may see black boxes appearing on distant textures.  They also may see graphical corruption on some textures.  These errors are specific to the Radeon™ 7200 video card.

11.  ATI® Radeon™ 7200 32MB Sky Texture Corruption at 1024x768 Resolution

Users playing Call of Duty™ on an ATI® Radeon™ 7200 32MB video card at an in-game resolution of 1024x768 may see corrupted or "blocky" sky textures in a few levels.  To remedy this, either play the game in Safe Mode, or reset your system settings to "Optimal."  These errors are specific to the Radeon™ 7200 32MB card.

12.  ATI® Radeon™ 8500 64MB Blinking/Dropping Textures

Users playing Call of Duty™ on an ATI® Radeon™ 8500 64MB video card, with settings on low detail, may see distant textures dropping out in the Stalingrad level.  They also may see certain textures "blink" out when they shoot at them (such as train wheels).  These errors are specific to the Radeon™ 8500 64MB card.

13.  ATI® Radeon™ 9000 Texture Popping

Users playing Call of Duty™ on an ATI® Radeon™ 9000 video card may see occasional texture popping, especially on the "Sewer" and "Dam" levels.  These errors are specific to the Radeon™ 9000 card.

14.  Switching Texture Quality on ATI Radeon 9000 Causes Texture Corruption

In very rare instances, users playing Call of Duty™ on the ATI® Radeon™ 9000 card that switch the quality of in-game textures to 32-bit while in a level with water causes the water textures to corrupt or disappear.  If this problem occurs, restart the game to restore full texture display function.

15.  Matrox® Parhelia™ Missing Geometry & Light Flickering

Matrox® Parhelia™ users may find parts of some levels missing geometry.  This is due to the Parhelia™ not drawing in-game fog effects, which is causing the graphical anomalies.  Parhelia™ users may also experience light flickering on textures and the player gun model on various levels of the game.

16.  Matrox® Parhelia™ Users Switching To Windowed Mode In-Game

When a user playing Call of Duty™ on a Matrox® Parhelia™ video card attempts to switch from windowed mode to full-screen mode (or vice versa) while in the middle of a game, it may cause graphical corruption (a "hall of mirrors" effect) around the main game window.  To avoid this, choose either full-screen mode or windowed mode from the shell when a game is not in progress.

17.  nVidia® GeForce4™ Full-screen Color Issues

nVidia® GeForce4™ users may experience washed out or otherwise unappealing texture quality when playing the game with High character and general textures settings, 32-bit textures in full screen mode.  If you experience this, adjust the "Image Settings" slider in the GeForce4™ settings menu all the way to "Quality" in order to remedy the situation.  You can do the following:

1) Right-click on the desktop and select "Properties."
2) Choose the "Settings" tab.
3) Click the "Advanced…" button.
4) Select the "GeForce4" tab.
5) Select the "Performance & Quality Settings option from the side menu.
6) Adjust the "Image Settings" slider away from "High Performance" and over to "Quality."
7) Click OK to save your changes and restart Call of Duty™.

18.  Changing Settings After Player Death In Single Player

Adjusting game settings, such as graphics settings or game options, if your single player character is currently dead is not recommended.  Change these options either before you begin the game, or by pressing Escape and going to the menus when your character is alive.  Otherwise, the changes may not take effect.

19.  Twitchy Graphics When Turning and Strafing

You may see vibrating or "tearing" of textures (i.e. a vertical wall appearing torn in two pieces around the middle) while turning your view and strafing (walking sideways) rapidly.  Enable the Vertical Sync option in your video card options screen, and be sure that Vertical Sync is not forced to "Off."  In some cases, Vertical Sync needs to be set to "Default On" or "Always On" to fix this issue.  Enabling Vertical Sync may cause slight performance issues.

20.  Running Game With Hardware Acceleration Off

As Call of Duty is a 3D game, it will not launch unless hardware acceleration is on.  If hardware acceleration is off, you will receive a "Could not load OpenGL.  Make sure that you have the latest drivers for your video card from the manufacturer's web site" error message."  If you receive this message, and you have confirmed that you have the latest drivers for your video card, check to see if hardware acceleration is off.

You can check the status of hardware acceleration in two ways:

Method 1:  Advanced Settings Under Display Properties
1) Open the Control Panel.
2) Double-click Display.
3) Click Settings.
4) Click Advanced.
5) Select the Troubleshooting tab.
6) Verify that Hardware Acceleration is on.

NOTE:  For most systems with supported video cards running the latest drivers and DirectX 9.0b, you should be running Call Of Duty with "Full" acceleration.

Method 2:  Display Settings In DirectX Diagnostic Tool
1) Open the Start Menu and select "Run."
2) Type the word "dxdiag" (with no quotation marks)
3) When the DirectX Diagnostic Tool has finished loading, select the Display Tab.
4) Verify that DirectDraw Acceleration is enabled.  If it is disabled, enable it.
5) Verify that Direct3D Acceleration is enabled.  If it is disabled, enable it.
6) Exit the DirectX Diagnostic Tool to save your changes.

GAMEPLAY ISSUES

1.  Where Are The Autosaves For Each Level?

Call of Duty™ autosaves at the beginning of each single player mission as well as at certain points within each mission.  If you wish to load one of these, you can do so by hitting "Esc" while playing the game and selecting "Load Game" or selecting "Load Game" from the main menu.  Highlight the name of the game you wish to load and the click the "Load" button.

IMPORTANT NOTE:  Call of Duty™ will not create certain autosaves if the player's health is below 40%.  This is to keep from having to continue the game with too little health.

2.  Saving and Mission Failure

If you save your game during a mission failure, you may be unable to load a game from the load screen.  In this case, exit and restart game. You will now be able to load a save game.

3.  Overwriting Saved Games

When saving your game over a previously existing save game file, you will not be able to update the name of the new save game file.

4.  Config.cfg

Your configuration and settings are stored in the config.cfg (or config_mp.cfg for multiplayer).  If you need to reset your configuration, do not delete this file.  Instead, click on the "Play Call of Duty (Safe Mode)" shortcut or select Set Default Controls/Set Optimal Settings from the Options menu.

IMPORTANT NOTE:  Call of Duty's Safe Mode resets the system settings for optimal performance for your computer.

5.  Binding the Pause Key to Other Functions

You will lose the ability to pause the game if the Pause key is bound to any other functionality.  To set "pause" back to the Pause key, make sure the Pause key is not bound to any other function.

MULTIPLAYER & INTERNET ISSUES

1.  Problems Finding Internet Games

If you are having problems seeing servers in the Multiplayer Join Server screen, please make sure that you have checked the following before contacting customer support.

A.) Make sure that you are connected to the Internet (through either a Local Area Network, dial-up connection, etc.).  You must connect to the Internet before starting the game.

B.) Once you have connected to the Internet and started the game, select the “Join Server” option from the main menu and click the “Source” button in the upper left portion of the screen until you see the word “Internet”.  Once you have selected “Internet” as the source, click the “Refresh List” button to the right of the “Source” button.

C.) If you are running firewall software on your system, such as ZoneAlarm®, please refer to the "Issues When Using Firewall Software" section below. 

2.  Issues When Using Firewall Software

If you are using firewall software such as ZoneAlarm® and you are experiencing problems, make sure your firewall software is set to allow UDP packets on port 28960.  Call of Duty™ uses this port for connection, message of the day, server browsing, and so forth.

In general, we do not advise setting up a Call of Duty™ server on a machine that is also either a NAT server (such as Microsoft's Internet Connection Sharing) or set up with ipForwarding for a Local Area Net (LAN) onto the Internet. These machines see clients on your LAN as different addresses from the Internet and thus you cannot authorize these clients. 

NOTE:  Activision Customer Support does not support playing multiplayer through firewalls or shared connections.

3.  The Game Freezes When Selecting Multiplayer

This will sometimes occur if you are not connected to the Internet before selecting multiplayer, and your Internet Service Provider uses "Auto Dial" to connect to the Internet.  Auto Dial is a feature that brings up a dialogue box whenever using Internet applications without being connected to the Internet, the dialogue box will prompt the user to connect to the Internet and ask for their user name and password.

If you use Auto Dial, please make sure you are connected to the Internet before starting Call of Duty™ to prevent your system from hanging.  Contact your Internet Service Provider for more information regarding Auto Dial as it may affect your account and connection.

4.  What Are the Map Names for Multiplayer?

If you are running a dedicated server for multiplayer, you can use the filenames listed below to load the corresponding maps for your server.  Maps can be loaded by typing directly into the server console on the host machine, or via the "\rcon" command for remote servers.  To load a map the server must execute the "map <filename>" command.

Map Name = File Name

Brecourt = mp_brecourt
Carentan = mp_carentan
Chateau = mp_chateau
Dawnville = mp_dawnville
Depot = mp_depot
Harbor = mp_harbor
Hurtgen = mp_hurtgen
Pavlov = mp_pavlov
POW Camp = mp_powcamp
Railyard = mp_railyard
Rocket = mp_rocket
Ship = mp_ship

NOTE:  mp_chateau and mp_ship do not support the Search & Destroy multiplayer game type.

5.  Problems Playing Multiplayer with More Than 32 People

The multiplayer maps created for Call of Duty™ do not support more than 32 players on a server, or more than 16 players per team, with the exception of the Behind Enemy Lines game type.  The maps have limited spawn points available.  With more than 16 players on a team, you will experience instances of telefragging (causing them to have to respawn).

If you are operating a server with more than 32 people, or more than 16 per team, do so at your own risk.

6.  Game Type Server Settings are Erased When Changing Game Types in Multiplayer

When you change the game type from the Start Server screen, the settings under the Game Type Settings menu will be reset without warning.  This was done to prevent bad configurations from occurring.  Server settings vary for each game type.

7.  Problems Adding IP Address to Favorites List

To get a server into your Favorites list, set the "Source" in the server browser to "Favorites" and then select "New Favorites,” and enter the server information.

8.  Locking Out a Game Using Password Feature

If the "Password" field is blank in the Start New Server screen, the server will not check for a password.  If it is not blank, the server will use the password listed in the field.  If you wish the server to have a password, you should type one in; if not, do not enter one, or delete it if you have set one before.

9.  Host is booted on a password protected listen server

If you are running a listen server with a password, you may encounter the server being booted after a Call Vote. To work around this issue, before the vote, do the following:
1. Display the console by hitting “`.”
2. Type "\password <server password>" where server password is the password you have set for the server.

10.  Hosting Multiplayer on Dialup

Activision does not support hosting games on a dialup Internet connection.

11. Playing Multiplayer on Dialup

If you are playing Call of Duty™ multiplayer on a dialup modem, please note that you are limited to playing games with a maximum of 8 players due to the limited amount of bandwidth available on a dialup connection. 

12.  Host Appearing In the Vote Kick List

When using the Vote Kick option you will not be able to kick the host.  You will only be able to vote off players who have joined a game.  

13.  Setting the Pure Server Variable

Altering the sv_pure setting at any time after starting the server is detrimental to all clients.  The ONLY legitimate method of activating or deactivating Pure Server is to switch the Pure setting to "Yes" on the Start Server screen.

14.  Hosting Multiplayer on a DSL server

If you are hosting a Call of Duty™ Multiplayer game on a DSL server, you will be limited to a maximum of 8 clients due to the limited bandwidth available on a DSL connection.

15.  Map Rotation and the Next Map Function

All players in a multiplayer game have an opportunity to call votes for map changes, game type changes, etc.  If a player calls a vote for "Next Map" and the server administrator did not specify a map rotation, the current map will simply restart if the vote passes.  Server administrators that wish to take advantage of the Next Map function should enable a map rotation.

The following map rotation configurations are available:
Server_re.cfg - Retrieval 
Server_bel.cfg - Behind Enemy Lines
Server_sd.cfg - Search & Destroy
Server_dm.cfg - Deathmatch
Server_tdm.cfg - Team Deathmatch

To load a map rotation, perform the following steps:

1) Start a dedicated or listen server using the Shell.
2) If using a listen server, when the server is up, press the ~ key to pull down the console.
3) Type \exec server_sd.cfg in the console.  If using a dedicated server, type exec server_sd.cfg (use whichever configuration matches the server’s gametype)
4) Once the configuration file is executed, the rotation will be loaded. 

In addition to having players call a “Next Map” vote, server admins can use the map_rotate command on a dedicated server (or \map_rotate on a listen server) to take users to the next map as defined by the currently executed config file.

WINDOWS® SPECIFIC OPERATING SYSTEM ISSUES

1.  Virtual Memory Warnings in Windows® 2000/XP

Users playing on machines using the Windows® 2000/XP operating systems that possess less than 600 megabytes (MB) of virtual memory may receive low virtual memory warnings.  To avoid these warnings, please make sure you set your virtual memory settings to at least 600 megabytes (MB).

To adjust your virtual memory settings, please do the following:

For Windows® XP systems:
1) Right click the My Computer icon.
2) Select Properties.
3) Select the Performance tab.
4) Select Virtual Memory.

For Windows® 2000 systems:
1) Right click the My Computer icon.
2) Select Properties.
3) Select Advanced.
4) Select Performance Options.

2.  Shift Key in Windows® 2000/XP Interrupts Game

If you press the Shift key 5 times consecutively in Windows® 2000 or Windows® XP the following message should appear:

"By pressing the SHIFT key five times you have turned on the StickyKeys feature in Windows® 2000 [or Windows® XP].  With this feature, you can lock down the CTRL, ALT, or SHIFT keys.  This is useful if you are unable to hold down more than one key at a time.

Click OK to turn this feature on.  If you do not want to use the feature, click Cancel.

<check box> Turn off keyboard shortcut for this accessibility feature.

<OK>
<CANCEL>
<SETTINGS>"

To avoid this happening in the future, click the Settings button on the window referenced above.  When the accessibility options screen appears, click the "Settings" button in the "Sticky Keys" portion of the window.  On the next window (should be labeled "Settings For Sticky Keys"), uncheck in the box that says, "Use shortcut,” then click on "Apply,” and close the windows.  The problem should not occur once the shortcut has been disabled.

3.  Windows® Key Interrupts Game in 2000/XP

If the Windows® key is pressed during game play, the Start Menu will interrupt the game.  Should this happen, simply press the Escape (Esc) key to close the menu and return to the game.  Unfortunately, there is no way to prevent this from happening again except by being careful not to hit those keys while playing.

4.  CTRL-ALT-DEL Freezes System On Windows® 2000

If the CTRL-ALT-DEL keys are pressed during game play, the screen will become corrupt and sometimes the system may become unstable.  Should this happen, simply press the Escape (Esc) key to return to the game or reboot the computer and refrain from trying to access the task manager while playing the game.

5.  Game Icons Are Missing From Start Menu And/Or Desktop In Windows® 2000/XP

When installing Call of Duty™ while logged into Windows® as a specific user, the game icons will only show up when logging in as that user.  For example, if you log into Windows® as "Joeuser", install the game, then log out and log back in as "Janeuser", the game icons will not show up.  If you wish to play the game, make sure you log into Windows® as the same user you were logged in as when you installed the game.

6.  Admin Rights Needed To Load and Play On Windows® 2000 or XP

If you are running Windows® 2000 or Windows® XP, you must have Administrator rights to properly install and play the game.

MISCELLANEOUS ISSUES

1.  Mouse Wheel with Logitech® Mice

People having problems with the "mousewheel" on Logitech® mice should grab the latest version of Logitech's drivers from the following location:

http://www.logitech.com/

In addition to the latest version of "Mouseware" drivers, you will need to download the "Mouse Registry File for Gamers" which will allow the "mousewheel" to work within Call of Duty™.

Note: Although "Mouse Registry File for Gamers" is not listed as being needed under Windows® Millennium Edition you will still need to download it in order to get the correct functionality from the wheel.

Please contact Logitech® support if you are unable to find this file on their website.

2.  Demo Recording

Demo recording is not supported in either single player or multiplayer play modes.  The console commands for demo recording are still present in the game, but when executed they will not yield the expected results.

<END DOCUMENT>