By using this site, you agree to our Privacy Policy and our Terms of Use. Close

Forums - Gaming - IGN: Marvel vs. Capcom 2 Review

Garamond said:

They should release a HAPP stick for this so I can complete my collection.

 

You mean this?

http://www.amazon.com/Xbox-360-Real-Arcade-Pro-EX/dp/B001GDONZS/ref=sr_1_1?ie=UTF8&qid=1248909275&sr=8-1



It's just that simple.

Around the Network

All games should get 10s no matter what. Stop judging these poor games on stupid things like controls and frame rate issues. Critical game criticism is fail.



You can find me on facebook as Markus Van Rijn, if you friend me just mention you're from VGchartz and who you are here.

^frame rate issue on the character select screen? notice that the graphic score are the same? does this game have a significant inferior gameplay expirience base purely on the control scheme? If that is the case, why was it not highlighted? Why did SFIV and Blazblue or any other fighter for that matter get the same score on both system despite the 'inferior' control?

Consistency in review is king.




MonstaMack said:
Garamond said:

They should release a HAPP stick for this so I can complete my collection.

 

You mean this?

http://www.amazon.com/Xbox-360-Real-Arcade-Pro-EX/dp/B001GDONZS/ref=sr_1_1?ie=UTF8&qid=1248909275&sr=8-1

Happ is an American styled arcade stick, which I am absolutely not used to. It's just that I already have a TE and then a Seimitsu modded TE and I'd just like a HAPP one for completions sake. I think that's just a Sanwai JLF with cheap Hori buttons (though I think it uses quick disconnects so Sanwa/Seimitsu buttons can easily replace those). Marvel players mainly use Happ parts for whatever reason, but I'm guessing no sticks are going to be released alongside this game.

Also, frame rate issues are a big deal fighting games. If the 360 version really does have issues during gameplay and the PS3 doesn't, it's more than fair to give the 360 version a lower score. I've heard some people have noticed some issues during supers/start of matches and other places, but I can't really tell if it's more than a few isolated incidents at this point. Whatever the case, blaming Backbone is the most logical solution.