Call of Duty 5: Beta Errors: Difference between revisions

From COD Modding & Mapping Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
==General==
==General==


===Directx Errors===
=== Directx Errors ===


* If you run a Windows Server 2003 and are getting the DX error get the DX9 files [http://wiki.modsrepository.com/codww_betafiles/codww_dx_server.zip HERE]
* If you run a Windows Server 2003 and are getting the DX error get the DX9 files [http://wiki.modsrepository.com/codww_betafiles/codww_dx_server.zip HERE]
Line 35: Line 35:
[http://www.nvidia.com/Download/index.aspx?lang=en-us NVIDIA]
[http://www.nvidia.com/Download/index.aspx?lang=en-us NVIDIA]


=== Sounds errors===
=== Sounds Errors===


*Update your audio drivers (Google "[make of audio card] [model # of audio card] Drivers").
*Update your audio drivers (Google "[make of audio card] [model # of audio card] Drivers").

Revision as of 16:19, 29 October 2008

General

Directx Errors

  • If you run a Windows Server 2003 and are getting the DX error get the DX9 files HERE
  • If yo encounter a DX error in Either Windows XP or Vista (32Bits) then get the Latest DirectX 9.0c update:

HERE

  • Some report that placing this file (d3dx9_37.dll) in the game folder also solve some issues.

Possible errors include:







  • Upgrading to latest Graphics Drivers is also recommended:

ATI

NVIDIA

Sounds Errors

  • Update your audio drivers (Google "[make of audio card] [model # of audio card] Drivers").

G_SPAWN entities server crash

  • This issue seems to be only on mp_castle. Its affecting TDM and SD as far as we know. A possible solution:
think this is an issue when you have a lot of players spwaning at once. Yes, that tends to be when the server is full but not always. For example, if you reduce the spawn delay then a group of people all spawn at once you will be more likely to get this error.

I believe it is an issue with the amount of spawnpoints on the maps and the spawn logic used. JD said earlier that the spawn system sees spawnpoints as obstructed if an enemy player is too close to the spawn point. This means it can not use that spawnpoint. Add in ten people trying to spwan at once and you get the issue.

This quote comes from Callofduty.com