-
Notifications
You must be signed in to change notification settings - Fork 202
Controllers being listed twice #22
Comments
Hi @WAZAAAAA0, would you please try the installer found here? It reverts back to SDL 2.0.3, which will hopefully fix the double-controllers issue. Also, please check that I correctly made the translation changes you requested. Thanks! |
According to @mrtnkl, reverting to SDL 2.0.3 doesn't fix the 2x controller issue, at least under win10... @mrtnkl, would you please try the following:
Thanks! |
Let's see... f56788f:
7f4be52: On a side note, the README.md: |
Hi, with the original build you sent me, I get 4 tabs (and only 1 controller detected by Windows): Only tab 3 actually allows controller mapping, tab 1 and 2 don't detect any presses or axis. I'll now go and install 7f4be52. |
Okay, this is odd. When I started 7f4be52 it got 4 controllers as well. But now, it ... works. I rebooted the device, started antimicro first - it said "no controllers", then I enabled the controller. It got detected by Windows and immediately by AntiMicro and only showed 1 tab! This is 7f4be52. I mapped the keys, loaded up my Oblivion mapping and everything works. 100%. Odd that I can't reproduce the 4 tabs bug at the moment. |
@WAZAAAAA0 Thanks for testing! Yes, I think you're right, the change is likely on our end and not with the SDL. I can't seem to find any bug reports relating to this with the SDL project. Does anyone know of a version that definitely worked? The more recent the better. If it is on our end, then there is hope that I can get it to show up on my end and try to track it down. Just to clarify, what version of Windows are you running? 7? Re: copyright date - thanks! I've updated issue #12 with a comment to make sure I track that down before release. Re: names of languages - very good point! I like your second idea, using the native name for each language. I've added issue #27. Just to clarify, AntiMicro defaults to English? Ideally, AntiMicro should default to whatever the system is set for, but I don't know how tricky that is. I'll look into it. Re: the README - Good catch! Yes, I needed to add some white space after each item. Thanks for the detail work! @mrtnkl Interesting! So 7f4be52 is working for you on Windows 10? Good to know. That is the mainline, so there is hope we'll be able to release a version that works on Windows 10 without much work. 😃 Please keep us posted if it shows up again. The fact that it is working now but wasn't earlier is further evidence that the problem is on our end. Thanks for testing! |
@jsbackus Upon further testing, the double detection tab only occurs if the controller is ALREADY connected before launching AntiMicro. If I open AntiMicro first AND THEN physically plug in my controller into the USB port, only 1 tab is shown. mrtnkl basically said the same thing:
It still needs to be fixed though. AntiMicro already defaults to whatever the system is set for (in my case, it defaulted to Italian). |
@WAZAAAAA0 Thanks! I've been able to replicate the issue in Wine (excusing this issue: #28), so I should be able to track it down.
Good catch! That aught to help narrow down where the issue is. Plus, it gives us a temporary workaround. Agreed, definitely needs to be fixed. Glad the language defaults to the current system language. |
I know this is totally unrelated but I notice the same issue (duplicate inputs and duplicate controllers listed for my XBOX elite controller on Steam BP) I noticed they upgraded SDL2 to 2.0.4 too... |
Hey folks, sorry it has taken so long to get back to this. I have a couple of test cases if you would be so kind as to try them for me: At least one of these should work. Hopefully both will. Thanks! |
@fr500 Interesting! Hope we don't have two problems to track down... Thanks for letting us know! |
Both 93099d0 and cf500290 have solved the double controller listing on Windows 7 Ultimate 64-bit SP1. |
Great! Thanks for testing! I'll try to take care of the few small loose ends we have and we'll try to release next weekend. Thanks again! |
…h code from commit #fd34684 in and out. Looks like the code in addInputDevice is causing a problem...
Happening at least on Windows version. Suspect it is related to SDL 2.0.4 and fix for issue #4. First step is to back the change out and rebuild with SDL 2.0.3 and retest.
The text was updated successfully, but these errors were encountered: