-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Feature Request: relocalization to a map or ADF support #94
Comments
Thank you for the suggestion. The ability to re-localize to a previously built map is something we hope to add in the future. It's on our radar, but we can't promise if or when exactly it will be added. |
Cloud Anchors introduced in 1.2 allows some degree of relocalization, but is not a full solution to this request so I'm not closing it. |
Hi, is there any update on the offline capabilities (save to file / load from file) of Cloud Anchors? |
No update at this time. |
Please release a Cloud Anchor version with no time limit!! |
+1 on need for persistence longer than 1 day, and willingness to pay for an affordable subscription to effectively host persistent anchors |
+1 for some way to persist anchors and have them shared across devices, cloud anchors or just a way to serialize and deserialize on next device or sessions. ARKit seems like already have it sorted out with saving and sharing of World Map. |
I have been trying to do this with anchors and then storing the local position of the nodes attached to anchors. So the target is to be able to have the nodes in the same physical location across the sessions and devices. In the same session this works and in some cases this works fine also for new sessions but sometimes the locations are not correct and sometimes the whole coordination systems seems to have been moved. Should this be possible even in theory or is this something that cannot yet be done? |
Have a look at:
The following workaround is currently working for us:
|
Thanks for the reply, yes, I do it in the same way. I don't use world coordinates but local position to a nearby anchor. I also initialize the device exactly the same spot and pose but seems that those still vary occasionally which makes the process unpredictable. |
I help myself with Image Detection at the moment just for doing relocating the phone when starting the new session, because even starting in the same spot/pose is not really accurate. But I also am looking REALY forward in Saving/Loading (+ Sharing) the AR Session like I can do with ARKit. CloudAncors are no solution for me because I have no Internet Access in my experience. |
Any updates? We really need to save/load arcore sessions! |
Was looking forward to see arcore finally achieving something that is kinda the dealbreaker for slam, but currently we will probably resolve to intel tracking cameras, as their api finally allows to store maps and relocalisation. |
+1 AR session serialization and restoration would enable developers to use ARCore to add real value and let the users access what they've built/set in their AR sessions. That would take ARCore to the next level of utility. |
Do we have any other possibility to save/restore scene? Maybe someone can point to the direction? Just tested on iOs device that it works super fast and accurate on it. How is it possible to achieve the same accuracy with ARCore? |
The deeper I dig, the more functions I found is missing (compared to ARKit). |
Any update on this? It would be a very useful feature. |
+1 for this feature |
+1 Also looking for a way to persist and reload a session with relocalization to continue interactions with a long lived scene after app is exited and relaunched. |
Tango had ADF files, ARcore cannot store this information... So there is no possibility to start something, save it and later continue.
The duplicate ticket #42 was closed.
The text was updated successfully, but these errors were encountered: