Marvel vs. Capcom 2: New Age of Heroes Previews - Arc

  • Publisher: Capcom
  • Genre:Fighting
  • Developer: Capcom Production Studio 1
  • Release Date:Dec 31, 2000
  • # 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:This arcade-style fighting title pits some of Marvel Comic's most famous comic book heroes of all time against Capcom's legendary stable of video game characters. The result is over 50 playable characters and several play-modes including, Arcade, Score Attack, Training and an innovative Three-on-Three Match. The pantheon includes Spiderman, Mega Man, the Hulk, Wolverine, Captain Commando and many others.
G4TV Rating
  • Avg User Rating
  • Rate This Game

Marvel vs. Capcom 2: New Age of Heroes Previews


Sort by: Filter by:
All Categories
  • No results



  • Fightin' Words Episode 4: Looking Back At MvC 2

    Posted: June 13, 2011

    20,717 Views | 08:57

  • EVO 2010: Capcom Tournament Results

    Posted: July 20, 2010

    6,461 Views | 02:42

  • EVO 2010 Marvel vs. Capcom 2 Final: Justin Wong vs. Santhrax

    Posted: July 14, 2010

    13,297 Views | 15:36

  • Know Your Roots: Marvel vs. Capcom Series

    Posted: May 13, 2010

    34,411 Views | 02:27

  • Best Superhero Video Games Of All Time

    Posted: July 14, 2009

    21,791 Views | 03:01


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

        <customErrors mode="Off"/>

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

        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>