-
Notifications
You must be signed in to change notification settings - Fork 22
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
[Steam Deck] Major performance hit when using DualShock due to rumble #55
Comments
What input / joypad driver is RetroArch using on your Steam Deck system? |
SDL2. |
OK, if you change it to some other input/joypad driver combo, you don't get the same performance dropoff? |
That's correct, yes |
Crosspost from libretro/beetle-psx-libretro#872 (comment)
|
Wouldn't be the first time Steam messes something up. It does sound like more of a problem with the SDL2 driver, as SwanStation (and Beetle PSX from the looks of it) don't do anything special to achieve rumble that the other cores you mentioned do. Regardless of that though, the only thing I could do on my end is to add the same option from ReARMed to SwanStation so people can at least use the DualShock without having to deal with an increased performance requirement. |
Description
Crosspost from libretro/beetle-psx-libretro#872
When using the Analog Controller (DualShock) controller profile on the Steam Deck, performance takes a major hit (E.G. Crash Bandicoot Warped, using default settings, and Vulkan renderer at 3x, witnessing a drop from around 300fps to around 130fps when fastforwarding without the use of the Powertools plugin) due to apparently the rumble polling, as commenting out
swanstation/src/libretro/libretro_host_interface.cpp
Lines 1305 to 1306 in 9c2ed9e
gives me the same fps when not using the DualShock profile.
Trying out the same situation on my Windows 11 PC, using the XInput controller driver vs the SDL2 controller driver used on the Steam Deck, shows no such performance hit.
Expected behavior
Be able to use the DualShock controller profile without having to incur a (major) performance penalty.
Actual behavior
As per the description, a major drop in fps occurs
Version/Commit
Environment information
The text was updated successfully, but these errors were encountered: