X

Final Fantasy VII: Dirge of Cerberus Videos and Trailers - PS2

  • Publisher: Square Enix
  • Genre:Action, Adventure
  • Developer:
  • Release Date:Aug 17, 2006
  • # of Players:1 player
  • ESRB:T - Teen (Titles rated "Teen (T)" may be suitable for ages 13 and older, and may contain violent content, mild, or strong language, and/or suggestive themes.)
  • Platforms:
Game Description:Delve even deeper into an already epic storyline in Final Fantasy VII: Dirge of Cerberus, the third installment of games continuing the saga begun in Final Fantasy VII. Three years after Final Fantasy VII, a cleansing is about to begin. Those deemed unworthy will be hunted down and summarily destroyed. A faction known as the DG (Deepground) Soldiers, who were buried alive after the Meteor tragedy, have re-emerged and begun attacking. Vincent Valentine is the one man who may be able to save the world from destruction. He's joined by other Final Fantasy VII characters on a journey that will see harsh justice dispensed and astounding truths revealed!
G4TV Rating
N/A
  • Avg User Rating
    (3 Ratings)
    3.7 / 5
  • Rate This Game

Final Fantasy VII: Dirge of Cerberus Videos

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