You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug report was migrated from our old Bugzilla tracker.
Reported in version: 2.0.3 Reported for operating system, platform: Windows (All), All
Comments on the original bug report:
On 2014-11-13 12:48:06 +0000, wrote:
An official Microsoft Xbox 360 wired controller (Hardware ID: USB\VID_045E&PID_028E&REV_0114) is not detected using SDL 2.0.3. The same controller works with SDL 2.0.0.
I am attempting to use a controller with SDL through Mupen64Plus, a Nintendo 64 emulator. After initially reporting this regression to them, it was determined to be an issue with SDL when it was updated from 2.0.0 to 2.0.3. I had initially reported that this regression occured on Windows Vista x86. A developer was unable to reproduce the problem on a Windows 7 computer. However, I was able to later reproduce it on a Windows 7 x64 machine.
I am using custom drivers (XBCD 0.2.7 by Squall Leonhart), but the behaviour is still the same when they are uninstalled and the default ones are used.
On 2014-12-05 05:48:45 +0000, Alex Szpakowski wrote:
Are you able to test using the latest Mercurial version of SDL (the upcoming 2.0.4)? Just to make sure the issue is still there in the most current code.
On 2014-12-05 10:28:53 +0000, wrote:
I'd be happy to test the latest version. However, I am very inexperienced with source code and building projects. I downloaded a ZIP of the project from http://hg.libsdl.org/SDL (revision f6355bfca853) and attempted to compile it with Visual C++ 2010 Express, but the build failed. I tried to look for any exisitng builds of 2.0.4 in the repository but couldn't find one. If you could help me with getting the latest version, I would apprecaite it.
On 2015-02-19 06:32:16 +0000, Ryan C. Gordon wrote:
Marking a large number of bugs with the "triage-2.0.4" keyword at once. Sorry
if you got a lot of email from this. This is to help me sort through some bugs
in regards to a 2.0.4 release. We may or may not fix this bug for 2.0.4,
though!
On 2015-04-07 04:57:56 +0000, Ryan C. Gordon wrote:
(sorry if you get a lot of copies of this email, I'm marking several bugs at once)
Marking bugs for the (mostly) final 2.0.4 TODO list. This means we're hoping to resolve this bug before 2.0.4 ships if possible. In a perfect world, the open bug count with the target-2.0.4 keyword is zero when we ship.
(Note that closing a bug report as WONTFIX, INVALID or WORKSFORME might still happen.)
--ryan.
On 2015-08-30 18:03:12 +0000, Alex Szpakowski wrote:
360 controllers work for me as of the latest 2.0.4 Mercurial code; should I close this as 'worksforme'?
Just the first part of the diff is a trivial fix for this issue for me. At least on my computer, my official Microsoft Xbox wired controllers show up as "Controller (XBOX 360 For Windows)", which is a different case than the code is looking for.
diff -r f0645cd8fd39 -r 7161a0cf5b92 src/joystick/SDL_gamecontroller.c
--- a/src/joystick/SDL_gamecontroller.c Sun Mar 20 15:35:34 2016 -0300
+++ b/src/joystick/SDL_gamecontroller.c Mon Mar 28 14:17:55 2016 -0700
@@ -660,7 +660,7 @@
if (!mapping) {
const char *name = SDL_JoystickNameForIndex(device_index);
if (name) {
if (SDL_strstr(name, "Xbox") || SDL_strstr(name, "X-Box")) {
This bug report was migrated from our old Bugzilla tracker.
Reported in version: 2.0.3
Reported for operating system, platform: Windows (All), All
Comments on the original bug report:
On 2014-11-13 12:48:06 +0000, wrote:
On 2014-12-05 05:48:45 +0000, Alex Szpakowski wrote:
On 2014-12-05 10:28:53 +0000, wrote:
On 2015-02-19 06:32:16 +0000, Ryan C. Gordon wrote:
On 2015-04-07 04:57:56 +0000, Ryan C. Gordon wrote:
On 2015-08-30 18:03:12 +0000, Alex Szpakowski wrote:
On 2017-03-03 19:36:31 +0000, Jimb Esser wrote:
On 2017-08-14 04:37:35 +0000, Sam Lantinga wrote:
The text was updated successfully, but these errors were encountered: