Post Modern Game Input Devices
summary
Shows concrete input paths and which actually work: keyboard/mouse map to state polling, touch uses Hammer.js gesture library and still needs game-loop buffering, gamepad uses the prefixed Gamepad API, phone-as-controller uses a websocket with session IDs, voice uses the Web Speech API but requires HTTPS and server-side recognition, and motion devices like Leap Motion websocket at ~120fps and Glass sensors exposed via a Java websocket are wired into a 60Hz game loop for demos (some demos fail live).
AI-written summary · about
chapters (9)
- 0:00Start
- 1:50Here comes the Hammer
- 4:55Phone as a Gamepad
- 5:10It's called a Browser
- 6:34Camera Face Tracking
- 7:35Voice Recognition
- 9:54Leap Motion
- 13:35Project Glass
- 14:01Mirror API
related talks
42mExploring Alternative Interactions in JavaScript
29mNatural User Interface using JavaScript
29mOnce Upon A Time, Somewhere Between Your Console And Browser
14mOne control to rule them all
24mWe Will All Be Game Programmers
29mJavaScript and Game Development
33mSpecial Relativity with Video Games
34mThe past, present, and the future of HTML5 game development