Xbox 360 Wireless Controller Has Unknown GUID |
ace491
|
I resolved my problem. It was unrelated to SDL.
|
|||||||||||
|
Xbox 360 Wireless Controller Has Unknown GUID |
Jonny D
|
|
|||||||||||
|
Xbox 360 Wireless Controller Has Unknown GUID |
Joseph Carter
|
My guess is something related to XInput not being available, not working, or not being used. Happened to me on XP, dunno if it was ever resolved, everyone here just told me to upgrade Windows because XP was obsolete.
JosephSent via mobile On Dec 13, 2014, at 07:15, Jonathan Dearborn wrote:
|
|||||||||||||
|
Xbox 360 Wireless Controller Has Unknown GUID |
Sik
|
2014-12-13 23:35 GMT-03:00, T. Joseph Carter:
I *did* have an issue with XInput some time ago. Fixed by updating SDL. Apparently I had built a version that happened to be right at the time they where switching between the old XInput code and the new one, resulting in it not working correctly. But it seems that here it wasn't even SDL related anyway. _______________________________________________ SDL mailing list http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org |
|||||||||||||
|
Xbox 360 Wireless Controller Has Unknown GUID |
Joseph Carter
|
The problem I had was that XP's XInput was too old for SDL to
support. Newer wasn't available for XP, so it wasn't going to work unless I used an alternative driver that made the triggers work as they do under XInput. That's ultimately what I did. Joseph On Sun, Dec 14, 2014 at 02:50:57AM -0300, Sik the hedgehog wrote:
SDL mailing list http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org |
|||||||||||||||
|