Funny, I just added support for XInput the other day.
An Xbox 360 controller will work, but with one exception: the left and right triggers (pressure-sensitive analog buttons) are mapped as one single axis. You can map low and high as their own buttons, but if the user tries pressing both at the same time, they cancel each other out.
It's an artificial limitation, as other controllers map each analog button as its own axis just fine.
Luckily the code's really easy, just one function call to XInputGetState() -- no need for initialization / resource freeing, and the return code tells you if the device is connected.
The downside is DirectInput makes it really tough to identify the controllers. I use RawInput's device name to do it, but there's a few other methods.
Further, it requires xinput1_3.dll; which doesn't ship with XP 2k5 or Vista SP0.
And I was just thinking about writing an XAudio 2 driver, heh. It at least shares the WAVEFORMATEX struct, but otherwise it looks quite different from literally everything else in DirectX.
Should share code or something for that 
|
Index 
Flat 
Re: EDIT: I think I understand what's going on now.
Reply
