#Xinput test win10 windows

I feel for any developer whose game requires the implementation of anything more than the most basic of controller input the byzantine web of APIs and catch cases they need to implement is truly horrifying.Ībove rant aside, I just tested my (knockoff) wireless 360 receiver with my (official) 360 controller and everything seems to be working as before on Win10AU, so the problems described above do appear to be specific to the Xbox One controller(s). Game devs now have three (four, if you count raw input) separate controller methods to choose from, all of which are broken in various ways (deprecated, extremely limited support for controllers that differ in terms of buttons/layout from a 360 controller, inconsistent handling of axis center positions, inconsistent handling of controller hotplug, problematic conflicts when the same controller is available through multiple APIs, limited maximum number of controllers, etc.) Microsoft appears to now be pushing yet another input API to developers, although I believe this one is built as an abstraction layer on top of Xinput. The API is technically inferior to DirectInput in almost every way (and the ways it isn't could have simply been incorporated into an updated version of DirectInput), and it additionally requires licensing fees paid to Microsoft to implement peripherals using it (one of the reasons there was a serious lack of non-Microsoft Xinput compatible controllers for so long).

#Xinput test win10 windows

Microsoft has been cocking up game input devices on Windows for the past 10 years ever since Xinput was released.