Closed ChristopheChevallier closed 1 year ago
Thanks for this report. As you say, this appears to be related to Android version and/or particular Pixel models. While we investigate, can you report the same to Google? https://github.com/google-ar/arcore-android-sdk/issues
Hi, done, thanks! https://github.com/google-ar/arcore-android-sdk/issues/1573
@ChristopheChevallier - We have communicated this issue to Google. As mentioned on the ARCore's issue thread, Google is working on finding the root cause of the issue. You can follow the progress from Google on that thread.
Since this is not an AR Foundation bug, I will close this issue. Feel free to reopen it if you have further questions for Unity on this issue.
Sounds good. Thanks!
Chris
ARfoundation samples show some serious drift on my Google Pixel phone running Android 13. It seems fine on the Android 12 phones I tested so far. I started working on my app end of Jan, I'm pretty much sure that it was working fine then, I suspect that an automatic update to the Google Play Services for AR update mid Feb created the problem but am not sure how to test that since it can't be rolled back.
Steps to reproduce the behavior:
Expected behavior Accurate tracking of the room with both tracking points and planes sticking to the ground.
Actual behavior The phone has issues detecting planes and both the planes and tracking points drift as you move your phone around so it looks like your AR object is floating around.
Smartphone:
See attached a video of a working and non working phone side by side. Test done with ARFoundation 4.2.7 Left: Google Pixel 3a with Android 12, Pixel 3a with Android 12 (Google Play Services for AR 1.36.230390433) Right: Samsung Note 9 with Android 10 (Google Play Services for AR 1.36.230390423)
https://user-images.githubusercontent.com/20796736/226788415-be36f9e7-ac14-4b56-b5b1-3ee46b3d5220.mp4