> > ... you can't properly read the X360
> > pad in Windows via DirectInput - they force you to use XInput instead....
>
> ...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....
Yup, it's a limitation due to microsoft's driver, not of XInput vs directInput. If the user uses redclOud's XBCD driver instead, directInput can see the triggers as separate axes. QED
Why MS is limiting the driver and saying it's a limit of directInput is up for argument. (Over simplification, promotion of XInput/XBox developement, warning of depreciation of directInput, laziness, etc.)
Robin
www.urebelscum.speedhost.com/ or
www.angelfire.com/retro/u_rebelscum or
rain.prohosting.com/urebel
|
Index 
Flat 
Re: EDIT: I think I understand what's going on now.
Reply
