Reinstalled Chrome .deb, Version 79.0.3945.79 (Official Build) (64-bit) according to this solution: https://community.stadia.com/t5/The-Stadia-Controller/How-to-link-controller-in-Ubuntu/td-p/4388
Relatively minor issue. Stadia controller does not vibrate. On the Stadia homepage, the "Connect a controller" prompt shows as if a controller is not connected, but inputs work fine and gameplay is perfect, so I believe the site thinks this is a third-party controller.
@Cicero Unfortunately I don't actually have a Linux machine to test against so I'm not able to help troubleshoot beyond the general advice given in other threads. If you haven't already, please be sure to use the in-app feedback option to let the developers know about this issue. ![]()
Maybe @GraceFromGoogle can provide guidance?
@StadiaTeam This is caused by an incorrect vibrationActuator property being set via the HTML5 Gamepads API for Ubuntu Chrome. There is no way for the browser to tell the controller to vibrate, in essence.
In Windows:
> navigator.getGamepads().item(0).vibrationActuator
GamepadHapticActuator {type: "dual-rumble"}
In Linux/Ubuntu:
> navigator.getGamepads().item(0).vibrationActuator
null
In Windows, it is easy to tell the controller to vibrate via:
navigator.getGamepads().item(0).vibrationActuator.playEffect("dual-rumble", {
startDelay: 0,
duration: 1000,
weakMagnitude: 1.0,
strongMagnitude: 1.0
})
Where this fails in Linux/Ubuntu Chrome builds, because the vibrationActuator property is null. I will attempt to debug this further but I am limited in my ability given that I don't know a lot about how the controller announces itself to the Gamepad API (and don't have a lot of experience with it in general).
@Cicero Thanks for opening that bug - and for linking it here. I've been following it to see how things shake out.
Have you had a chance to test if enabling that additional udev rule and replugging the controller makes it ready to rumble?
sudo sh -c "echo 'KERNEL==\"hidraw*\", SUBSYSTEM==\"hidraw\", ATTRS{idVendor}==\"18d1\", ATTRS{idProduct}==\"9400\", MODE=\"0666\"' > /etc/udev/rules.d/50-stadia.rules"
This udev rule fixes the problem! Thanks! ![]()