Webdevelopment for WebVR and WebAr

Questions
41

Thanks, I just upgraded to chrome version 89 and got it working!

By the way, GetAvailableFeatures of the feature manager seems to not be working.

42

What are you getting? can you explain the error?

43 
            const fm = xr.baseExperience.featuresManager;
            const availableFeatures = fm.GetAvailableFeatures;
            console.log(availableFeatures)

return undefined.

44

It is a (static) function, , you should call it and not only reference it:

45

Thats awesome nobody brings up Tsuro! I made a completely procedural version as one of my random BJS projects. Sorry for the post necro, but I have never seen anyone else mention that game XD.
http://pryme8.github.io/TSO/

1 Like
46

Dear @RaananW, one more question. I am interested in tracking a number of different images (i.e., 20) and I would like at each moment to have only one of them active (if they are in the camera view). Is this possible with the current implementation?

47

This is not possible with the current WebXR feature implementation. You are offloading the image to the underlying system, and the system itself searches for the images on each frame.

You can read the draft here - marker-tracking/explainer.md at main · immersive-web/marker-tracking (github.com)

1 Like
48

Just for documentation reasons, image tracking works on chrome 88 beta with xr incubation features flag on, so no need for canary.

1 Like
49

@RaananW I am having some issues with the camera in immersive-ar WEBXR environments with latest chrome versions and image tracking. The problem appears at least after chrome version 104 and persists in the latest canary 109.0.5370.

Specifically, the camera does not focus so the whole experience fails! The only way to address it is to reinstall the ar-services from google play. But again after some sessions, I get the same failure.

So, am I the only one experiencing this issue? I think that probably the issue is not with babylon but with the internals of chrome. I reported the issue to chrome but seems that they do not plan to resolve it.

https://bugs.chromium.org/p/chromium/issues/detail?id=1371883

Is there any possibility that the camera might not be initialized correctly with the createDefaultXRExperienceAsync?

Best
Panagiotis

50

Hi,

we have no control over the camera. We actually don’t know you are using a camera - webxr abstracts it for us. I had those issues on different apps over the years, both related and not related to XR. this was always an OS/camera issue. For me, most of the time it was resolved by an update from the vendor or the app that I was using.

51

Hello @RaananW ,

whenever you test again a WebXR application can you please inform me if you also have the same issue?

Although I guess this is an internal chrome problem.

1 Like
52

It seems that for WebXR they use fixed focus, except in the case of enabling the image tracking feature, which enables auto-focus as a side effect. Maybe something has changed in the code of ARCore

See AR mode background blurry · Issue #2470 · google/model-viewer · GitHub and
Focus control for handheld AR · Issue #1210 · immersive-web/webxr · GitHub