Skip to content
This repository has been archived by the owner on Jan 24, 2020. It is now read-only.

Debug aframe template #14

Open
chrislatorres opened this issue Jun 6, 2019 · 1 comment
Open

Debug aframe template #14

chrislatorres opened this issue Jun 6, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@chrislatorres
Copy link
Contributor

chrislatorres commented Jun 6, 2019

Currently getting: TypeError: navigator.xr.requestDevice is not a function

Template is: https://github.com/exokitxr/studio/blob/master/aframe.html

@chrislatorres chrislatorres added the bug Something isn't working label Jun 6, 2019
@avaer
Copy link
Member

avaer commented Jun 6, 2019

This is a symptom of A-Frame not supporting the current WebXR spec. Until that's updated (most likely through THREE.js), we could make the iframe load in WebVR mode, if it's detected it's a-frame. We will need this kind of detection anyway for opening the editors.

I don't think we actually can back-poly this old API in Exokit, because doing so is detected by expecters of the new API (such as WebXR samples) to start polyfilling everything.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants