Game Description:The supervillain Grandmaster has imprisoned a quintuple of Marvel heroes – Spider-Man, Captain America, Thor, Iron Man and Wolverine – in a deadly game purely for his own amusement. The heroes are forced to play along and complete a variety of challenges designed to test their abilities to their limits as the Grandmaster manipulates them like pawns on his own private board game. Up to four players can participate to compete against the Grandmaster and his band of villain henchmen, all the while joining forces to break the dome and win their freedom.
Marvel Superheroes 3D: Grandmaster’s Challenge will be bundled with a selection of five superhero masks – one for each of the lead characters – to lend an added level of immersion for younger superheroes! Each mask is embedded with relief 3D glasses in the optical outlets, allowing players to experience the title in a third dimension. The 3D mode can be switched on and off at will from an in-game menu and can be experienced on any display with no additional technology.
“Marvel games are always a pleasure to work on as you have such a fantastic variety of source material to work with,” commented Mark Liddle, Head of UK Business Development, Bigben Interactive. “With Marvel Superheroes 3D: Grandmaster’s Challenge we think we’ve found a new formula to appeal to big and little superheroes alike!”
Marvel Superheroes 3D: Grandmaster’s Challenge will be published on 26th November 2010 by Bigben Interactive exclusively for Nintendo Wii.
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".
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.