X

Burnout 2: Point of Impact Latest News - PS2

Game Description:Burnout 2 has all the demolition and racing action of the original Burnout, plus more! More cars -- there are 14 new vehicles to choose from, plus seven secret vehicles to unlock during the game. More road -- there are 30 new stages, plus six new U.S. locations including Los Angeles, Miami, The Rockies, New Mexico, and an airport. New features -- now you'll have to handle weather effects and drive through a few training levels before taking on the big boys. Earn boosts by jumping high! Invite over a friend for multiplayer match-ups.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Burnout 2: Point of Impact 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>