X

Fatal Frame 2: Crimson Butterfly - Director's Cut Latest News - XBX

  • Publisher: Tecmo
  • Genre:Action, Adventure
  • Developer:
  • Release Date:Nov 2, 2004
  • # 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:Fatal Frame returns with the creepy story of twin sisters Mio and Mayu Amakura. Central to the creepy feel of Fatal Frame 2 is its major theme of Mio and Mayu's twin sister relationship. After your twin sister Mayu chases a crimson butterfly into the forest, you chase after her and discover a long forgotten village with an unknown past. Soon you find yourself sucked into a world of horrors and illusions. Real-time visuals, terrifying atmospheres, ever more demonic enemies and an enhanced antique camera weapon that helps you destroy your ghostly foes, makes Fatal Frame 2 one of the most exciting survival-horror games of its kind.
G4TV Rating
N/A
  • Avg User Rating
    (1 Rating)
    5 / 5
  • Rate This Game

Fatal Frame 2: Crimson Butterfly - Director's Cut News

Displaying 1–1 of 1 articles

 


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>