X

Jak X: Combat Racing Videos and Trailers - PS2

  • Publisher: Sony Computer Entertainment
  • Genre:Racing
  • Developer: Naughty Dog
  • Release Date:Oct 19, 2005
  • # of Players:6 players
  • ESRB:T - Teen (Titles rated "Teen (T)" may be suitable for ages 13 and older, and may contain violent content, mild, or strong language, and/or suggestive themes.)
  • Platforms:
Game Description:Well-known adventure duo Jak and Daxter take a break from their usual platforming ways and step into a combat racer in Jak X, the fourth installment in the Jak franchise. Jak and Daxter have been poisoned by the sinister Krew! In order to get the antidote, they'll have to race for Krew in the Kras City Grand Championship. Now Jak and his buddies are forced into a high-speed combat race for their lives against the best drivers on the planet. Dash and blast your way to the finish line in multiple race types, including Circuit and Deathmatch, in multiple settings. Rack up points to earn vehicle upgrades.
G4TV Rating
N/A
  • Avg User Rating
    (3 Ratings)
    4.7 / 5
  • Rate This Game

Jak X: Combat Racing Videos

Displaying 1–1 of 1 videos

  • Jak X: Combat Racing

    Posted: October 20, 2005 | 2,048 Views | 03:36 | 1 Comment

    It's almost a racing game for everyone, but traces of the tad-too-touchy driving the Jak series is known for will throw newcomers for a loop and frustrate even veteran drivers on occasion.


 


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>