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

[Feature Request/Issue] Multiple Controller Support - Better Controller Profiling #2694

Closed
futurepr0n opened this issue Feb 4, 2016 · 3 comments

Comments

@futurepr0n
Copy link

I am using RetroArch 1.2 on OSX, and it has been amazing. The updated interface is a dream, mapping a controller configuration is a breeze, however I find that when I am using 2 controllers - only P1 input ever works. It looks like the P1 controller ends up being the control for both P1 & P2. I am not sure why this is the case, and Im not sure how to help with diagnosing it but if you would like me to try - I can provide as many details as possible and/or help where applicable!

  • Using Bluetooth Controllers
  • Both are Dualshock 4's

I think that the issue might be that they are both named "Wireless Controller" as far as OSX is concerned. I think this might be the issue because RetroArch might not be differentiating between the MAC Addresses, and instead relying on the Controller Name for the mapping.

Would it be possible to build in a way to Name a controller based on its MAC, and then you can set the Controller Name or something? I think that could help..

I have gone in the menus, and mapped the inputs successfully using both controllers individually, but as soon as I boot the game up - only P1's Controller seems to be recognized, and both P1 and P2 are controlled by that device.

Edit:
I'm not sure if this is a real issue, or something that is just because of my set up. I will try to update this ticket tonight after trying a few more attempts.. I just came across a way to name the controller in OSX, https://support.apple.com/en-ca/HT205348, so maybe after explicitly changing the device names, I won't have a conflict when mapping the controllers in RetroArch's config.

@andres-asm
Copy link
Contributor

Weird, I don't have a mac for sure so I think it could be driver specific. I have tried several identical in windows and android and they are working fine.

What input driver are you using?

@andres-asm
Copy link
Contributor

Please re-open if this is still an issue.

@futurepr0n
Copy link
Author

On Mac- I am using the default driver that supplies the bluetooth connection. Do you mean the Retroarch input Driver?

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

2 participants