X

Marvel vs. Capcom 3: Fate of Two Worlds Screenshots and Images - Xbox 360

  • Publisher: Capcom
  • Genre:Fighting
  • Developer: Capcom
  • Release Date:Feb 15, 2011
  • # of Players:1 player, 8 online
  • ESRB:T - Teen (Mild Language,Partial Nudity,Sexual Themes,Violence)
  • Platforms:
Game Description:Marvel vs. Capcom 3: Fate of Two Worlds arrives after a decade of waiting, as the iconic Marvel and Capcom characters join forces again in a re-envisioned team fighting game for a new generation. Fill the shoes of legendary characters from the most beloved franchises in entertainment as you battle in a living comic book brought to life in a VS. fighting game for the first time by Capcom’s MT Framework. Get set for the ultimate faceoff with Marvel vs. Capcom 3.
G4TV Rating
5 / 5
  • Avg User Rating
    (46 Ratings)
    4 / 5
  • Rate This Game

Marvel vs. Capcom 3: Fate of Two Worlds Screenshot & Image Galleries

  • Marvel vs. Capcom 3 TaskMaster Trailer

    Posted: January 18, 2011

    16,943 Views | 01:18

  • Marvel vs. Capcom 3 Akuma Trailer

    Posted: January 18, 2011

    20,149 Views | 01:20

  • Capcom Talks Marvel vs. Capcom 3 At CES 2011

    Posted: January 12, 2011

    19,249 Views | 04:47

  • Marvel vs. Capcom 3 Haggar and Phoenix Preview Video

    Posted: January 7, 2011

    56,986 Views | 04:07

  • Marvel vs. Capcom 3 Haggar Trailer

    Posted: January 7, 2011

    11,300 Views | 01:21

 


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>