X

Crimson Skies: High Road to Revenge Videos and Trailers - XBX

  • Publisher: Microsoft
  • Genre:Action, Adventure, Flight
  • Developer: Microsoft Game Studios
  • Release Date:Oct 23, 2003
  • # of Players:4 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:The skies are filled with thrills and kills in Crimson Skies: High Road to Revenge. Set in an alternate 1930s reality, Crimson Skies puts you in the middle of harrying air combat, warring nations and romantic adventure. As the heroic air pirate Nathan Zachary you'll lead the Fortune Hunters in spectacular aerial battles, taking on fighter aces and zeppelin gunships. Master ten warplanes, using detonator cannons, tesla guns and more. With XBox Live, participate in intense online aerial dogfights! Crimson Skies: High Road to Revenge is the best arcade style aerial combat game of its kind. Come fly the deadly Crimson Skies!
G4TV Rating
N/A
  • Avg User Rating
    (1 Rating)
    5 / 5
  • Rate This Game

Crimson Skies: High Road to Revenge Videos

Displaying 1–1 of 1 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>