If it was properly implemented then XInput shouldn't have a problem with any popular modern PC pad. Your issue probably has more to do with Games for Windows Live, which is a nightmare for user interfaces in general.
Fair enough. I don't use Live but yeah, it does appear that it's GFW that's imposing the "Xbox controllers only" mandate.
I've never felt any inclination to use a pad in a non-console port on my PC, so I don't know if there's some special love for DirectInput in some genre I don't know about other than console games where a pad is superior to mouse and keyboard.
I'm not precisely sure what the genre or port status has to do with it. If a game works with an Xbox controller there's no good reason it shouldn't work with a Rumblepad 2.
Also I'm obviously using Windows, which (Vista and beyond) has native drivers for Xinput. Making it totally plug and play for either a wired controller or a wireless controller using the receiver.
Uh, yeah, so are DirectInput-compatible controllers.
I don't know what, if anything, we're arguing about. XInput doesn't stop me from remapping controls, though some games do, and I simply appreciate being able to play ports of console games, made to look much better on my PC, with controls that reflect the console version perfectly. Not to mention that the 360 is pad is actually a pretty damn good pad.
The problem is that it supports a tiny fraction of the controllers on the market. And that there's no technical reason this should be the case.
If I'm reading this correctly: He's just madfrustrated the piece of shit controller be bought
Cute.
Here is a link to Google. It is a search engine. See what happens when you plug the phrase "rumblepad 2 reviews" into it.
Yes, what a rube I am; I bought the highest-rated controller on the market instead of another, more expensive controller for a video game console that I do not own, and did not foresee Microsoft deliberately breaking compatibility with all its competitors' products.
...actually, that last part DOES sound kinda stupid on my part. I'll give you that one.
isn't as easily read/as easy to program for as the first party Microsoft controller for Microsoft systems using an API created by Microsoft. I think.
...you can't possibly be arguing that users should expect only Microsoft hardware to work correctly with Windows.
...and incidentally, DirectInput is also an API created by Microsoft.
I can see where you're coming from and I disagree. Why should they have to go back and make it work for your controller?
Because when you sell the operating system that runs on 90% of the world's computers, you can't go around fucking breaking compatibility with competitors' products. There have been multiple court rulings verifying this fact, both in America and overseas.
Why doesn't logitech hack it to make it read as an Xinput after you install some drivers?
Presumably because Logitech would be just as happy with me buying a new controller from them as MS would be with me buying a new one from them.