X

BioShock 2 Screenshots and Images - Xbox 360

  • Publisher: 2K Games
  • Genre:Shooter
  • Developer: 2K Marin
  • Release Date:Feb 9, 2010
  • # of Players:1 player, 10 online
  • ESRB:M - Mature (Blood,Intense Violence,Sexual Themes,Strong Language)
  • Platforms:
Game Description:Return to the undersea city of Rapture, following the dramatic events of the first BioShock. Step into a Big Daddy suit with a rivet gun, drill and new plasmid powers at your disposal, as you fight to survive against the new "Big Sister" and a host of new freakish enemies, while you search for and protect the remaining Little Sisters. The game also features competitive multiplayer for the first time.
G4TV Rating
4 / 5
  • Avg User Rating
    (77 Ratings)
    4.5 / 5
  • Rate This Game

BioShock 2 Screenshot & Image Galleries

  • Best of 2010: Best Shooter

    Posted: December 14, 2010

    24,507 Views | 01:49

  • Best of 2010: Best DLC

    Posted: December 14, 2010

    18,140 Views | 00:54

  • Holiday Buyers Guide - Must Have Shooters

    Posted: November 23, 2010

    16,976 Views | 02:49

  • Bioshock 2 Minerva's Den Debut Trailer

    Posted: August 26, 2010

    13,587 Views | 01:16

  • Sessler's Soapbox: The World Makes the Game

    Posted: August 17, 2010

    33,314 Views | 05:07

 


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>