Game: rumble continues 5-10 s after releasing a charged sword spin (Y) (Linux, nightly-627 + PRs) #1924
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1924
Loading…
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?
What happens
Holding Y to charge the sword spin and then releasing it leaves the controller rumbling for about 5–10 seconds after the spin and its sound have ended.
Build
v3.0.0-n627-g93e8237d, built from nightly-627afc4d1ad+ #1642, #1870, #1893, #1914, #1909/#1911 (off), Linux, RX 9070 XT.bin/holdslibSDL2-2.0.so.0,longshot,longshot_vk.so— norenhdrum.so, so this is the SDL motor path (HOS_RUMBLE_BACKENDauto resolves to motors for the pads here).Settings and pads
longshot_options.ini:vibration=0(Auto),rumble_strength=100. Controllers connected during the session: Flydigi Vader 4 Pro (SDL, gyro) and two Xbox userspace pads; which one rumbles needs confirming.What I would look at
host/pad_sdl.csends SDL a 1 s rumble effect and re-sends it every 0.5 s while the amplitude is nonzero; a change to zero is sent at once. A 5–10 s tail therefore means either the game keeps sending a nonzero value after the release (the vibration handle/pattern is not being stopped), or the zero does not reach this pad. Thehid: vibration #…lines (first six) and the every-4096hid: … vibration values, strongest …line should say which.Worth testing:
HOS_HD_RUMBLE=0andHOS_RUMBLE_BACKEND=motorsvshd— I can do that here when the PC is free and add the log.Expected
The rumble stops when the charged spin ends.
I have no log from the session yet; I can capture one with the switches above on request.
Possibly related, for context:
Update, and closing as not a confirmed bug: with the game's Vibration row Off the stuck rumble does not happen. Controller: Flydigi Vader 4 Pro (SDL, gyro). I filed this without a reproduction or log, which I should not have done. If it is reported again with Vibration on, it should come with the
hid: vibrationlines and theHOS_HD_RUMBLE=0/HOS_RUMBLE_BACKEND=motorscomparison. The workaround for now is Vibration Off.