MX vs. ATV Alive Previews - Xbox 360

  • Publisher: THQ
  • Genre:Racing
  • Developer: Rainbow Studios
  • Release Date:May 10, 2011
  • # of Players:1 player, 12 online
  • ESRB:E - Everyone (Mild Language, Mild Suggestive Themes, Mild Violence)
  • Platforms:
Game Description: Own the competition as you wrestle for position with tightly contested racing in the fifth iteration of the MX vs ATV franchise. Feel the realism of the revolutionary real-world physics engine which has defined the racing genre. Live the sport as Alive captures the spectacle of motocross and the essence of competitive racing while providing the best riders and gear from the latest manufacturers.
G4TV Rating
  • Avg User Rating
    (1 Rating)
    5 / 5
  • Rate This Game

MX vs. ATV Alive Previews

Displaying 1–1 of 1 previews

Sort by: Filter by:
All Categories
  • Preview

    MX vs. ATV Alive Hands-On Preview -- Big Air, Muddy Faces, and Close Calls

    Secure those mud visors and tighten those boots as we take our first hands-on look at THQ's latest motorcross title.

    Posted: Apr 7, 2011

  • MX vs ATV Alive Launch Trailer

    Posted: May 9, 2011

    1,476 Views | 00:30

  • MX vs. ATV Alive "What Are Whoops" Video

    Posted: April 28, 2011

    1,001 Views | 01:06


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