Include the following details (edit as applicable):
- Issue category: VPS
- Device type & OS version: Android
- Host machine & OS version: Windows
- Issue Environment : On Device
- ARDK version: ARDK 3.0 beta
- Unity version: 2021.3.17
Description of the issue:
When I try to localize with private wayspot( i scanned with Wayfarer app), when i go more far, localizing system becomes slower and starts to work strangly. I guess it depends on distance, but don’t know the exact reason.
So what i want to know is, what is the condition of localizing not working properly? Does it depend on the distance of wayspot and the device?
If it’s correct, than the distance being considered is absolute distance or relative distance? Relative distance I try to say is that it depends on the size of mesh i took with Wayfarer application.
If it isn’t correct, than what causes localization-system-not working properly?
Hi Olivia,
There are some important limitations with localization outlined in User Best Practices for Localizing that should be considered as you develop your application. I would recommend reading through the entire linked article to clear up some confusion on how VPS is intended to be implemented.
Kind Regards,
Maverick L.
I read the documentation in detail, but i can’t check exactly which size is the related one.
I think my description was not enough. What I want to know is, yes, i know the distance is important, but which distance. The Absolute distance from the wayspot not considering the size of wayspot, or the relative distance considering the size of wayspot? For example, If I scanned two wayspot points, one of size 1m, and one of size 9m, should I try to scan from the same distance far (for example 1.5m far away from the wayspot)? That’s the point.
I am asking this because I want to localize the feature which is far from the device. If the relative distance is important, than I think I can scan the very big object in the very far distance.
Hi Olivia,
The distance you’re looking for is the distance between the camera and the “node” – the node being the default anchor you get from using remote content authoring. Localization in Lightship attempts all meshes/nodes to prioritize localization success, while in 8th Wall you localize against a particular anchor. Something to consider is that the distance limit isn’t an operational limit, rather it’s a point where localization quality begins to suffer.
Kind Regards,
Maverick L.