Ports demo to native VR API #4
Conversation
| <title>Transformation and display for head-mounted Leap Motion Controller</title> | ||
|
|
||
| <!-- note - the light grabbing doesn't work with r68 --> | ||
| <script src="//cdnjs.cloudflare.com/ajax/libs/three.js/r67/three.min.js"></script> | ||
| <script src="http://cdnjs.cloudflare.com/ajax/libs/three.js/r67/three.min.js"></script> |
There was a problem hiding this comment.
These should be left as // for display within https iframes. Makes it harder for dev, I know :(
|
Tried a cursory test in FF - looks nice! I'm curious - would it be better to fall back to a THREE.js riftEffect if the APIs are not available? This would remove browser dependencies, at the cost of more complication (edge cases for the app dev to test, etc). Perhaps the idea is that anyone with a rift would be sure happy to upgrade their browser for VR web apps. |
|
The two scripts - VREffect & VRControls - is the idea that they would be available somewhere as 3rd party libraries? |
|
They’re already part of three.js https://github.com/mrdoob/three.js/blob/master/examples/js/controls/VRControls.js https://github.com/mrdoob/three.js/blob/master/examples/js/effects/VREffect.js I have to update the link to the builds Diego. On Oct 7, 2014, at 10:28 PM, Peter Ehrlich notifications@github.com wrote:
|
Hi from Mozilla. This patch makes one of those demos use the VR native APIs in the browser.
You need to run the demo in one of the development builds:
http://vrhelloworld.com/builds/