Hi all,
I’ve been having interesting discussions with a WebGL game developer, whose
employer is betting big on the Web Platform as the foundation for their games
currently in development.
I asked him what the most interesting features and improvements would be to
allow them to keep betting on the Web as their development platform of choice;
two requests surfaced as must-haves:
1. Optional access to the hardware pointer/ cursor as a possible extension to
the pointerLock(Element) API to have better performance when capturing the
cursor and the optional ability to restrict mouse movement within a rect. One
example might be:
requestPointerLock({clipRect: [0, 0, window.innerWidth, window.innerHeight],
useHardwareCursor: true})
… where clipRect could also be a DOMRect (if it can be instantiated from
content), for example. The point here is to allow for more control over the
cursor and accessibility to a more direct pointer layer.
2. Optionally bypass the browser compositor when a WebGL context is in
fullscreen mode. In this mode, WebGL draw calls would write to the OS back
buffer directly, increasing performance. Of course, this would never be
possible if the WebGL context has to be rendered amidst other HTML elements on
a web page, so that’s why the proposition here is for fullscreen mode only.
What do you think? Is WebGL game development something we ought to focus on and
cater to?
One last thing I was wondering is whether we already have settings for v-sync
and GPU switching accessible from privileged content?
All the best,
Mike.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
