X

Obscure: The Aftermath Videos and Trailers - PS2

  • Publisher: Ignition Entertainment
  • Genre:Action, Adventure
  • Developer: Hydravision Entertainment
  • Release Date:Mar 27, 2008
  • # of Players:1 player
  • ESRB:M - Mature (Titles rated "Mature (M)" may be suitable for ages 17 and older. They may include more intense violence or language than products rated "Teen" as well as mature sexual themes.)
  • Platforms:
Game Description:After the terrifying events of their high school experience, the survivors of Obscure have moved on to college – and to a normal life. Or so they think! The discovery of a mysterious plant on campus makes events take a turn for the worse, and once again, the heroes find themselves fighting for their lives. Choose from six different playable characters, each with his or her own special abilities. Swap characters throughout the game to make use of your skills, and have a friend jump in on the fly to help you solve puzzles and fight the monsters lurking in the shadows. No matter what, you must stay alive as you play your very own teen horror movie!
G4TV Rating
N/A
  • Avg User Rating
    (1 Rating)
    2 / 5
  • Rate This Game

Obscure: The Aftermath Videos

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