X

Burnout 3: Takedown Latest News - XBX

  • Publisher: Electronic Arts
  • Genre:Racing
  • Developer: Criterion Games
  • Release Date:Sep 8, 2004
  • # of Players:2 players
  • ESRB:T - Teen (Titles rated "Teen (T)" may be suitable for ages 13 and older, and may contain violent content, mild, or strong language, and/or suggestive themes.)
  • Platforms:
Game Description:Electronic Arts has put its muscle behind the Burnout series. Burnout 3 features amazing graphics, adrenaline-pumping gameplay and awesome crash dynamics. In eye-peeling races you'll weave through crowded streets, dive through tunnels and hug dangerous turns. Sound is always key to any good racing games, and EA pumps up the ear candy to pull racers deep into Burnout 3's raw intensity. But Burnout 3's key attraction is its epic 100-plus crash sections! New modes include the online two-player Crash mode, Double Impact, Road Rage and the 6-player Crash Party.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Burnout 3: Takedown News

Displaying 1–1 of 1 articles

  • Criterion Games' Need For Speed Described As "Action" Oriented

    Electronic Arts and Criterion Games keep teasing about what the Burnout developer has planned for their reinvention of Need For Speed. But we have a slightly better idea of what's coming. John Schappert, who left EA to join Microsoft before returning to EA last year as COO, described the upcoming collaboration as an "action-based Need For...

    Posted February 8, 2010

    Criterion Games' Need For Speed Described As "Action" Oriented

 


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>