X

Tom Clancy's Rainbow Six Critical Hour Videos and Trailers - XBX

  • Publisher: Ubisoft
  • Genre:Shooter
  • Developer: Ubisoft Quebec City
  • Release Date:Mar 16, 2006
  • # of Players:16 players
  • 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:It's the end of an era. John Clark is retiring, handing control of Team Rainbow over to his longtime counterpart Ding Chavez. The result is the most comprehensive Rainbow Six saga yet, with the best of the franchise's past recharged for modern gaming. Fans have chosen seven single-player missions from the original Rainbow Six and Rogue Spear sagas, returning Rainbox Six to its more tactical roots. Combat terrorists around the globe using over 20 weapons. Accuracy is effected by injuries and actions (like running). Infiltrate non-linear levels where close-quarter battles await. Online multiplayer includes 18 additional levels spanning the revolutionary Persistent Elite Creation Mode and new Free-For-All and Assassin Modes.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Tom Clancy's Rainbow Six Critical Hour 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>