@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 es...
See more...
@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).