X

Crackdown Videos and Trailers - Xbox 360

  • Publisher: Microsoft
  • Genre:Action, Adventure
  • Developer: Realtime Worlds
  • Release Date:Feb 20, 2007
  • # of Players:1 player, 2 online
  • ESRB:M - Mature (Blood and Gore,Intense Violence,Sexual Themes,Strong Language,Use of Drugs)
  • Platforms:
Game Description:The action-driving hybrid has been enhanced - genetically enhanced - in this explosive creation from the mind behind Grand Theft Auto. Pacific City is being strangled by crime and the only hope is the Agency and its genetically enhanced agents. In a world of revolutionary scale, explore Pacific City's full width, depth, and height as you fight crime by any means necessary. Pull off impossible stunts like insane leaps, super-human speed, bone-shattering blows, impossible vehicular maneuvers, and other moves you'll have to see to believe. Add over 100 licensed songs, doubly intense co-op play, and more, and the war-on-crime game has officially evolved. You ready?Read our full interview with Realtime Worlds' Dave Jones in the GameFly 10Q.
G4TV Rating
N/A
  • Avg User Rating
    (11 Ratings)
    4.8 / 5
  • Rate This Game

Crackdown Videos

Displaying 1–14 of 14 videos

 


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>