There is no standardized way to detect gamepad button presses or axis movements. Gamepaddisconnected - indicates that a gamepad has been disconnected. Gamepadconnected - indicates that a gamepad has been connected. Sounds cool right? It's quite the contrary when you go about implementing it.Īs of now, only 2 events are supported by the gamepad API. This means that using this API, developers would be able to connect gamepads and similar input devices to the browser and be able to use them in their gaming applications. As stated in the spec - The Gamepad specification defines a low-level interface that represents gamepad devices. Turns out a few years back the W3C introduced the Gamepad specification which has been under constant development since then and has been implemented by various browser vendors (but is still subject to change). Developers had to design mouse/keyboard based interfaces for game controls that can be tricky to operate and can take some time to get used to. Using a mouse to move around is fun, but it can turn out to be quite a daunting task for gamers that prefer more natural controls like a directional pad or a joystick for character movements.įor long there has been no native support in the browser for connecting gamepads or joysticks. But on the web it's totally different, you just need a browser and either your mouse or keyboard becomes the controller.
But for games with more complex controls, it was just more viable to switch to a standard gamepad.ĭesktop games provide this flexibility to gamers majorly because they have native support for connecting external devices like gamepads and joysticks. For most games, controls mapped to a standard keyboard were fine to play with. I still vividly remember playing games on my PC, the times when detailed polygon models weren't a thing, open worlds were small and well, not that open (to be very honest) and online multiplayer gaming was still underway.
0 kommentar(er)
