X

Advent Rising Videos and Trailers - XBX

  • Publisher: Majesco
  • Genre:Action, Adventure
  • Developer: GlyphX Inc.
  • Release Date:Jun 2, 2005
  • # of Players:1 player
  • 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:In this epic, 3rd-person sci-fi adventure inspired by author Orson Scott Card, you'll travel the galaxy amidst Seekers, Aurelians, and Humans. The first in a trilogy of games, Advent Rising offers up a powerful array of weapons including pistols, blasters, rifles, rocket launchers, and alien-created weapon like microwave guns. Additional superhuman powers like energy blasts, levitation, and energy shields develop as the game progresses, keeping things even more interesting. Visually astounding, Advent Rising was based on the Unreal warfare engine integrated with the Karma physics engine. Downloadable content will be available. The soundtrack features the Mormon Tabernacle Choir and Los Angeles Orchestra.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Advent Rising Videos

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