X

The Chronicles of Riddick: Escape from Butcher Bay Videos and Trailers - XBX

  • Publisher: Vivendi Universal
  • Genre:Action, Adventure, Shooter
  • Developer: Starbreeze AB
  • Release Date:Jun 2, 2004
  • # 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:Chronicles of Riddick: Escape from Butcher Bay is tailor-made for fans of the 2000 sci-fi cult film Pitch Black, starring Vin Diesel. As a prequel to both Pitch Black and the 2004 Chronicles of Riddick sequel, Escape from Butcher Bay tells the origin story of our rough anti-hero, Riddick. As Riddick, you will escape Butcher Bay and acquire superhuman powers. You will even learn how Riddick had his eyes shined by Pope Joe. Chronicles of Riddick: Escape from Butcher Bay also makes use of cutting-edge game design using Normal-Mapping, Per-Pixel Shading and Dynamic Lighting.
G4TV Rating
N/A
  • Avg User Rating
    (1 Rating)
    4 / 5
  • Rate This Game

The Chronicles of Riddick: Escape from Butcher Bay Videos

Displaying 1–1 of 1 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>