Project

General

Profile

Actions

Emulator Issues #13155

open

8bitdo SN30 Pro Bluetooth Controller Mapping Not Working on macOS Monterey

Added by NiMi over 1 year ago. Updated 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
OS X
Issue type:
Bug
Milestone:
Current
Regression:
Yes
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

N/A

Game ID? (right click the game in the game list, Properties, Info tab)

N/A

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

N/A

What's the problem? Describe what went wrong.

Description

I am unable to map a controller in dolphin. This is the only controller I have to test with so I can not say whether the issue applies to other controllers or not. I am able to map keys with keyboard.

What steps will reproduce the problem?

Steps to reproduce

  1. Pair an 8bitdo SN30 Pro Controller with the MacBook Air
  2. Observe that the controller works fine to control the mac/other applications
  3. Open Dolphin
  4. Open Controllers
  5. Configure a Standard GameCube controller OR emulated Wii Remote
  6. Select the controller in the dropdown on the top left
    • Note: It shows up as a Dualshock 4 Wireless Controller
  7. Click a button to map & try to press it on the controller
  8. Observe that dolphin does not wait for input, no button gets mapped

This issue is present in both the latest stable and development versions of dolphin.

Current stable version: 5.0
Current development version: 5.0-18349

Is the issue present in the latest stable version?

Yes, 5.0

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

N/A

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

N/A

What are your PC specifications? (CPU, GPU, Operating System, more)

System Information

macOS Monterey
version 12.2.1
MacBook Air (Retina, 13-inch, 2018)
Processor: 1.6 GHz Dual-Core Intel i5
Memory: 8 GB 2133 MHz LPDDR3
Graphics: Intel UHD Graphics 617 1536 MB
Controller: 8bitdo SN30 Pro Bluetooth

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

N/A

Actions #1

Updated by burnbot over 1 year ago

I have the same controllers with the same problem on an M1 mac. Have you tried the 5.0-16101 build from the dolphin page? Downgrading to that seemed to work for me. It seems like the new builds don't detect the same inputs as the 16101 build (SDL/0/Controllername).

Actions #2

Updated by NiMi over 1 year ago

burnbot wrote in #note-1:

I have the same controllers with the same problem on an M1 mac. Have you tried the 5.0-16101 build from the dolphin page? Downgrading to that seemed to work for me. It seems like the new builds don't detect the same inputs as the 16101 build (SDL/0/Controllername).

Gave it a try. I can confirm that it is working (albeit finicky) in 5.0-16101!

Actions #3

Updated by JMC4789 over 1 year ago

It's a bug in SDL2.26 - it'll likely get resolved by them down the line.

Actions #4

Updated by JosJuice over 1 year ago

  • Milestone set to Current
  • Regression changed from No to Yes
  • Operating system OS X added
  • Operating system deleted (N/A)
Actions #5

Updated by burnbot over 1 year ago

JMC4789 wrote in #note-3:

It's a bug in SDL2.26 - it'll likely get resolved by them down the line.

do you (or anyone else?) know what the most recent version is that doesn't use SDL2.26?

Actions #6

Updated by TellowKrinkle over 1 year ago

I made an issue on the SDL GitHub: https://github.com/libsdl-org/SDL/issues/7270

If anyone has one of these broken controllers and is able to build SDL from source, please uncomment this line of SDL, build Dolphin against it (alternatively, take the dylib and swap it in to a PCSX2 build, since PCSX2 uses a dylib for SDL), then run Dolphin/PCSX2 from the terminal and it should spam you with logs about PS4 controller packets. Take some of those logs and post them to the SDL issue.

Actions #7

Updated by TellowKrinkle about 1 year ago

This should hopefully be fixed in 5.0-18700, can you check and make sure?

Actions #8

Updated by burnbot about 1 year ago

I still have the same problem in 5.0-18720. the SDL/0/DUALSHOCK 4 Wireless Controller is not detected.

Actions #9

Updated by burnbot about 1 year ago

burnbot wrote in #note-8:

I still have the same problem in 5.0-18720. the SDL/0/DUALSHOCK 4 Wireless Controller is not detected.

Just to clarify a bit: the "Input/0/DUALSHOCK 4 Wireless Controller" and "SDL/0/PS4 Controller" inputs ARE detected in the newest versions, but for some reason, 8bitDo SN30 Pro with the most recent firmware is not sending through those "ports". In prior Dolphin builds (my current working version is 16793), the "SDL/0/PS4 Controller" detected input is replaced with "SDL/0/DUALSHOCK 4 Wireless Controller", which is both detected and working (in 16793).

Hope that helps?

Actions #10

Updated by Billiard26 2 months ago

SDL has been updated. Is this still an issue?

Actions

Also available in: Atom PDF