Browser support

"BigRobCoder" wrote:

"unsafe" wrote:
For the sensor data, I'm building an NSAPI browser plugin using FireBreath which will provide javascript bindings for LibOVR. I'll post an update when it's ready; if anybody has experience building on FireBreath, feel free to contribute.

https://github.com/grimwire/ohmd-plugin

Isn't NSAPI used for web server plugins? Did you mean NPAPI, or am I missing something?

You're right, I meant NPAPI. Thanks

"unsafe" wrote:

"BigRobCoder" wrote:

"unsafe" wrote:
For the sensor data, I'm building an NSAPI browser plugin using FireBreath which will provide javascript bindings for LibOVR. I'll post an update when it's ready; if anybody has experience building on FireBreath, feel free to contribute.

https://github.com/grimwire/ohmd-plugin

Isn't NSAPI used for web server plugins? Did you mean NPAPI, or am I missing something?

You're right, I meant NPAPI. Thanks

Cool, that's what I figured, just wanted to make sure we're on the same page before diving in on this :)
I forked your project on github and filled in the "get_orientation()" stub. Using my Rift, I was able to get (what appears to be) correct orientation data in Chrome!
The github URL is https://github.com/BigRobCoder/ohmd-plugin (build/install the plugin and run pluginTest.htm in Chrome). Note that it's a little messy right now :oops: , I wanted to post this before bed.

here is a guy whose already added chrome support and has some examples. Not sure how far you guys have made it. I'm looking at working with this.

https://github.com/benvanik/vr.js

Did work on this continue, or end after vr.js made its appearance? I'm strictly a web developer, and would be interested in seeing where this goes.

"wildermuthn" wrote:
Did work on this continue, or end after vr.js made its appearance? I'm strictly a web developer, and would be interested in seeing where this goes.

I got distracted by another project, by the time I returned vr.js had appeared, I plan to use that now. Don't know about the original author.

This is great! was just thinking today what a 3d web would be like and whether anyone was talking about it.

how are people generally getting this up and running currently? was thinking about how it would be better to have a oculas specific browser so that you can add VR specific html tags and js requests etc. I was thinking it could display current sites in a meaning-full manner, followed by VR enhanced sites, then VR only sites taking full advantage. - this also feeds into my thoughts on UI for a VR web and desktop.

anyways, good to hear your thoughts and examples

"bbyford" wrote:
This is great! was just thinking today what a 3d web would be like and whether anyone was talking about it.

how are people generally getting this up and running currently? was thinking about how it would be better to have a oculas specific browser so that you can add VR specific html tags and js requests etc. I was thinking it could display current sites in a meaning-full manner, followed by VR enhanced sites, then VR only sites taking full advantage. - this also feeds into my thoughts on UI for a VR web and desktop.

anyways, good to hear your thoughts and examples

VR specific tags could be created as web components. One way might be to use three.js and polymer-project together with vr.js. If polymer is too bleeding edge, then angularJS could be an alternative for now, it will also probably use polymer in the future.

this would be amazing!:)

Hi,

We're currently thinking about creating something more generic than a browser's plug-in. As modern browsers support "Device Orientation API", we'd like to create our own Windows driver to take Oculus data and make them available as Device Orientation data. In this way, no need for browser plugin and it will work in any browser: Chrome, Firefox & IE11.

The idea is to add support for Oculus in our WebGL engine: BabylonJS: http://www.babylonjs.com . We would then make this driver available on github.

We've started looking at Windows sensor driver sample. But I'm looking for documentation on how to grab the data from the Oculus from our own driver. Can we build a filter driver on top of the Oculus one? Has anyone ever think about doing something similar?

Bye,

David

I don't think anyone has tried exactly what you are saying, but it seems possible.