X

Final Fantasy X Latest News - PS2

  • Publisher: Square Enix
  • Genre:RPG
  • Developer: Square
  • Release Date:Dec 18, 2001
  • # 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:This epic RPG follows an athlete named Tidus through the world of Blitzball, an underwater combination of soccer and basketball that becomes a key part of the gaming action. The cast is rounded out by Yuna, the daughter of a powerful summoner. Haunted by mysterious dreams that foretell of her destiny, Yuna must join Tidus and save the human race by somehow stopping the evil force known as "Sin." This tenth Final Fantasy not only boasts improved character renderings, more dynamic camera movement, and impressive summon and spell graphics, but is the first in the groundbreaking series to feature voiceover. Also improved is the "Facial Motion System" which adds innovative real-time facial animation to the character.
G4TV Rating
N/A
  • Avg User Rating
    (20 Ratings)
    4.7 / 5
  • Rate This Game

Final Fantasy X News

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