If this guy keeps his words we can expect some sort of fix to this issue soon. I strongly urge all of you who have this problem to email Madcatz about it. Apparently they do not know about the seriousness of this issue since they did not do anything about it since March. If enough people email them, it will make them actually start working on a fix instead of leaving the issue as it is.
Also, I got my reply when I emailed the Europe tech support email. Either the US branch do not check their tech support email or they are ignoring this issue and their customers completely.
My 360 Joystick is working fine on Vista-32
Used MAME and #Reload
I used the configurations on both to map my buttons
For those who are using MAME and not getting it to work, make sure people configure the controls in the Settings first. Enable Joystick Support you may have forgot to do that.
Indeed, this is quite disappointing. I was super psyched to get my TE stick Tuesday, only to get home and find it wonât work on this PC. I ended up rage buying a PCI usb hub deal.
I really hope madcatz does not blow this off and actually fixes this problem so other people can actually use theirs.
I had the chance to test a PS3 TE stick and it worked fine on both my Acer laptop and my Atom netbook. One was running XP SP2 and the other was Windows 7 RC. Shows up in game controller settings and briefly tested with MAME.
Not sure if this will help or not but just adding my findings to the threadâŚ
I got my Fightstick a week ago and was having similar problems too, but a VIA-based add-on PCI card fixed the problem (thanks for the poster who first tried that out!).
Iâve been doing some research on the issue and found a few things that may be of interest. It is a little-known fact that there are two mutually incompatible standards for USB 1.x controllers - UHCI and OHCI (USB 2 was standardised with EHCI). OHCI is an open-standard, while UHCI is proprietary to Intel. As far as I know, only VIA has licensed UHCI from Intel, while everyone else used OHCI. From the previous posts, it seems that those whose Fightsticks work (Intel and VIA users) all have UHCI USB chipsets, while all those for whom it doesnât work (AMD, NEC, Nvidia etc.) all have OHCI USB chipsets.
The easiest way that Iâve found of determining which type you have is to open Device Manager (in the Control Panel), and expand the âUniversal Serial Bus controllersâ section in the device tree. There should be numerous entries ending with âHost Controllerâ. OHCI controllers are listed as âOpenHCD USB Host Controllerâ, while UHCI controllers are listed as âUniversal Host Controllerâ (âEnhanced Controllerâ are EHCI controllers for USB 2, and irrelevant here). For the benefit of others who are planning to buy the stick mainly for their PCs, could everyone please confirm that UHCI controllers work with the Fightstick but OHCI controllers donât?
It also seems that this is not a unique problem - Thrustmaster have had simliar problems before with their joysticks and wheels.
Indeed, âOpenHCD USB Host Controllerâ, does not work. Madcatz should be made known about this.
Edit: Iâve sent an email to Madcatz pointing them to the post by Lionclaw. If anyone would like to contact Madcatz regarding this issue, Iâd recommend the following email: brhelpline@madcatz.com (Attn: Daniel Nuth). This guy was the one who replied me after I sent them four mails over a week regarding this issue, so we can assume heâs working on the fix now.
EHCI controllers are responsible for handling USB 2 devices only. The FightStick is a USB 1 device, so it gets handled by the UHCI/OHCI controllers on your system. You can see this if you select the menu item âView | Devices by connectionâ in Device Manager. On my computer, plugged into an add-in PCI card, it goes:
ACPI x64-based PC -> Microsoft ACPI-Compliant System -> PCI bus -> PCI standard PCI-to-PCI bridge -> VIA Rev 5 or later USB Universal Host Controller -> USB Root Hub -> USB Human Interface Device -> HID-compliant game controller
If I plug it into a built-in port instead, it is connected like:
ACPI x64-based PC -> Microsoft ACPI-Compliant System -> PCI bus -> Standard OpenHCD USB Host Controller -> USB Root Hub -> USB Human Interface Device -> HID-compliant game controller
In this case, it doesnât work. I guess that this is your situation?
