Some Playstation 4 controllers don't work #7270
Comments
|
I just tested with the 8BitDo SN30 Pro in PS4 mode on Windows and macOS and it worked fine for me. If you can get a report with a log with DEBUG_PS4_PROTOCOL enabled, that would be very helpful. Thanks! |
|
How to enable DEBUG_PS4_PROTOCOL for Steam? I have 8BitDo Pro 2 controller that used to be detected as ps3 type controller when set to dinput mode and used define layout ui from large mode to save layout as ps4 type controller. config.vdf and log controller.txt confirms the server was not found when uploading the ps4 layout config so is still pending upload. The old ps3 type controller layout that Steam Input used to load is available in config.vdf but steam is now loading generic gamepad config which i cant see as being defined in config.vdf. Valve just pushed hotfix to Steam stable client to fix ps4 controller support in SDL as gyro was still being switched on even when steam input/sdl was disabled for game. Bug Report for broken ps4 and ps3 controller types when using 8BitDo Pro 2 controller in Steam for windows can be found at https://steamcommunity.com/groups/SteamClientBeta/discussions/3/3763356482614563631/ |
|
Got access to a PS4 controller PS4 non-enhanced packetsSetting enhanced mode ( |
|
Ah, good find, thanks! |
|
this issue still exists in both pcsx2 and dolphin in the latest builds with the 8bitdo SN30 Pro. reopen? |
|
This fix is in for 2.28 and 3.0. Have you tested the latest code on GitHub? |
|
I've only tested through the latest pcsx2 and dolphin builds, so probably not? Not sure how to test otherwise. I'm on macos. |
|
Okay, yeah, this fix will be in 2.26.5, released at the beginning of next month. |
|
@burnerbots PCSX2 uses SDL releases, but Dolphin is using the SDL2 branch, and should have the fix already, so the 8bitdo's might have a separate issue. Can you take this SDL dylib (unzip it), then right click on your PCSX2.app, Show Package Contents, then place it in You can use <details>
<summary>8bitdo Packets</summary>
```
packets
```
</details>to hide it by default so it doesn't take up too much space. |
|
@TellowKrinkle Yeah, it's still not working. Here's some of the stuff I got: 8bitdo Packets2023-03-13 17:26:29.079 PCSX2[51936:2531542] INFO: CRC MISMATCH: 36492fa9 != CRC(78 bytes) => 9052b162 Does that help? Cause I have no idea what it all means, haha. |
|
Yeah, looks like the 8bitdo controllers don't send valid CRCs, and instead sends I'll let @slouken decide what they want to do about that |
|
@TellowKrinkle interesting. I wonder why it worked with previous builds. I'm guessing it's a similar issue with the new dolphin builds that have SDL2 then? |
|
I upgraded my SN30 Pro to firmware version 2.00 and now I can reproduce this as well, thanks! |
I've gotten two reports for this on PCSX2 and two on Dolphin now
One of the Dolphin ones can be seen here, on an 8bitdo SN30 Pro, which apparently identifies as a PS4 controller. The rest were support requests that never got issues, with people who claimed to be using actual DS4s. Three of the four were on macOS, one on Windows.
One of the PCSX2 reporters helped me bisect it to 2ccdd06, but they disappeared before I could get a log with
DEBUG_PS4_PROTOCOLenabled. Removing the CRC check didn't help, and reverting a larger portion of the commit didn't until I removed theHIDAPI_DriverPS4_IsPacketValidcall, so my best guess would be something in thek_EPS4ReportIdUsbStatecase, but I'm still waiting for someone with the issue to reappear...The text was updated successfully, but these errors were encountered: