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 Direct-Feed Warthog Ride Gameplay

    Posted: October 5, 2009

    1,886 Views | 06:58

  • Halo 3: ODST Direct-Feed Tank Gameplay

    Posted: October 5, 2009

    1,465 Views | 05:05

  • Halo 3: ODST Direct-Feed Mombasa Street Fight Gameplay

    Posted: October 5, 2009

    1,571 Views | 05:45

  • The Making of the Halo 3: ODST Live Action Short

    Posted: September 30, 2009

    19,826 Views | 04:41

  • T-Squared Helps ODST Noobs

    Posted: September 28, 2009

    8,382 Views | 02:22


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