avaer commented 5 years ago

Should test these devices to make sure the WebXR implementation is working:

[x] Oculus Quest
[x] Magic Leap
[x] Android
[x] StreamVR Vive-style
[x] SteamVR Oculus Rift
[x] iPhone -- tried chrome + safari on ios and both don't work -- https://github.com/exokitxr/exokit-web/issues/28#issuecomment-529054479
[x] MacOS

This includes the 2D page rendering, as well as XR entry: https://github.com/exokitxr/exokit-web/issues/13

chrislatorres commented 5 years ago

Result on Oculus Browser on Quest. Will need to resize/hide the UI based on browser window size. Could use same as #28

com oculus vrshell-20190905-153417

avaer commented 5 years ago

Clarified that we should also be testing XR entry. That would probably block this issue on https://github.com/exokitxr/exokit-web/issues/13.

chrislatorres commented 5 years ago

13 XR entry button is not entering in Oculus Browser on the Oculus Quest.

avaer commented 5 years ago

@chrisplatorres Any way to get a log?

chrislatorres commented 5 years ago

Yes:

how to wirelessly do dev tools:

Quest plugged in

adb shell ip route ip address is src
adb tcpip 5555 Quest unplugged
adb connect ip:5555
in chrome chrome://inspect
open site in quest

this worked on linux, windows was having some firewall issues: An attempt was made to access a socket in a way forbidden by its access permissions. (10013)

chrislatorres commented 5 years ago

Tested and found that Magic Leap does not allow SharedArrayBuffer (#43) and does not have a flag to enable.

chrislatorres commented 5 years ago

pixel3a / android by default gives error

Uncaught (in promise) ReferenceError: SharedArrayBuffer is not defined

but it works after enabling chrome://flags -> sharedarraybuffer experimental flag

Screenshot_20190905-234457

chrislatorres commented 5 years ago

Current Oculus Quest / Oculus Browser error, with WebVR/WebXR flags enabled:

com.oculus.browser (OculusBrowser/6.0.17.167158974 SamsungBrowser/4.0 Chrome/74.0.3729.182)

questlogCapture

avaer commented 5 years ago

That error is WebXR not being supported by Quest right? Since even the webxr samples fo not work. The flags should be disabled so the polyfill takes over.

chrislatorres commented 5 years ago

Getting similar error on desktop SteamVR: xrsteamvrerrorCapture

chrislatorres commented 5 years ago

Getting this error on Chrome Canary with the following flag setup:

Uncaught (in promise) DOMException: The specified session configuration is not supported.

canar2Capture canarCapture

chrislatorres commented 5 years ago

Error when attempting to disable WebXR flags and load web.exokit.org 's polyfill (note: polyfill did work on WebXR samples):

com oculus vrshell-20190906-154821 chrquest

chrislatorres commented 5 years ago

navigator.xr is undefined on web.exokit.org, but logs as the polyfill in the samples:

xrnavCapture

avaer commented 5 years ago

MLO testing: https://github.com/exokitxr/exokit-web/pull/47#issuecomment-529016595

chrislatorres commented 5 years ago

Loading in MLO now, but when clicking the XR entry button, getting similar error as Quest:

xr-scene.js:141 Uncaught (in promise) TypeError: Failed to execute 'requestSession' on 'XR': cannot convert to dictionary.

mlo2Capture

chrislatorres commented 5 years ago

Magic Leap

Magic Leap is loading without an issue now, other than the white grid is visually weird in AR because it goes out to infinity/does not depth clip with IRL environment. Also a-blaster is "stuck to your face" / not updating position or anything: ablastCapture