Re: landing soon: core APIs for VR
On 19/11/14 17:15, Vladimir Vukicevic wrote: > - Figure out how to ship/package/download/etc. the Oculus runtime > pieces. The last discussions on these were that you were planning to approach Oculus to enquire about getting them under an open source license. How did that go? If that's not going to happen, what is your current proposal for how we deal with that? I'm sure the APIs you are adding are device-agnostic; but what's the plan for extending device support? Do we just tell other device manufacturers what our interface is and get them to write their own glue? Gerv ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: landing soon: core APIs for VR
On a related note: I added dev-doc-needed to these bugs for you, since nobody had already done so. > On Nov 19, 2014, at 12:15 PM, Vladimir Vukicevic wrote: > > We've had a lot of excitement around our VR efforts and the MozVR site, and > we want to capitalize on this momentum. Very soon, I'll be landing the early > support code for VR in mozilla-central, pref'd off by default. This includes > adding the core VR interfaces, display item and layers functionality for VR > rendering, as well as supporting code such as extensions to the Fullscreen > API. Eric Shepherd Developer Documentation Lead Mozilla Developer Network Blog: http://www.bitstampede.com/ Twitter: http://twitter.com/sheppy ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: landing soon: core APIs for VR
On Nov 19, 2014, at 12:15 PM, Vladimir Vukicevic wrote: > > We've had a lot of excitement around our VR efforts and the MozVR site, and > we want to capitalize on this momentum. Very soon, I'll be landing the early > support code for VR in mozilla-central, pref'd off by default. This includes > adding the core VR interfaces, display item and layers functionality for VR > rendering, as well as supporting code such as extensions to the Fullscreen > API. Will the docs team have access to anyone who can answer questions or help produce sample code snippets? Having access to help like that will make it easier for us to justify giving time to this topic for documentation (since the less we have to scrounge for info, the faster we can get it done). This is an exciting topic, and in combination with things like WebGL, WebRTC, and so forth, it has enormous potential! Eric Shepherd Developer Documentation Lead Mozilla Developer Network Blog: http://www.bitstampede.com/ Twitter: http://twitter.com/sheppy ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
landing soon: core APIs for VR
Hi all, We've had a lot of excitement around our VR efforts and the MozVR site, and we want to capitalize on this momentum. Very soon, I'll be landing the early support code for VR in mozilla-central, pref'd off by default. This includes adding the core VR interfaces, display item and layers functionality for VR rendering, as well as supporting code such as extensions to the Fullscreen API. Core VRDevices API: https://bugzilla.mozilla.org/show_bug.cgi?id=1036604 Layers/gfx pieces: https://bugzilla.mozilla.org/show_bug.cgi?id=1036602 Fullscreen API extensions: https://bugzilla.mozilla.org/show_bug.cgi?id=1036606 https://bugzilla.mozilla.org/show_bug.cgi?id=1036597 This code is sufficient to perform WebGL-based VR rendering with an output going to an Oculus Rift. None of the CSS-based VR code is ready to land yet. Additionally, this won't work out of the box, even if the pref is flipped, until we ship the Oculus runtime pieces (but initially instructions will be available on where to get the relevant DLL and where to put them). The following things need to take place to pref this code on by default for nightly/aurora builds (not for release): - Figure out how to ship/package/download/etc. the Oculus runtime pieces. - Add support for Linux - Add basic tests for VRDevice APIs Beyond that there is a lot of work left to be done, both around supporting additional headset and input devices (Cardboard, etc.) as well as platforms (Android, FxOS), but that can be done directly in the tree instead of needing to maintain separate one-off builds for this work. - Vlad ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform