4 ms·
FPS isn't really an issue for web games, it's input latency. Current browsers add something like a 60ms delay to every input event, and there isn't any fast pa
by 33a 12y ago
FPS isn't really an issue for web games, it's input latency. Current browsers add something like a 60ms delay to every input event, and there isn't any fast path for translating inputs to events on screen. This makes it very difficult right now to create fun and fast paced interactive games in HTML5.
- kevingadd 12y agoInput latency is an issue, sure, but saying that framerate doesn't matter is just ignorant. The existence of attempts at improving throughput (like asm.js and NaCL and Dart) demonstrates that performance is still a serious concern for developers. Also, keep in mind that high throughput - necessary for delivering a consistent 60FPS - will naturally reduce input latency by reducing the length of frames and the amount of time spent not pumping input messages. P.S. It's my understanding that gamepad input in both Firefox and Chrome is not buffered in any fashion, so that's going to be low-latency.