X

Final Fight: Double Impact Videos and Trailers - Xbox 360

Final Fight: Double Impact
  • Publisher: Capcom
  • Genre:Fighting
  • Developer: Proper Games
  • Release Date:Apr 14, 2010
  • # of Players:1 player
  • ESRB:T - Teen (Animated Blood, Mild Violence, Suggestive Themes)
  • Platforms:
Game Description:Final Fight: Double Impact is a dual release of two classic arcade side-scrolling beat-em-ups. First up is Final Fight, where players follow the heart-pounding adventures of Cody, Guy, and Haggar – three heroes fighting their way across crime-ridden Metro City in hopes of saving Haggar's daughter from the evil clutches of Mad Gear. There are 6 stages filled with perilous challenges where the only hope for justice is the unique fighting techniques mastered by each character. With the news released today that Cody and Guy will both be playable characters in Super Street Fighter IV, Capcom fans now have the chance to take a trip down memory lane and experience these characters in their first appearance before playing them in the new Street Fighter game.
G4TV Rating
4 / 5
  • Avg User Rating
    N/A
  • Rate This Game

Final Fight: Double Impact Videos

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