X

Need for Speed: Carbon Videos and Trailers - XBX

  • Publisher: Electronic Arts
  • Genre:Racing
  • Developer: Black Box
  • Release Date:Nov 1, 2006
  • # of Players:2 players
  • ESRB:U - Unknown (Titles rated "Everyone 10+ (E10+)" may be suitable for ages 10 and older. They may contain cartoon, fantasy, or mild violence, mild language, and/or minimal suggestive themes.)
  • Platforms:
Game Description:Conquering the city is just the beginning in this street racer that challenges you to survive not just the streets, but the perilous curves of a treacherous canyon! First, take down rival crews as you race for control of the city streets. When the police get too close, the showdown moves to Carbon Canyon, where you'll put your turf and reputation on the line against rival crew leaders in life-or-death races. Choose your car class: Exotic, Tuner, or American Muscle. A new physics engine creates a distinct ride for each. You'll be able to fine-tune your ride with more precision than ever using the revolutionary new Autosculpt car customizer.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Need for Speed: Carbon Videos

Displaying 1–4 of 4 videos

 


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>