X

Outrun 2006 Coast 2 Coast Latest News - PSP

  • Publisher: SEGA
  • Genre:Racing
  • Developer:
  • Release Date:Apr 25, 2006
  • # of Players:6 players
  • ESRB:E - Everyone (Everyone)
  • Platforms:
Game Description:OutRun 2006's epic all-American roadtrip makes a seamless transition to the PSP as the series makes a stunning handheld debut. Race from coast to coast and experience all the beauty America has to offer...as you watch it whiz by at 200 mph! Slip behind the wheel of a precision Ferrari racer and conquer 50 tracks, including 20 from OutRun2 and 30 from the OutRun2 SP arcade game. You'll also find all-new missions created especially for PSP. Link with your PS2 to combine OutRun miles you've accumulated on both systems and unlock special content made exclusively for the PlayStation family. Compete against up to five friends in online or ad-hoc races.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Outrun 2006 Coast 2 Coast News

Displaying 1–1 of 1 articles

  • SEGA Won't Comment On New 'OutRun'

    Could it be that SEGA may be coming out with a brand new OutRun game? The OFLC (Australian government's Office of Film and Literature Classification website) has a rating for the OutRun Online Arcade. It says that OutRun is a multi-platform collaboration between THQ and SEGA. But this could be left from days of yore when THQ handled the...

    Posted November 18, 2008| 3 Comments

    SEGA Won't Comment On New 'OutRun'

 


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>