Wolfpup
CAGiversary!
In researching my problems with Dead Rising 2, I've stumbled across some other issues that I'm not having, but seem to point to a weird problem Microsoft may have created with Windows controller support...
So Windows still has, and used to primarily use "DirectInput", part of DirectX, for controller input. I think it's a generic API that any controller can tie in to. Makes sense.
Now while it's still supported, it's been depreciated and apparently not updated since Direct X 8 (and doesn't work with "metro" apps)...apparently they want keyboard and mouse support done through something else, and they want developers using Xinput instead.
So I'd have assumed Xinput was just a direct replacement, but it's looking like it's literally ONLY for Xbox 360 controllers? Like even third party 360 controllers don't work, I guess? And One controllers don't work?
I'm foggy on all this, but it sounds like maybe Microsoft went from a sensible "we support all controllers through our API" to a "hey, this Xbox 360 controller is it". While I think pushing to get most/all games to support a 360 pad is a great idea, cutting out everything else stinks. DR2 isn't working with One pads even, or third party 360 pads, though does work with Playstation 3/4 pads if they're running software to make the system think they're 360 pads...I guess.
I may have the issues confused, and frankly controller support on non-console systems is confusing generally (like what's up with iOS?)
So Windows still has, and used to primarily use "DirectInput", part of DirectX, for controller input. I think it's a generic API that any controller can tie in to. Makes sense.
Now while it's still supported, it's been depreciated and apparently not updated since Direct X 8 (and doesn't work with "metro" apps)...apparently they want keyboard and mouse support done through something else, and they want developers using Xinput instead.
So I'd have assumed Xinput was just a direct replacement, but it's looking like it's literally ONLY for Xbox 360 controllers? Like even third party 360 controllers don't work, I guess? And One controllers don't work?
I'm foggy on all this, but it sounds like maybe Microsoft went from a sensible "we support all controllers through our API" to a "hey, this Xbox 360 controller is it". While I think pushing to get most/all games to support a 360 pad is a great idea, cutting out everything else stinks. DR2 isn't working with One pads even, or third party 360 pads, though does work with Playstation 3/4 pads if they're running software to make the system think they're 360 pads...I guess.
I may have the issues confused, and frankly controller support on non-console systems is confusing generally (like what's up with iOS?)