Include the following details (edit as applicable):
- Issue category: Lightship Maps / Semantic Segmentation / Multiplayer / Real-time Mapping-Depth / ARDK Documentation / Unity Example Package / Sample App aka ‘AR Voyage’ / ARDK Virtual Studio Tools / Developer Tools / Networking / VPS / Scanning Framework
- Device type & OS version: Android
- Host machine & OS version: Windows
- Issue Environment : On Device
- ARDK version: 3.9 & 3.11
- Unity version: U6 & U2022
Description of the issue:
We are facing significant drift when using WPS to place objects in GPS space while running on Unity.
We have gone to great lengths to ensure that we only start “activating” content once the device and WPS is fully localized by:
- Waiting until the device has a GPS reading before initializing anything.
- Once you have a GPS Location, wait to ensure that positioned items are being generated in the right place (we create a dummy WPS object at Lat/Lon 0 and wait until it is positioning far away from the device
- Once everything is positioning correctly, then we start initializing objects
However, once placed, after anywhere from 30 seconds to a few minutes the placed object drift away. Sometimes by little (less than 1 meter), sometimes by a lot (several meters).
Worse, placed anchors will drift by different amounts.
We can provide lots of video reports demonstrating this.
The test project is using minimal Lightship services to keep performance down, but repeated tests produce similar results.
Any suggestions, or other settings / configuration we can apply to reduce placed drift. Or even some indicator on the ObjectPositioner to denote the device is stable enough to start displaying content?