X

Virtua Fighter 4 Latest News - PS2

  • Publisher: SEGA
  • Genre:Fighting
  • Developer: SEGA-AM2
  • Release Date:Mar 19, 2002
  • # of Players:2 players
  • 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:The latest version of Virtua Fighter makes sure no fighter is left behind, with an innovative training mode that takes you from rank amateur to accomplished fighter. You'll learn each move of your chosen character, as well as when and how to use them. VF4 includes 13 fighters, each with a unique style. You can now switch fighting styles in the middle of a match to confuse your opponent. Train your own character AI, then set it free in a match with other characters or even another player.
G4TV Rating
N/A
  • Avg User Rating
    N/A
  • Rate This Game

Virtua Fighter 4 News

Displaying 1–1 of 1 articles

  • Sega: Yu Suzuki's Not Working Here Anymore

    Update: Epic fail by Sega of America President Simon Jeffrey. As Kotaku reports, Jeffrey reinstated that one of Sega's creative force, Yu Suzuki, is still in the company's payroll as a leading "creative officer". Big sigh of relief there for Suzuki fans. So look at the story below as a motivation to watch what you say, before it gets...

    Posted August 12, 2008| 8 Comments

    Sega: Yu Suzuki's Not Working Here Anymore

 


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>