Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Second USB controller does not work on Windows #4204

Closed
Nekmo opened this issue Dec 10, 2016 · 8 comments
Closed

Second USB controller does not work on Windows #4204

Nekmo opened this issue Dec 10, 2016 · 8 comments

Comments

@Nekmo
Copy link

Nekmo commented Dec 10, 2016

I've been HOURS trying to run my second SNES controller on Windows with Retroarch, but the documentation is confusing, outdated and there are 65536 ways to configure the controls in Retroarch.

There are people who say that using xinput works, but it has not work me.
https://libretro.com/forums/archive/index.php?t-1919.html

Here it says to use Emulastation, which detects the 2 controllers and works GREAT but nothing changes in Retroarch.
https://github.com/retropie/retropie-setup/wiki/retroarch-configuration

Here it talks about using Retroarch-config, but it is no longer included with the Windows version.
https://github.com/libretro/RetroArch/wiki/RGUI
https://libretro.com/forums/showthread.php?t=1995

For all this, I just have to ask. Why?


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@AlexFolland
Copy link
Contributor

If it's the same type of device, there's a bug that makes both devices show the same number in XMB and/or RGUI. For me, it shows "SNES (#0)" for both my SNES controllers, but switching between them works, even if I can't see the switch visually. I believe this might be what you're experiencing, and if so, this is a bug with enumerating the controllers, and there's a workaround. Try pressing the right arrowkey while "SNES (#0)" is highlighted.

@AlexFolland
Copy link
Contributor

It still shows "SNES (#0)" for both of my SNES controllers using RetroUSB adapters.

@AlexFolland
Copy link
Contributor

Yes. That's exactly what you said last time we had this conversation 1-2 years ago. It's still a problem though.

@AlexFolland
Copy link
Contributor

Autoconfiguration has never worked for any of the input devices I've used with RetroArch in any situation I've tried it, so I don't even know how to use it.

@Nekmo
Copy link
Author

Nekmo commented Dec 11, 2016

The gamepad is: https://es.aliexpress.com/item/1-x-Retro-Super-for-Nintendo-SNES-USB-Controller-for-PC-for-MAC-Controllers-SEALED/2051991309.html?detailNewVersion=&categoryId=200001103

@AlexFolland The same thing happened to me, but in my case "USB Gamepad (#0)".

Also it did not detect the type of controller well before. Now put "SNES joypad". The options before were RetroPad, RetroPad w/ Analog...

I could upload my configuration file, but I do not know if it would do anything because it now works.

Although it works now for me, I do not close the thread because I think the problem still exists, and there may be more people suffering from this problem. I think it's a bug and it should be fixed.

@AlexFolland
Copy link
Contributor

Why is this closed? The issue still isn't resolved. He posted that a workaround worked, but the issue shouldn't be closed. Or should a new one be opened to describe the exact issue?

@danzel
Copy link
Contributor

danzel commented Dec 15, 2016

Sorry thanks 👍

@danzel
Copy link
Contributor

danzel commented Dec 16, 2016

I think I just found where the two controllers with #0 naming comes from. (This happens on mac too)

input_autoconfigure_joypad_reindex_devices is the method that assigns numbers to names based on them being duplicates.
But it appears to only run if autoconfigure is successful (based on a very brief look through of this code).

input_autoconfigure_joypad_add will return early if it doesn't find settings, before it would do the name index updating.

So if the controllers don't autoconfigure, they'll both get #0 numbers!

Might look in to this more next week, but if someone else beats me to it please go ahead and fix 👍

@libretro libretro deleted a comment from andres-asm Feb 23, 2020
@libretro libretro deleted a comment from andres-asm Feb 23, 2020
@libretro libretro deleted a comment from andres-asm Feb 23, 2020
@libretro libretro deleted a comment from andres-asm Feb 23, 2020
@libretro libretro deleted a comment from andres-asm Feb 23, 2020
@libretro libretro deleted a comment from andres-asm Feb 23, 2020
@libretro libretro deleted a comment from andres-asm Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants