« Review: Deadly Towers - Q's NES Review | Main | New Godzilla Top-Secret Snapshot! »
Review: StormChaser GamePad for PS2
There hasn"t been a first party game controller since the Sega Saturn that actually was able to play a Capcom fighting game properly so once a new game system comes out after a while a third party will put out a game controller made for proper fighting games. The StormChaser GamePad from Interact is the closest on the PS2 to that. While it is not quite the legendary MadKatz Dreamcast pad it is pretty good. Except the Xbox who will never get any good Capcom fighting games.
The Pros :
Rubber Hand Grips
Pressure sensitive buttons
Has a good ergonomic feel
Almost as nice to hold as the Sony Dual Shock 2.
The Vibration Feedback kicks it up a notch.
The Cons:
Button Programmability and Button Relocation Options that you never want to use or trigger by accident.
The Vibration Feedback is LOUD it. It sounds like you are using a sex toy.
No colors on the buttons.
Conclusion: Capcom VS SNK2 kicks with this game and it works well with most other games.
Rating: 7 out of 10 Good but with some minor problems
Jake at June 20, 2002
Reviews
Comments
Hello does anyone know how to program the joystick, cause I need help.
Thank you
Posted by: Rick Cyr at January 25, 2008 6:04 AM
I used to love the MadCatz Dream Pad. It was way more comfy and better designed than the official Dreamcast controller, even for non-fighting games. Anyway, I digress.
Good review. I might mention this pad to one of my friends, as she still occasionally plays on her PS2.
Posted by: steve at June 22, 2008 9:45 AM
Hold all button presses until you hear the beep!
Press and hold the program button
Press the key you want to program
Press the key you want to assign to that key, or hit the same key again to revert to default
You can follow with additional keys, or press "select" for a pause. you can also press select plus one of the shape keys for a repeat of the last key (3 o'clock is x1, then x2, x4 and x8 at the top).
If the macro isn't working, try adding pauses
Posted by: Anonymous at August 28, 2008 12:13 PM

