X

Call of Duty 3 Latest News - Xbox 360

Game Description:One of World War II's most epic campaigns, the liberation of Paris, gets epic next-generation treatment in Call of Duty 3. Step into a breathtaking, seamless storyline as four ordinary Allied soldiers thrust into an extraordinary situation, the Normandy Breakout. An all-new close-quarters battle mechanic lets you fight hand-to-hand, rig impromptu bombs, disarm traps, and perform other keys to battlefield survival. Branching mission paths with multiple attack routes and distinct tactical requirements let you choose to outflank your enemy or overpower him head on. Environmental physics means there's nowhere to hide. Cover, both yours or your enemy's, can be destroyed. Up to 24 can battle in team-based multiplayer with vehicles. Read our full interview with Treyarch's Creative Director, Rich Farrelly.
G4TV Rating
N/A
  • Avg User Rating
    (4 Ratings)
    3 / 5
  • Rate This Game

Call of Duty 3 News

Displaying 31–31 of 31 articles

  • Activision Claims Infinity Ward Only 'CoD' Rumors False

    Following rumors that Infinity Ward had renegotiated its contract with Activision to become the sole-developer of Call of Duty games after the release of Call of Duty 5. Call of Duty 5 will be developed by Treyarch, the developers of CoD3. The rumors included a mention of a spin-off series that might not even be a first-person shooter. A former...

    Posted April 22, 2008| 41 Comments

    Activision Claims Infinity Ward Only 'CoD' Rumors False

 


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

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

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

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