mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #218] [BUG] DualSense controller causes massive FPS drop (45-55 FPS vs 120+ FPS) if split_lock_detect enabled #147
Labels
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#147
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Gylfkxjyjdll on GitHub (Jun 28, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/218
When connecting a DualSense controller via USB or Bluetooth, all games experience severe framerate drops (from 120+ FPS down to 45-55 FPS). This persists across multiple titles but does not occur with other controllers. Performance immediately recovers upon disconnecting the controller or relaunching games without the controller connected.
System & Environment:
OS: Linux Debian 12.11
Kernel: Linux 6.14.5-1-bpo12-pve
Steps to Reproduce:
Launch a game
Ensure stable framerate without controller
Connect DualSense controller via USB or Bluetooth (moonlight)
Observe immediate FPS drop to 45–55 FPS.
Disconnect controller → FPS returns to normal.
Expected Behavior:
Steady FPS (60+) regardless of DualSense connection, matching behavior of other controllers.
Workaround:
Adding split_lock=off to kernel parameters resolves the issue.
my grub parameter atm:
GRUB_CMDLINE_LINUX_DEFAULT="nouveau.blacklist=1 quiet nvidia-drm.modeset=1 intel_iommu=on systemd.unified_cgroup_hierarchy=false split_lock_detect=off"@ABeltramo commented on GitHub (Jun 28, 2025):
Thanks for the details, after a quick search I've found this article and https://github.com/ValveSoftware/steam-for-linux/issues/8003
Sounds like something that we should be able to address user land in Inputtino, possibly something silly with how we use uhid..
@Strykar commented on GitHub (Jul 1, 2025):
The old
split_lock_detectis now a sysctl tunable namedsplit_lock_mitigatesince kernel 6.2 - https://wiki.archlinux.org/title/Steam/Game-specific_troubleshooting#Split_lock_detection_/_mitigation@Gylfkxjyjdll commented on GitHub (Sep 19, 2025):
I am uncertain if this issue has been resolved, but I have tested this with my DualSense controller again and have not experienced this significant FPS drop. This issue can be closed.