-
Notifications
You must be signed in to change notification settings - Fork 116
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
Vibration / rumble stops working after reconnecting the controller [Xbox Series S] #444
Comments
This is a known issue due to how xpadneo offers rumble support to games, and games using the wrong SDL API to query rumble support. We can probably work around this from the xpadneo side, but the SDL project lately stated that games really should use a different API to query for rumble support. Until then, you should be able to work around it by disabling the welcome rumble in the driver. This tightens the time frame between device detection and offering the rumble feature which will probably work around that race condition in SDL - at least most of the time. |
Thank you :)! Is there a way to disable the welcome rumble without commenting the function in the code? I can't seem to find any option in the configure.sh script |
;-) So you actually add that parameter to the module load options. |
Working! Thanks again ! : ) |
Thanks for confirming. Please leave this opened so I can implement a fix. |
The newer API is also not applicable for some use cases, for example some emulators emulate controllers that have wildly different layouts than SDL2 expects for modern games. Was it ever confirmed that the newer API even fixes this? |
Just wanted to say that I was also having this issue and that disabling ff_connect_notify also fixed this for me on a Gulikit KingKong2 Pro controller. Disabled using |
@RobotRoss I closed your other report as duplicate then. You can apply the setting permanently:
The next version will disable that by default, or switch to a different method. |
That issue should be reopened, seems to be a different problem. See comment on the other issue. |
Version of xpadneo
#434 latest commit
Controller Model
Connection mode
Installed Software
Protocol Information
Please help us identify at which layer the problem can be found if you want
to report mapping errors or if the controller fails to be detected:
evtest
is showing issues (describe the issues below)BTN_NORTH
andBTN_WEST
are intentionally swappedjstest
is showing issues (describe the issues below)gamepad-tool
is showing issues (post console output below)Please describe how it is failing below in the next sections.
Severity / Impact
Describe the Bug
Vibration / rumble works when starting the game but after reconnecting the controller with the game opened (power off -> power on) it stops working. For example if it turns off because of inactivity and then you power it on again
Steps to Reproduce
Expected Behavior
Vibration / rumble should start working after restart of the game
Observations / workaround
I found out that I could re-enable the vibration / rumble by closing and opening the game again.
I also observed that the welcome rumble start plays correctly even after the restart of the controller
System Information
I also tried with the latest Nobara Linux Kernel (6.59 fsync 201)
Controller and Bluetooth Information
Bus 003 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
xpadneo-btmon.txt
xpadneo-dmesg.txt
xpadneo-lsusb.txt
The text was updated successfully, but these errors were encountered: