RPCS3
[Bug] DS3 Handler BT Input Issues
Quick summary
When using the DS3 handler via Bluetooth, there's a noticeable lag in actions over time making it nearly unusable. However, I couldn't reproduce this while using the SDL handler or with my DualShock 4 using it's native handler.
There's also another issue where saving in Pads while using the DS3 handler it makes an input of both sticks, this one also happens while wired but I'm just mentioning it here as I don't think it's important enough to warrant an issue for it.
Details
I tried checking if it was a regression but I went as far as I could (as far as the builds picked my GPU and didn't crash), but was still seeing this happen so this is why I opted to fill it as a bug. Worth mentioning that this doesn't happen on Windows and it not happening with my DS4 or with the SDL handler rules out it being poor connection. I also tried 2 different controllers and both behave the same way, so this seems to be a Linux and a DS3 handler specific issue.
Will attach logs and videos from both Windows and Linux, not sure how useful will the logs be for this, but if there's a better way of diagnosing this, I'm open to try.
Linux
The most relevant out of the 4 is the first one since you can see how doing the same motions with the DS3 handler and the SDL handler, the first one ends up acting up and going around while the other stays in place.
I'll upload footage later of actual gameplay to show how bad it actually gets.
EDIT: Gameplay
0:20 and 0:40 are the most evident (if can't tell in normal speed, change to 0.5 and see the delay between input and camera) Throught the match this happens often.
Attach a log file
BluetoothLinux.log WiredLinux.log
BluetoothWindows.log WiredWindows.log
Attach capture files for visual issues
No response
System configuration
Fedora 41 5800X RX 7800XT
Other details
No response
I think I may have ran into that issue yesterday. Using an 8bitdo pro 2 on Windows 10 with a USB bluetooth adapter. I tested other games on my computer/steam and had no delay but with MGO it would happen over time. If I unplugged and replugged the adapter it went away for a while.
Not sure if this is useful but I found a good way to reproduce/test it is to just to run in circles quickly. I would stop spinning and my character would do a couple more laps. It seemed to get worse after putting a lot of stress on it.
I think I may have ran into that issue yesterday. Using an 8bitdo pro 2 on Windows 10 with a USB bluetooth adapter. I tested other games on my computer/steam and had no delay but with MGO it would happen over time. If I unplugged and replugged the adapter it went away for a while.
Not sure if this is useful but I found a good way to reproduce/test it is to just to run in circles quickly. I would stop spinning and my character would do a couple more laps. It seemed to get worse after putting a lot of stress on it.
I don't think is the same issue because as described, I only experience this with the DS3 handler while using it via BT under Linux. Using SDL with my DS3 or my DS4 with SDL or DS4 handler I have zero issues, so it's seems like a totally different issue to me at least.
Here are 2 more game comparisons, again DS3 handler vs SDL handler both via BT:
GT5 DS3 Handler GT5 SDL Handler
LBP DS3 Handler LBP SDL Handler
In both it can be appreciated the delay in inputs, in GT5 is nearly impossible to correct the movement of the car while in LBP jumping and the character movement is delayed, I tried to emphasize this by doing corrections of the character movement and while jumping.
(Sorry for the lack of audio, lol)
the lag when BT is used seems to be present also on Windows (tested on killzone 3). The lag seems not present using wired DS3 handler or using SDL handler (wired and BT))
This is still a problem on version RPCS3 0.0.37-18022-9c93ec0b Alpha. It makes rhythm games like Project Diva f 2nd unplayable. Workaround is using SDL handler instead of DS3 handler.
