#webxr AR not working at all
Reported by
goo...@awe.media,
Jul 23
|
|||||||||
Issue descriptionSteps to reproduce the problem: 1. Open Chrome Canary (70.0.3498.0) and make sure #webxr and #webxr-hit-test flags are enabled 2. Open https://awe.media/static/webxr-gum/index.html 3. Tap on the "Start Augmented Reality" button What is the expected behavior? You should be prompted to allow access to the camera then the camerastream should be shown in the background and ARCore 6dof tracking should start. What went wrong? Not sure - can't see any errors in the console because of this blocking issue https://bugs.chromium.org/p/chromium/issues/detail?id=853525 We tried it without #webxr-hit-test enabled but same problem still presented. Did this work before? Yes 69.0.3492.0 Does this work in other browsers? Yes Chrome version: 70.0.3498.0 (Official Build) canary (32-bit) Channel: canary OS Version: 8.1.0: Pixel XL Build/OPM4.171019.021.P1 Flash Version: N/A See https://bugs.chromium.org/p/chromium/issues/detail?id=864268 which shows it was working ok a few days ago in 69.0.3492.0. Note #webxr VR does work - you can verify it using one of the standard webxr samples https://github.com/immersive-web/webxr-samples/blob/master/xr-presentation.html Also note that getUserMedia seems to work fine so it's not specifically a camera issue (not sure if that helps tho as it's really a different API - https://bugs.chromium.org/p/chromium/issues/detail?id=862028)
,
Jul 23
Just in case this helps - as we mentioned #webxr VR mode works in 70.0.3498.0 but AR mode doesn't (regardless of how #webxr-hit-test flag is set). And in 69.0.3494.0 if #webxr-hit-test is enabled then AR mode works but VR mode doesn't (e.g. effectively the opposite of 70.0.3498.0). So there doesn't seem to be a version of Chrome at the moment that supports both VR and AR mode using the #webxr API. Chrome Dev (69.0.3475.0) and Canary (69.0.3494.0) seem the closest - they will run both AR & VR - but only VR if #webxr-hit-test is disabled and AR if #webxr-hit-test is enabled.
,
Jul 23
,
Jul 23
,
Jul 23
,
Jul 23
This is expected. We added a new option to WebXR's XRDevice.requestSession and supportsSession to allow pages to indicate they want AR support.
If AR support is desired, use xrDevice.requestSession({outputContext:ctx, environmentIntegration:true});
Please reactivate if this doesn't work for you, so we can debug. You will still need to enable #webxr-hit-test in chrome://flags, and enable webxr through origin trial or chrome://flags.
,
Jul 23
Apologies, we missed that update 8) LGTM and thanks for the response.
,
Jul 23
BTW: These 2 docs are now out of date. https://immersive-web.github.io/webxr/#dictdef-xrsessioncreationoptions https://github.com/immersive-web/webxr/blob/master/explainer.md And nothing shows up when searching for this in the github repos: https://github.com/immersive-web/webxr/search?q=environmentIntegration&unscoped_q=environmentIntegration |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by goo...@awe.media
, Jul 23