X

F.E.A.R. First Encounter Assault Recon Previews - PS3

  • Publisher: Vivendi Universal
  • Genre:Shooter
  • Developer:
  • Release Date:Apr 25, 2007
  • # of Players:1 player, 16 online
  • ESRB:M - Mature (Blood and Gore,Intense Violence,Strong Language)
  • Platforms:
Game Description:A paramilitary force has invaded a multibillion-dollar aerospace compound and taken a number of hostages. The government counters this with its best special ops team but the group is immediately obliterated. Live footage of the massacre is cut off by a stunning wave of destruction and military leaders are paralyzed by disbelief. That's where F.E.A.R. begins. And it doesn't get much better in this paranormal first-person shooter. You're a soldier up against tactical teams, trained assassins, and heavy-armor-led squads. You'll use state-of-the-art weaponry in never-before-seen spectacular situations (ever had to survive a helicopter crash, then blast your way out?), where you'll watch enemies recoil and collapse in raw combat.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

F.E.A.R. First Encounter Assault Recon Previews

 

Sort by: Filter by:
All Categories
  • No results

 

 

 


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>