-
Notifications
You must be signed in to change notification settings - Fork 603
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
Switch Pro Controller no longer recognized on Cemu 2.0-66 #1098
Comments
Cannot confirm, Close steam entirely (SDL will not be able to exclusively access the Pro controller and will disappear from the control selection list) with steam open |
If you're running Cemu through Steam (for screenshot taking or other reasons), right-click on its library entry -> controller -> disable Steam Input. This is what I have to do for Cemu (and other emulators) to recognize my PS4 controller. I'd assume the same is true for Switch Pro as well. |
I have the exact same issue on macOS 14.3.1 and no I'm not on steam, going back to 2.0-65 solves the problem |
Same fix applies, delete the profile from the controllerprofiles folder, add the controller again. |
Remove and re-add Switch Pro [SDLController] from input settings fixed this for me. Wondering if I have to do this every time when I've used Steam inbetween Cemu? |
can't make my steam controller work on Cemu 2.0-80 on macOS. It is detected by Cemu, but won't work. Do you have some tips? |
Current Behavior
As of Cemu 2.0-66, the Switch Pro Controller is no longer working properly. Cemu does recognize the controller when looking for an SDL one as seen here
But no buttons or sticks are receiving any inputs anymore. I could confirm this was specifically related to 2.0-66, since downgrading to 2.0-65 made my controller work properly again.
Expected Behavior
For the controller to work as it did in 2.0-65, where every input was recognized.
Steps to Reproduce
Update from 2.0-65 to 2.0-66
System Info (Optional)
OS: Windows 10
GPU: RTX 3080
Emulation Settings (Optional)
No response
Logs (Optional)
No response
The text was updated successfully, but these errors were encountered: