X

Resistance 2 Screenshots and Images - PS3

Game Description:When an unstoppable force seems determined to destroy mankind, what can humanity do but keep fighting? Step back into the boots of Nathan Hale as you battle, not only the seemingly impossible Chimera, but the Chimera disease coursing through your body. Explore the alternate 1953 American landscape. Bring familiar weapons and a cache of new ones to bear against an undaunted enemy. First, play through the full-length single-player campaign. Next join up with seven others online for an unprecedented class-based eight-player co-op campaign with a separate, parallel story line. Then take on up to 60 players in massive online battles with a squad-based focus to balance the game and encourage rivalries!
G4TV Rating
N/A
  • Avg User Rating
    (25 Ratings)
    4.3 / 5
  • Rate This Game

Resistance 2 Screenshot & Image Galleries

  • X-Play Best of 2008: Best Multiplayer Game

    Posted: December 9, 2008

    6,421 Views | 01:54 | 4 Comments

  • X-Play Best of 2008: Best Gameplay Innovation

    Posted: December 9, 2008

    4,030 Views | 02:07 | 2 Comments

  • Cheat: Resistance 2: Finding Intel

    Posted: December 8, 2008

    8,099 Views | 01:35 | 1 Comment

  • Mr. Sark: 'Resistance 2' Plantation Level Walkthrough

    Posted: December 3, 2008

    2,219 Views | 03:17 | 7 Comments

  • Resistance 2 TV Spot

    Posted: November 18, 2008

    4,863 Views | 00:30

 


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>