F.E.A.R. 2: Project Origin Screenshots and Images - PC

F.E.A.R. 2: Project Origin
Game Description:The second heart-stopping shooter by Monolith (after F.E.A.R.) continues the spine-tingling supernatural suspense story of an escalating paranormal crisis that threatens to destroy a major American city. At the center of the calamity is the mysterious Alma, whose rage against those who wronged her triggered a chain of events that has spiraled completely out of control. Now that she has been loosed upon the world, the consequences will be unimaginable. Although this game is technically a follow-up to F.E.A.R., the game will not carry the F.E.A.R. franchise name due to a shift in publishers -- instead, it will feature a new name for its terror.
G4TV Rating
  • Avg User Rating
    (1 Rating)
    4 / 5
  • Rate This Game

F.E.A.R. 2: Project Origin Screenshot & Image Galleries

  • F.E.A.R. 2: Project Origin Briefing Trailer

    Posted: January 27, 2009

    2,462 Views | 01:51 | 1 Comment

  • F.E.A.R. 2: Project Origin Fear Away Infomercial

    Posted: January 23, 2009

    6,068 Views | 02:05 | 3 Comments

  • Gaming Update 01.20.09

    Posted: January 20, 2009

    1,233 Views | 01:54 | 1 Comment

  • F.E.A.R. 2: Project Origin Bourbon-Soaked Dev Q and A

    Posted: January 16, 2009

    4,706 Views | 09:38 | 1 Comment

  • X-Play Recommends: Powerhouse PC Games

    Posted: January 14, 2009

    3,696 Views | 02:32 | 1 Comment


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 -->

        <customErrors mode="Off"/>

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 -->

        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>