X

Duke Nukem Forever Screenshots and Images - PS3

  • Publisher: 2K Games
  • Genre:Shooter
  • Developer: Gearbox Software
  • Release Date:Jun 14, 2011
  • # of Players:1 player, 8 online
  • ESRB:M - Mature (Blood and Gore, Intense Violence, Mature Humor, Nudity, Strong Language, Strong Sexual Content, Use of Drugs and Alcohol)
  • Platforms:
Game Description: Duke Nukem Forever brings back the king of action in a highly anticipated game set to pummel players with unprecedented interactivity, variety, realism, and Duke's special whoop-ass brand of humor.
G4TV Rating
1 / 5
  • Avg User Rating
    (51 Ratings)
    3.3 / 5
  • Rate This Game

Duke Nukem Forever Screenshot & Image Galleries

  • Top 5 G4tv.com Gaming Videos of 2011

    Posted: December 21, 2011

    14,435 Views | 01:32

  • X-Play's Top 5 Shocking Videogame Moments of 2011

    Posted: December 21, 2011

    18,810 Views | 02:09

  • Face Time: Gearbox Software's Randy Pitchford

    Posted: September 7, 2011

    20,015 Views | 03:38

  • Duke Nukem Forever Ego Boost Tips and Cheats

    Posted: August 24, 2011

    27,642 Views | 02:35

  • X-Play's Most Patriotic Games

    Posted: July 5, 2011

    4,854 Views | 03:25

 


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>