You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
8BitDo Controller - No Vibration/Rumble on Host #697
Using latest nightly of Vibepollo, when switching my setup back to playing on my host PC without streaming, playing any steam games the vibration doesn't work any longer.
I can ping the controller through the steam controller settings and it will send a vibration to the controller and I can feel it, but in game (tested multiple games) there is no vibration getting sent to the controller.
Could there be an issue with the built in Vibepollo controller drivers, that when not streaming, a lingering background driver is intercepting the vibration signal and not sending it to my physical controller?
Controller is 8bitdo ultimate 2 wireless, connected VIA 2.4ghz dongle and using d-input mode.
Before, it would work just fine when playing natively on the PC, vibration and everything worked just fine, but now there is none.
Could you share the exact Vibepollo version/build and Windows version, one affected game, its Steam Input setting, and the configured Emulated Gamepad Type? If possible, please attach a redacted host log covering the last stream ending and the subsequent local game attempt; remove private addresses, credentials, and pairing data.
After disconnecting, does Steam or Windows list another controller besides your 8BitDo, and is the streamed application still paused or running? If convenient, does local in-game rumble return after fully exiting Vibepollo, or after a normal reboot before starting another stream? There is no need to uninstall drivers or change controller settings for this check. The Steam vibration test shows the controller can vibrate, but does not yet establish where game feedback is going.
Host OS: Windows 11 Home 25H2 26200.9711
Game I tried on: Phantom Blade 0, Wo Long, Crimson Desert
Steam input settings: I tried all games with steam input enabled, disabled and default.
Vibepollo emulated Gamepad Type: Vibepollo Virtual Gamepad (Xbox Series)
After disconnecting and going over to the host, checking joy.cpl in RUN, it shows only mt 8Bitdo Ultimate 2 connected, no other controllers.
When I try this on my host, I've disconnected the stream from my client and ended the session. I've also restarted my host PC and after logging in, closed Vibepollo off from the system tray and tried again.
Activity
Nonary commentedon Oct 31, 2026
Could you share the exact Vibepollo version/build and Windows version, one affected game, its Steam Input setting, and the configured Emulated Gamepad Type? If possible, please attach a redacted host log covering the last stream ending and the subsequent local game attempt; remove private addresses, credentials, and pairing data.
After disconnecting, does Steam or Windows list another controller besides your 8BitDo, and is the streamed application still paused or running? If convenient, does local in-game rumble return after fully exiting Vibepollo, or after a normal reboot before starting another stream? There is no need to uninstall drivers or change controller settings for this check. The Steam vibration test shows the controller can vibrate, but does not yet establish where game feedback is going.
EmilG88 commentedon Oct 31, 2026
sunshine-20261030-201830-216.log
sunshine-20261030-183039-143.log
Host OS: Windows 11 Home 25H2 26200.9711
Game I tried on: Phantom Blade 0, Wo Long, Crimson Desert
Steam input settings: I tried all games with steam input enabled, disabled and default.
Vibepollo emulated Gamepad Type: Vibepollo Virtual Gamepad (Xbox Series)
After disconnecting and going over to the host, checking joy.cpl in RUN, it shows only mt 8Bitdo Ultimate 2 connected, no other controllers.
When I try this on my host, I've disconnected the stream from my client and ended the session. I've also restarted my host PC and after logging in, closed Vibepollo off from the system tray and tried again.