X

F.E.A.R. 2: Project Origin Videos and Trailers - PS3

  • Publisher: WB Games
  • Genre:Shooter
  • Developer: Monolith Productions
  • Release Date:Feb 10, 2009
  • # of Players:1 player, 16 online
  • ESRB:M - Mature (Blood and Gore,Intense Violence,Partial Nudity,Sexual Themes,Strong Language)
  • Platforms:
Game Description:Just when you thought you'd conquered your F.E.A.R., there's another waiting in the shadows. F.E.A.R. 2: Project Origin picks up right before the original left off, frying your nerves with a new blend of paranormal chills and spine-tingling action. Alma, the psychic child at the supernatural center of the first F.E.A.R., has plunged the city of Auburn into chaos. A Special Forces Unit is diverted from a routine mission to try and stop her. Besides an enemy using advanced combat  techniques, you'll battle supernatural forces beyond human control. Use your environment to your advantage, slow time with enhanced reflexes, and more as you unravel a chilling new mystery.
G4TV Rating
N/A
  • Avg User Rating
    (1 Rating)
    4 / 5
  • Rate This Game

F.E.A.R. 2: Project Origin Videos

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