-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
is webvr-polyfill compatible with the newest versions of THREE.js? #340
Comments
Three has support for WebVR via Separately, the webvr polyfill can be included to provide the WebVR API if the platform does not exist |
@jsantell I found that, in my Samsung 8 chrome browser, it is necessary to visit chrome://flags/ to enable support for vr mode there and so I will probably continue using webvr-polyfill. Do you know, is there is a way to use webvr-polyfill and three.js without VRControls and VREffect scripts, or are those scripts required for webvr-polyfill to be used with three.js? |
@jsantell is Web VR commonly supported in phone browsers? Would you still recommend using native Web VR, even though it is not supported in the current Samsung 8 chrome browser? What are your thoughts and recommendations? |
VRControls and VREffect are no longer necessary #340 (comment)
Here's the most accurate support matrix I'm aware of: https://caniuse.com/#search=webvr. The polyfill is still necessary to support a majority of users (most notably at the moment, Chrome, which is supporting the in-flux WebXR API) |
@jsantell thank you |
Description:
I updated packages in a webvr-polyfill-using application and now see the black screen reported here in Samsung 8, Chrome (the only device I have for testing this). Previously this worked fine.
the latest versions of THREE.js no longer include VREffect and VRControls scripts. Which version of webvr-polyfill and THREE.js should we use?
Additional Information:
The text was updated successfully, but these errors were encountered: