HTML5/WebGL source port of Quake
github.com
github.com
* Local config storage (doable in cookies or localstorage)
* Local save storage (probably too big to fit in 5MB of localstorage)
* Mouselook (mouse buttons work fine). I think you can already do this though, I know you can at least track cursor position and you can implement mouselook off that.
* Mousewheel in firefox, at least, wasn't rebindable.
* I see problems in fullscreen browser games that take every single browser button and override it, so you would probably want a "you can't rebind this key" key. If there isn't already one.
Tracking view position from mouse coordinates has always been possible, but handling mouse focus and coordinate wrapping is necessary for games with mouse look. The really tricky bit is that there are security implications in much the same way as full screen mode.
See here for details on Pointer Lock: http://www.chromium.org/developers/design-documents/mouse-lo...
We'll be 15 years behind the PCs of 15 years from now[1].
[1] Unless something changes drastically in the web stack.
Do we need all the power a PC provides natively to make great games?
I think the market has declared this to be a definitive "yes". Users don't want to waste their hardware dollars so that you can spend them on inefficient solutions.
When your competition takes advantage of the hardware, and you don't, then your application (or game) falls behind in the marketplace.
There's the argument that users are willing to have lesser performance ... for lesser cost. This is true, but quite different from your code performing more poorly than your competition's on the same hardware.
Also, quite scary how well you remember the maps, 15 years later.
Although the controls are really weird, right click goes forward, I can't aim with the mouse...
If pointer-lock only works in element-fullscreen in Firefox (on which he develops) then what other choice is there ? Nobody plays shooters with the keyboard since wolf3d, and the BananaBread demo does pointer-lock precisely via element-fullscreen.
Just kidding. :)
Running smooth in Chrome Canary.
There is an open question as to how html5 now compares to native some years ago since that's how (for gaming) it should be judged. I believe we will reach a limit point and in the long term, maybe the browser-related inefficiencies will just be marginal to the end user experience.
* mouse look is really what is missing.
16 on March 15
Running smoothly on Linux, tested on Firefox and Chrome.