Posts

Post not yet marked as solved
0 Replies
343 Views
I am working on an ARKit application that helps navigate a user to a destination inside a building. We are using images attached to the name tags on each room to identify the room. The images are added to detectionImages property. We initially build a world map of the area by scanning the area (allowing ARKit to add it's own anchors), and adding custom image anchors to record initial transforms of all room tag images. To get to a destination, the user scans the image on the nearest room. ARKit detects the image and returns it's transform.We then use the transform between the image's original transform when it was added to the world map and the new transform when the image is scanned by the end-user, to update the world origin using the setWorldOrigin function to move the world origin from where the user started the session to the world origin that existed when the world map was generated.Unfortunately, with ARKit 3.0, this does not restore the world origin to the exact original position causing the navigation path (and all associated nodes) to be offset from the desired position.Any ideas on what could be the cause of this issue? What can be done to improve this?
Posted Last updated
.