Tried it a few minutes ago and my device behaved exactly as it has been with everything elseā¦ i.e. no reticle.
However!!! I remembered that I had an old (five years or thereabouts) Huawei P20 Lite gathering dust in a cupboard here somewhere, so I managed to dig it out and charge it upā¦ and the first thing I tried on it as soon a there was enough charge (and the OS had updated) was the bike demo youāve linked to.
Hey prestoā¦ instant reticle and instant (and perfect) placement of the bike in AR
So, the great news is, itās not a Needle issue at all and that of the two devices Iāve now tested with itās my newer, Motorola G9 Power thatās garbage.
Of course, the bad news isā¦ that itās my newer, Motorola G9 Power thatās garbage
Yep, @herbstšµā¦ as per my previous response, I tried the bike demo on the Moto G9 before I tried the old P20 Lite, and the G9 didnāt display a reticle at all.
I eventually became so annoyed with my Moto G9ās intransigence when it comes to running any AR Needle projects that I performed a full factory reset on it to see if that would make a difference.
With everything updated (namely the latest v of the OS and Google Play Services), but with nothing else installed on the device other than the following browsers, I ran the previously mentioned tests using Chrome and Firefox.
/ / /
CHROME RESULTS
model-viewer demo: The model loaded and the AR button was present. When clicked, the camera view opened and a plane was immediately found and the model was placed in AR.
Needle Tools Test Projects: The projects loaded and the āAR/VRā buttons were there onscreen, but when an attempt to run the AR was made nothing happened. A white screen flashed up briefly, followed by the camera view launching, but no reticle ever appeared despite extensive panning and waiting.
FIREFOX RESULTS
model-viewer demo: The model loaded but no AR button was present.
Needle Tools Test Projects: The projects loaded but the āAR/VRā buttons both displayed the words āWEBXR NOT AVAILABLEā. When either were clicked I was taken to https://immersiveweb.dev/
/ / /
Once again all the tests ran perfectly on a very old Huawei P20 Liteā¦ but very definitely no joy from the Moto.
So, I think we can probably consider the Motorola G9 Power a no-go when it comes to this stuff.
Thanks for that elaborate test! One possibility is that weāre requesting additional features that model-viewer is not requesting for immersive-ar, and that your phone goes into a ābad modeā when those features are requested but not when only the features model-viewer requests are.
You can test this too if you want - when you look into the WebXR.ts script and the ARButton.js script you can see which features are requested when starting the session, and can try turning some of them off again to check if that changes the behaviour (thereās no exposed way right now of doing that, need to mess with the core)
Okay, so I randomly (really, really randomly!) began by commenting out some of the imports in WebXR.ts to the point whereby the only thing that ran in Glitch was a black screen.
Then I uncommented the same stuff, ran it againā¦ and hey presto, it worked ā¦ and I have literally no idea why???
The reticle was very slow to appear (and seemed very flakey/jittery and hard to position) but it was there nonethelessā¦ and, when tapped, the AR content was placed as expected.
Soā¦ Iām no wiser but at least Iām able to run projects on the Moto G9 now, so Iām savouring the āvictoryā
Itās really baffling, isnāt it? Thereās definitely nothing changed in the code.
I literally just removed the ācommenting outā that Iād introduced; then resaved it, rebuilt it and deployed it againā¦ and there it wasā¦ a functioning reticle.
until it died
]
ā¦ and I have literally no idea why???