X

F.E.A.R. Files Videos and Trailers - Xbox 360

  • Publisher: Vivendi Universal
  • Genre:Shooter
  • Developer: TimeGate
  • Release Date:Nov 7, 2007
  • # of Players:1 player, 16 online
  • 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:The game which reinvented the "action movie" style of horror gaming is back with this combo pack of a F.E.A.R. expansion and a stand-alone campaign! Step into the boots of an elite soldier, trained to respond to unusual and unimaginable circumstances, and play through two complete missions, including the brand-new Perseus Mandate campaign and the expansion pack Extraction Point. As before, the A.I. is combat-adaptable and ready to fight back, but this time, you have six new weapons at your disposal to bring the pain. The environments are even more destructible, and you can take the fight online with up to 16 players on all-new multiplayer and instant-action maps!
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

F.E.A.R. Files Videos

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