i’m noticing that even though the gamepad is on, that the property puzzle prints that it is false… UNTIL the first input. this may explain why the first movement i make (since app start) with the gamepad is delayed/jerky.
any way to “simulate” a gamepad input in order to have it know it’s “on” (true) to circumvent this bug?
i already have my gamepad procedures not run unless the gamepad “is_connected variable” i’ve made is “true”, that gets triggered when it gets connected/disconnected.
this is not a bug, but rather a browser security feature to prevent device fingerprinting etc without an explicit user consent. You might want to add some “Please press any key…” message upon you application startup to inform the users that they should press something to start playing with your app.