The Darkness 2 Screenshots and Images - PC

The Darkness 2
  • Publisher: 2K Games
  • Genre:Action, Shooter
  • Developer: Digital Extremes
  • Release Date:Feb 7, 2012
  • # of Players:1 player
  • ESRB:M - Mature (Blood and Gore, Drug Reference, Intense Violence, Strong Language, Strong Sexual Content)
  • Platforms:
Game Description:It’s been two years since Jackie Estacado, now the Don of the Franchetti crime family, used The Darkness to kill the men responsible for his girlfriend’s murder. He’s been unable to shake the memory of Jenny’s death since bottling up his supernatural power, and now The Darkness wants out. A sudden, unprovoked attack on Jackie’s life heralds the start of a full-scale mob war, which has clearly been orchestrated by some outside force. The botched attempt opens the door for The Darkness to reemerge, and sets Jackie on a journey to hell and worse, as he unravels the mystery behind the attack and the motivations of The Darkness itself.
G4TV Rating
4 / 5
  • Avg User Rating
  • Rate This Game
  • The Darkness 2 Video Review

    Posted: February 13, 2012

    12,838 Views | 03:01

  • Darkness 2: All Executions Video

    Posted: February 8, 2012

    8,567 Views | 01:36

  • First 15: The Darkness 2

    Posted: February 7, 2012

    4,367 Views | 15:01

  • The Darkness 2 Launch Trailer

    Posted: January 24, 2012

    16,949 Views | 01:44

  • The Darkness 2 Demo Gameplay Video

    Posted: January 18, 2012

    4,178 Views | 14:54


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