Halo 3: ODST Screenshots and Images - Xbox 360

  • Publisher: Microsoft
  • Genre:Action, Shooter
  • Developer: Bungie
  • Release Date:Sep 22, 2009
  • # of Players:1 player, 16 online
  • ESRB:M - Mature (Blood,Language,Violence)
  • Platforms:
Game Description: Step into the combat boots of an Orbital Drop Shock Trooper (ODST), sent into the destroyed city of New Mombasa to investigate what happened to the city, its citizens, and the other soldiers sent to defend it. For the first time in the franchise's history, players will see the Halo universe from outside Master Chief’s perspective, as they experience the events leading up to Halo 3.
G4TV Rating
5 / 5
  • Avg User Rating
    (196 Ratings)
    4.1 / 5
  • Rate This Game

Halo 3: ODST Screenshot & Image Galleries

  • Halo 3: ODST Discussion

    Posted: September 21, 2009

    3,938 Views | 03:01

  • Halo 3: ODST First 15 Direct-Feed Gameplay

    Posted: September 21, 2009

    10,295 Views | 15:09

  • Adam Sessler Interviews PAX 2009 Storytellers Panelists

    Posted: September 21, 2009

    1,713 Views | 10:01

  • Halo 3: ODST Review

    Posted: September 19, 2009

    60,753 Views | 03:29

  • Halo 3: ODST Soundtrack - 'ODST Theme'

    Posted: September 18, 2009

    19,619 Views | 01:48


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 -->

        <customErrors mode="Off"/>

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 -->

        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>