Either chrome or playground should be responsible for using only actualy gamepads as gamepad inputs. While on the documentation website, my mouse reciever is registered as a gamepad.
Ideally, this would not be much of an issue, and the code should still run without errors. Although you might get unexpected controller numbers.
Currently, because the usb receiver does not have any axes, playground will crash when assuming that all controllers have 4 axes to register.
Here is an image of the devtools window at the line of code that falls over currently:
Either chrome or playground should be responsible for using only actualy gamepads as gamepad inputs. While on the documentation website, my mouse reciever is registered as a gamepad.
Ideally, this would not be much of an issue, and the code should still run without errors. Although you might get unexpected controller numbers.
Currently, because the usb receiver does not have any axes, playground will crash when assuming that all controllers have 4 axes to register.
Here is an image of the devtools window at the line of code that falls over currently: