-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feasibility and desirability of persisting anchors #69
Comments
@AdaRoseCannon did we end up discussing this at TPAC? |
We did talk about it. I don't remember the final decision on persistent
anchors only the discussion that they are not a stepping stone to shared
anchors but a distinct feature.
I think the Anchors features like these are blocked waiting on industry
standardisation so we don't nail our feet to the floor too soon.
…On Thu, 9 Dec 2021, 17:59 Rik Cabanier, ***@***.***> wrote:
@AdaRoseCannon <https://github.com/AdaRoseCannon> did we end up
discussing this at TPAC?
FYI Oculus just released support for persistent Spatial Anchors
<https://developer.oculus.com/experimental/spatial-anchors-overview/>.
I would love to add support for anchors to the Oculus browser as long as
they support persistence. Otherwise I think that they are not useful enough.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#69 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABAHSMWOYLYPABTVSDUHW7LUQDVAZANCNFSM5F3OGK6A>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
We would be building on top of our OpenXR implementation which is part of the OpenXR standard. |
From my perspective, it's unlikely that we would implement anchor persistence in Chrome anytime soon. In order to do so on top of ARCore, we'd have to use Cloud Anchors API, which IIUC would mean that ARCore needs to reach out to a backend service (some details here), and I'm not too thrilled about that. Non-exhaustive alternatives that we could pursue in Chrome for Android:
Standard disclaimer that it is my personal opinion, other team members may disagree with me. I also may be missing something, I have not dug too deeply into the problem yet. |
@bialpio it's unfortunate that you need to reach out to a backend service. Is the issue that this would be too much setup cost or that it's not part of Chromium? If I remember correctly, Chrome already uses some backend services for web features. @thetuvix , I see that there are Microsoft specific OpenXR extensions for Anchor persistence. Are you interested in exposing that? |
Persistent anchor are now in the spec |
/tpac Persisting anchors on a device to allow a session to resume where they left off with the same anchors.
The text was updated successfully, but these errors were encountered: