X

Dead to Rights II: Hell to Pay Previews - PS2

  • Publisher: Namco
  • Genre:Shooter
  • Developer:
  • Release Date:Apr 13, 2005
  • # of Players:1 player
  • ESRB:M - Mature (Titles rated "Mature (M)" may be suitable for ages 17 and older. They may include more intense violence or language than products rated "Teen" as well as mature sexual themes.)
  • Platforms:
Game Description:There's gonna be hell to pay! Officer Jack Slate and his trusty K-9 partner Shadow return in Dead to Rights II. This third-person action shooter won't disappoint! The storyline takes place before the first Dead to Rights game. After a judge is kidnapped, it's up to you to take care of business. You'll have 25 brutal disarm moves at your disposal, as well as a stocked arsenal (rocket launchers, grenades, molotovs, etc.), and a melee fighting system (wield bats, pipes, chainsaws, meat cleavers, machetes, and swords). It's up to you to rid Grant City of crime and corruption!
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Dead to Rights II: Hell to Pay Previews

Displaying 1–1 of 1 previews

Sort by: Filter by:
All Categories
  • Video Preview

    Namco Booth Report

    Blair Herter hits the Namco booth at E3 2009 to give us a report on the new 'Dead to Rights' game, as well as 'Soul Calibur: Broken Destiny' for the PSP, and the rest of the roster.

    Posted: Jun 3, 2009 | 510 Views | 02:09


  • Namco Booth Report

    Posted: June 3, 2009

    510 Views | 02:09

 


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>