X

Burnout Revenge Latest News - Xbox 360

Game Description:It's automotive anarchy in this race for vengeance that ignores everything your driver's education taught you. Ram your way through traffic, create massive pileups, and lay waste to everything in sight on tracks designed to cause trouble. The vengeance meter rewards you for playing dirty. Three car classes have distinctive destructive characteristics and enlarge as they grow more powerful. Rage against the clock in Traffic Attack Mode or get personal in a heated Grudge Match. The sequel to the 2004 Racing Game of the Year, Burnout Revenge features real-world locations and more car destruction than ever. Online play is available for up to six players, so you can make enemies all over the world.
G4TV Rating
N/A
  • Avg User Rating
    (3 Ratings)
    4.3 / 5
  • Rate This Game

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