Call of Duty: World at War Screenshots and Images - Xbox 360

  • Publisher: Activision
  • Genre:Shooter
  • Developer: Treyarch
  • Release Date:Nov 12, 2008
  • # of Players:1 player, 18 online
  • ESRB:M - Mature (Blood and Gore,Intense Violence,Strong Language)
  • Platforms:
Game Description:Call of Duty: World at War re-creates history while making some of is own. Built using the same engine that delivered jaw-dropping visuals in COD: Modern Warfare, World at War sends you to new battlefronts, including the Pacific Theater, where you'll fight as American Marines or Russian infantry. Battle on multiple fronts against ruthless new enemies, some never-before-seen in a COD game. Cinematic visuals are here, along with improved squad-based multiplayer. But World at War truly makes its mark with the addition of co-op play for the first time in Call of Duty history. Coordinate two-player assaults on local split-screens or join with up to four online.
G4TV Rating
  • Avg User Rating
    (43 Ratings)
    4.2 / 5
  • Rate This Game
  • Call of Duty: World at War Verruckt Just the Beginning

    Posted: March 24, 2009

    7,312 Views | 02:14 | 5 Comments

  • Call of Duty: World at War Map Pack 1 Trailer

    Posted: March 19, 2009

    8,400 Views | 01:45 | 4 Comments

  • Will Work For Games: Call of Duty: World at War

    Posted: March 3, 2009

    4,697 Views | 02:57 | 4 Comments

  • Pro Tips With Tsquared: Call of Duty: World At War

    Posted: January 13, 2009

    15,486 Views | 02:19 | 23 Comments

  • Gaming Update 1.13.09

    Posted: January 13, 2009

    1,958 Views | 02:06


Runtime Error

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

        <customErrors mode="Off"/>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>