cvan
commented
9 years ago What's the "ideal" solution here? I imagine ideally we could work well in 2d with mouse look if no VR device is found. Also ideally perhaps we automatically enter VR mode if a device is found?
There's a lot of CSS necessary for the 3D transform stuff to be backwards compatible with 2D mode. Last time I discussed this with @jcarpenter, it was said that it wasn't worth the time investment. I know months ago you, @KevinGrandon, expressed the desire to be able to dogfood Horizon as your 2D browser (hence your desire to retain parity with tab functionality, and so forth).
I think @jcarpenter had wanted us to just have only the "Enter VR" button and some graphic welcome screen (possibly related to #153, though I had originally intended for that to cover more of a welcome screen once VR mode is entered) that tells the user that you must be in VR mode to enjoy Horizon.
Once you enter VR mode, ideally we'd always have the stereo VR view mirrored on the display (on Windows, we have Direct to Rift; @caseyyee knows more here).
Related: one of the awesome benefits of projects that use the webvr-boilerplate: WebGL WebVR sites get 2D support for free (and Cardboard support too!). I don't know if time will permit us to have that kind of awesome 2D backwards compatibility for Horizon. I know that obviously limits Horizon's uses to the 0.0001% of folks who own an Oculus HMD. I'd like to maintain though that shipping something is arguably more important now than covering all the use cases (we think people care about/need). Admittedly, shipping the wrong features can also be a risk. This is something we'll have to be mindful of.
caseyyee
What's the "ideal" solution here? I imagine ideally we could work well in 2d with mouse look if no VR device is found. Also ideally perhaps we automatically enter VR mode if a device is found?