X

BAJA: Edge of Control Screenshots and Images - Xbox 360

  • Publisher: THQ
  • Genre:Racing
  • Developer: 2XL Games
  • Release Date:Sep 23, 2008
  • # of Players:1 player, 10 online
  • ESRB:E - Everyone (Mild Lyrics)
  • Platforms:
Game Description:Ever race cars through a backyard or schoolyard sandbox? Well, imagine if that sandbox were 100 square miles in size! That's what you've got in BAJA: Edge of Control. Take your pick from more than 40 racers, including 4x4s, Buggies, and Trophy Trucks as you learn the skills you need to compete in the world's most grueling off-road challenge: The Baja. Master the hill-climb, compete in circuit races, and and rise through the ranks. Fine-tune your machine with more than 200 authentic parts. Marvel at eye-popping vistas, looming mountains, and uncomfortably steep cliffs on the expansive landscape.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game
  • Baja: Edge of Control All Access

    Posted: September 25, 2008

    2,368 Views | 02:40 | 2 Comments

  • Baja: Edge of Control Trailer

    Posted: September 21, 2008

    172 Views | 04:43

  • Baja: Edge of Control Designer Interview

    Posted: August 15, 2008

    2,234 Views | 02:04 | 2 Comments

 


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>