Postby il_gattopardo » Tue Apr 24, 2012 6:46 am
I just did a little testing on my laptop. It seems that my issue may indeed be oddly driver-related.
My desktop, where I have the issue, is using special 360 controller drivers called XBCD. They allow for customisation of just about everything, including the controller deadzones, turning the triggers into simple buttons, and so on. It's magnificent and extremely useful, really, especially when you still play flight sims, but your last joystick died ages ago. Problem is, as I said, 4DO doesn't like these drivers.
On my laptop however, an aging netbook, 4DO and my controller got along BEAUTIFULLY using Microsoft's drivers. No issues whatsoever, all button presses detected and programmed as set 2 for player 1.
I'm not sure what it is about XBCD that is causing such conflict with 4DO, but I did at least figure out that Microsoft's stock drivers work a-ok. I hope this helps somewhat, although I can't say how many people here use XBCD drivers with their 360 wired/wireless controllers. Thank you.