X

Halo: Reach Videos and Trailers - Xbox 360

  • Publisher: Microsoft
  • Genre:Shooter
  • Developer: Bungie
  • Release Date:Sep 14, 2010
  • # of Players:1 player, 16 online
  • ESRB:M - Mature (Blood,Violence)
  • Platforms:
Game Description:Halo: Reach, developed exclusively for Xbox 360 by acclaimed developer Bungie, is the blockbuster prequel to the best-selling Xbox franchise of all time. It represents the culmination of Bungie’s 10 years of experience crafting groundbreaking Halo games. In Halo: Reach, players experience the fateful moments that forged the Halo legend. It’s the story of Noble Team, a squad of heroic Spartan soldiers, and their final stand on planet Reach, humanity’s last line of defense between the terrifying Covenant and Earth. This darker story is echoed by grittier visuals amid a backdrop of massive, awe-inspiring environments. Characters, enemies and environments are rendered in amazing detail by an all-new engine designed to deliver epic-scale encounters against the cunning and ruthless Covenant.
G4TV Rating
5 / 5
  • Avg User Rating
    (277 Ratings)
    4.6 / 5
  • Rate This Game

Halo: Reach Videos

Displaying 91–105 of 154 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>