You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2020. It is now read-only.
Like thousands of other VR enthusiasts, I recently got an Oculus Quest and was excited to try to use it for development purposes. I was particularly eager to try React 360 because I'm very familiar with React and so the principles are easy for me to pick up. (I am sure there are many others like me in this regard.) But when I navigated in my Quest to my local Metro build as described in the documentation, the Oculus Browser provides no option to launch the content in VR.
The limited search results available when I tried to research this issue indicated that this is because of a discrepancy between what the Oculus Browser supports (WebXR) and the API that React 360 uses (WebVR).
Expected behavior
I expect that one of the most ideal workflows for creating web-based VR content should be available for VR viewing in the single most popular VR headset on the market right now. Not making this available seems very counterintuitive if the goals of this project include enabling more developers to experiment and pursue projects that will make VR a more viable and exciting product for consumers.
Solution
I am not sure what needs to be done to facilitate this feature. I am unfamiliar with the specifics of this project, but I'm certainly willing to help contribute if some guidance or advisement can be provided.
The text was updated successfully, but these errors were encountered:
Description
Like thousands of other VR enthusiasts, I recently got an Oculus Quest and was excited to try to use it for development purposes. I was particularly eager to try React 360 because I'm very familiar with React and so the principles are easy for me to pick up. (I am sure there are many others like me in this regard.) But when I navigated in my Quest to my local Metro build as described in the documentation, the Oculus Browser provides no option to launch the content in VR.
The limited search results available when I tried to research this issue indicated that this is because of a discrepancy between what the Oculus Browser supports (WebXR) and the API that React 360 uses (WebVR).
Expected behavior
I expect that one of the most ideal workflows for creating web-based VR content should be available for VR viewing in the single most popular VR headset on the market right now. Not making this available seems very counterintuitive if the goals of this project include enabling more developers to experiment and pursue projects that will make VR a more viable and exciting product for consumers.
Solution
I am not sure what needs to be done to facilitate this feature. I am unfamiliar with the specifics of this project, but I'm certainly willing to help contribute if some guidance or advisement can be provided.
The text was updated successfully, but these errors were encountered: