TheTee82
commented
2 years ago I can confirm the force feedback issue with Dualsense controllers since a few weeks now.
System Information
- Steam client version (build number or date): Jan 16 2022 17:34:43 ( 1642451672 )
- Distribution (e.g. Ubuntu): manjarolinux 21.2.2
- Opted into Steam client beta?: Yes
- Have you checked for system updates?: Yes
steam.sh[44878]: Running Steam on manjarolinux 21.2.2 64-bit
steam.sh[44878]: STEAM_RUNTIME is enabled automatically
setup.sh[44952]: Steam runtime environment up-to-date!
steam.sh[44878]: Steam client's requirements are satisfied
Startup - updater built Jan 16 2022 17:34:43
Opted in to client beta 'publicbeta' via beta file
You are in the 'publicbeta' client beta.
Installing breakpad exception handler for appid(steam)/version(1642451672)
[Installing breakpad exception handler for appid(steam)/version(1642451672)
Loaded SDL version 2.0.20-7009179Issue: Force feedback of DualSense behaves 'weird' since a few weeks - both wired and via bluetooth
- when running native 'Shadow of the Tombraider' ( 750920 )
- rumble/force feedback timings seem way off (short to medium feedback vibrates very long)
- controller seems to have queued the (too long/wrong) feedback
- resulting in controller rumbling even after completely closing the game for a minute or so
- when running proton 'Mass Effect Legendary Edition' ( 1328670 )
- controller gets a lot of short bursts of feedback instead of medium to long feedback (eg. when scanning a planet in ME2)
- resulting in the short bursts continuing long after the "event" has finished
- when running proton 'Yakuza: Like a Dragon' ( 1235140 )
- when bumping in to pedestrians and some special moves controller gets several short bursts of feedback instead of single/normal feedback
- same behaviour like Yakuza and Mass Effect could be found in several other titles. eg: 'The Legend of Heroes: Trails of Cold Steel ( 538680 )', 'Cloudpunk ( 746850 )', etc.
Additional Info
When using fftest tool (included in linuxconsole package in pacman):
- find connected controller / Handler event-number using
cat /proc/bus/input/devices(eg.Handlers=event24 js0) - run
fftest /dev/input/event24Uploading effect #0 (Periodic sinusoidal) ... OK (id 0)Uploading effect #4 (Strong rumble, with heavy motor) ... OK (id 1)
- OK: feedback only last as long as test runs and stops when canceling test
Controller Info
Local Device Found
type: 054c 0ce6
path: sdl://3
serial_number: - 0
Manufacturer:
Product: PS5 Controller
Release: 0
Interface: -1
Controller using HIDAPI driver, vid=54c, pid=ce6
!! Steam controller device opened for index 0.
Steam Controller reserving XInput slot 0
Controller using HIDAPI driver, vid=54c, pid=ce6
BYieldingQueryAccountsRegisteredToController
CClientJobFetchPersonalizationFileID
lavadrop
Your system information
Please describe your issue in as much detail as possible:
In some games, that using steam input api, vibration periodically interrupts, even if vibration in game supposed to be persistent all the time. For some games, its like interrupt for 3 second every 10 seconds(so, 10s vibration, 3s not, 10s vibration and so on). Issue is both with bluetooth and wire modes. Also, that is very strange, vibration "unstucks" and resumes when i pressing any buttons on controller or pressing triggers. Affected games: Dirt Rally 2.0(proton, as x360 input, even this option is disabled in steam controller menu for this game), Shadow of the Tomb Raider(native, as ds4 input). Non-affected games: Forza Horizon 4(proton, as x360 input).
Shadow of the Tomb Raider specifics: Every time when alt-tabbing back to game, controller vibrates a few seconds, even if it's not supposed.
Steps for reproducing this issue: