Lost Planet 2 Screenshots and Images - Xbox 360

  • Publisher: Capcom
  • Genre:Action, Adventure
  • Developer: Capcom
  • Release Date:May 11, 2010
  • # of Players:1 player, 16 online
  • ESRB:T - Teen (Animated Blood,Language,Suggestive Themes,Violence)
  • Platforms:
Game Description: Taking place 10 years after the events of Lost Planet, this third-person action title takes players back to the now lush environs of E.D.N. III as they battle, from multiple perspectives, for control of valuable natural resources. In addition to a compelling single-player campaign, the game also features four-player online co-op and a robust character customization system.
G4TV Rating
3 / 5
  • Avg User Rating
    (15 Ratings)
    3.7 / 5
  • Rate This Game

Lost Planet 2 Screenshot & Image Galleries

  • The Big Games of Spring 2010

    Posted: April 8, 2010

    12,945 Views | 02:55

  • Lost Planet 2 Early Demo Access Direct-Feed Gameplay

    Posted: April 2, 2010

    4,402 Views | 15:42

  • Lost Planet 2 Desert Multiplayer Trailer

    Posted: March 31, 2010

    3,115 Views | 06:08

  • Lost Planet 2 Multiplayer Trailer

    Posted: March 29, 2010

    3,860 Views | 05:10

  • Lost Planet 2 Kill Big Trailer

    Posted: March 9, 2010

    5,528 Views | 04:02


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