X

Tom Clancy's Ghost Recon 2 Summit Strike Videos and Trailers - XBX

  • Publisher: Ubisoft
  • Genre:Shooter
  • Developer: Red Storm Entertainment
  • Release Date:Aug 3, 2005
  • # of Players:4 players
  • ESRB:T - Teen (Titles rated "Teen (T)" may be suitable for ages 13 and older, and may contain violent content, mild, or strong language, and/or suggestive themes.)
  • Platforms:
Game Description:Ghost Recon 2 goes deep behind enemy lines with new features in Summit Strike. In the single-player story, a wealthy Pakistani warlord is amassing an army to take over Kazakhstan, and the UN is powerless. The Ghosts are sent on 11 covert missions to capture the warlord alive and avert an international crisis. An array of weapons like the modular SCAR rifle helps you to neutralize objectives in forests, desert canyons, and the Arctic. Multiplayer mode features two new game types: the cooperative-only Heli Hunt, and Armor Strike, which lets you call in laser-guided air strikes on enemy tanks. Sweat through fierce firefights in beautifully rendered maps like the Government District and Badlands Fortress.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Tom Clancy's Ghost Recon 2 Summit Strike Videos

Displaying 1–1 of 1 videos

 


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>