Msg : AR Unavailable on Supported Device

This topic has 16 replies, 5 voices, and was last updated 4 years, 2 months ago by Yuri Kovelenov.

Viewing 15 posts - 1 through 15 (of 17 total)

1 2 →

Author

Posts
2020-04-03 at 5:18 pm #25305

grimmy
Customer

Hi, I’m using a samsung Galaxy S7 edge (a supported ARCore device acording to https://developers.google.com/ar/discover/supported-devices#android_play) but I receive th ‘AR Unavailable’ warning when testing the AR demo on device.

I have the latest Android update and I’m connecting using port forwarding with the device tethered – localhost:8668.

The app runs fine but when i press the ‘Enter AR’ button I get the warning.

I have the latest version of chrome on the device (version 80.0.3987.162)

Am i doing something wrong.?

Cheers

2020-04-03 at 5:41 pm #25308

grimmy
Customer

Solved. I hadn’t set the Chrome flags on device as described here: https://www.soft8soft.com/docs/manual/en/introduction/AR-VR-development.html

However, does this mean my end users will need to do this too? (That’s not going to happen :))

I also get an ‘Enter AR native popup every time I launch the app which is quite annoying.

Additionally on the S7 the framerate is very clunky, the surface detection is very inaccurate and it crashed out of chrome the second time I ran it. ANy tips?

Cheers

2020-04-04 at 8:04 am #25315

Alexander Kovelenov
Staff

WebXR+AR support is expected to be unflagged in Chrome 82. In fact, it was planned for Chrome 81, but this version was skipped due to COVID.
As for S7 issue. What is the framerate for non-AR session? Maybe you need to optimize your application by reducing the amount of geometry and materials complexity.

Soft8Soft Tech Chief
X | FB | LinkedIn

2020-04-04 at 8:30 am #25317

grimmy
Customer

Gosh okay! Cheers.

On the S7 I’m simply running the AR demo that comes shipped with Verge3D (the little guy that says hello in Russian :)).

In general its a fairly decent phone but its less about frame rate and more about the bad surface recognition. It really cant tell when a surface is far or near. Additionally the blue ‘move around’ label seems to stay on screen for about 10 seconds before the demo actually starts.

So, are some phones better than this at others or is it just that the Google AR is pretty bad at this in general (for now)? Unfortunately I don’t have another device to test on. My other device is a Huawei Mate 10 which isn’t supported. Should I get a better phone?

The demo you have here (https://www.youtube.com/watch?v=92AMh4vV4zw) seemed to handle distances of surfaces better than my s7 though; the ‘move around’ label vanishes correctly after just a second and there is no ‘entering AR’ native popup. Maybe you just edited that out for the video?

Maybe I messed something up in the code? (ALthough I don’t think I changed anything) So, aNother questions is how do I redownload a demo project and/or reset it to default state.

Cheers

2020-04-04 at 10:22 am #25319

Alexander Kovelenov
Staff

We actually used Galaxy S8 to take this video, and it looks like it handles both 3D rendering and AR surface recognition much better.

Maybe there is some hardware issue with this model… do you have latest system/software updates installed?

As for “Enter AR popup” this message is a mandatory security measure imposed by the browser. It prevents websites to enter AR mode without user consent, thus forbids doing some nasty surveillance stuff :) .

Soft8Soft Tech Chief
X | FB | LinkedIn

2020-04-04 at 12:08 pm #25321

grimmy
Customer

Yes, I have all the latest updates for the device. Is there a way to get the original AR demo source files so that I confirm my tests? I just want to be sure it isnt me that caused the issue. Cheers

2020-04-04 at 2:00 pm #25322

Alexander Kovelenov
Staff

Sure, you can get the source files of this demo inside the applications/augmented_reality directory located in your Verge3D distribution.

I’d also suggest making a simple AR app with just a cube to confirm that the issue is due to hardware and not the slow 3D rendering.

Soft8Soft Tech Chief
X | FB | LinkedIn

2020-08-16 at 5:22 pm #31620

hoody
Participant

hey.guys i tried to run your AR example on my galaxy s9. Chrome flags are activated. But i get a message: AR unavailable.

What could be wrong?

2020-08-17 at 4:48 am #31632

Yuri Kovelenov
Staff

Hi,

do you have ARCore installed on your device?

Chief 3D Verger | LinkedIn | Twitter

2020-08-17 at 9:00 am #31642

hoody
Participant

Hi Yuri. Yes its installed.

Greets

2020-08-17 at 9:44 am #31643

Yuri Kovelenov
Staff

Are you running the AR example by this link? https://cdn.soft8soft.com/demo/applications/augmented_reality/augmented_reality.html

Chief 3D Verger | LinkedIn | Twitter

2020-09-11 at 9:52 am #32731

hermano
Customer

Hi guys,

I can enter AR mode in your AR-example-app without issues when opening from your link. But when it’s iframed into another site, or hosted on another server I get the AR unavailable message.

Any ideas?

2020-09-11 at 10:26 am #32735

Yuri Kovelenov
Staff

Hi,

Cannot it be that your website is served using HTTP protocol rather than HTTPS?

Chief 3D Verger | LinkedIn | Twitter

2020-09-11 at 11:08 am #32739

hermano
Customer

I had to check, and the website URL begins with “HTTPS”

I’m using an iPhone X with Mozilla’s XRViewer app.

The page has a lot of other HTML elements and scripts, I wonder if anything else is blocking the AR functionality somehow..?

2020-09-11 at 11:41 am #32741

hermano
Customer

Update: I am able to enter AR mode successfully when hosted externally when it’s not on that specific page. Trying to investigate if it’s a problem when it’s inside an iframe..
Author

Posts