Bug 510465 - Add feature that allows adding stick drift coordinates to a deadzone
Summary: Add feature that allows adding stick drift coordinates to a deadzone
Status: RESOLVED DUPLICATE of bug 351997
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_joystick (other bugs)
Version First Reported In: 6.4.5
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: accessibility, usability
Depends on:
Blocks:
 
Reported: 2025-10-10 16:38 UTC by Fernando M. Muniz
Modified: 2025-10-22 21:22 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Stick Drift being shown. (1.01 MB, video/x-matroska)
2025-10-10 16:38 UTC, Fernando M. Muniz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Fernando M. Muniz 2025-10-10 16:38:10 UTC
Created attachment 185659 [details]
Stick Drift being shown.

STEPS TO REPRODUCE
1. Have a game controller with stick drift
2. Look at the Game Controller page in System Settings.

OBSERVED RESULT
You'll see the stick drift, but you can't do nothing about it.

EXPECTED RESULT
Being able to "record" the stick drift coordinates and add them to a deadzone; so the game camera or the game character don't start moving around randomly.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.10.0
Kernel Version: 6.17.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-11300H @ 3.10GHz
Memory: 9 GB of RAM (8.1 GB usable)
Graphics Processor 1: Intel® Iris® Xe Graphics
Graphics Processor 2: NVIDIA GeForce GTX 1650
Manufacturer: LENOVO
Product Name: 82MG
System Version: IdeaPad Gaming 3 15IHU6

ADDITIONAL INFORMATION
My PS5 controller has stick drift.
Comment 1 TraceyC 2025-10-22 21:22:43 UTC
Thanks for the feature request. There's already a request open for this, so I'll merge this into the older one.

*** This bug has been marked as a duplicate of bug 351997 ***