VPS localization troubleshooting [URGENT]

I'm Stuck
1

Description of the issue:

We went ahead with trying to implement some of the VPS features in our application with a smaller test scan of just our office room, not the entire building. Unfortunately, we are unable to get a single successful VPS localization.

Below are the detailed steps we took to try and get it working.

  1. Import ARDK from the dedicated Github, initialize the scene and input our API key.
  2. Enable ‘Persistent Anchors’
  3. Download our .zip file test scan and import it into Assets, it decompiles into a manifest file and a mesh .fbx
  4. Initialize an AR scene with an XR Origin and ARSession
  5. Configure a UserID through the PrivacySettings API (this was requested since the new ARDK3 version)
  6. Add an AR Location Manifest to the Origin and import the manifest file that was decompiled from our .zip
  7. Enabled auto-tracking and Include Mesh in Build
  8. Built to Android

After these steps, we were unable to localize with two separate test scans of our same office room. The mesh appears on the screen, but it never attempts to align with the room. I have attached a log of the entire app lifetime, but there doesn’t appear to be any relevant information pertaining to localization or errors reported from the system.

In addition, we also tried:

  1. Using Single Localization
  2. Using Continuous Localization
  3. Retrying the steps outlined at (How to Place Content in Real-World Locations Using Location AR | Niantic Spatial Platform)

We are also unable to downgrade as the old version is no longer available on the public Github, and is losing support as per the message on the Lightship documentation, so the solution would need to be migrated anyway. Please let us know if there are any reported issues with VPS failing to localize, or if this issue is unique to us, and the best steps to resolve it.

cc: @Taylor_J_Brown

2

Hi @Taylor_J_Brown,

I’m sorry to hear you’re having trouble localizing against a test scan.

Could you provide more information on the device you used to capture the scan? OS version, Scaniverse version, date of capture, and the full location ID (title) so we can look into this further?

In the meantime, are you completely unable to localize against any test scans you create or only this one? Does Scaniverse’s Test VPS feature work for you for any locations?

Kind regards,
Maverick L.

3

Hi @Taylor_J_Brown -

We looked into this a bit, and we think that you might have created private scans using one API key, but then attempted to localize against it while using a different API key. Since it was a private scan, the latter API key will not let you view or localize against the private scans you created using the first key.

Import ARDK from the dedicated Github, initialize the scene and input our API key.
For this step, can you make sure you’re using the API key that corresponds to the lightship.dev account you used in Scaniverse to create the test scan and let us know if that allows you to localize?