VPS2 anchor stays "limited" - map node not connected to live node (indoor scan, production site)

I'm Stuck
1
  • Platform category: Swift
  • Device Model & OS version: iPhone 15 Pro
  • NSDK version: SwiftyNsdk 4.0 Beta

Hi,

I’m using the NSDK Swift sample project (VPS2 sample) with an indoor scan and can’t get the anchor to reach .tracked state.

Setup:

  • NSDK Swift sample project (from GitHub)
  • iPhone 15 Pro with LiDAR
  • Indoor scan uploaded via Scaniverse (~1 min)
  • Site set to production in Geospatial Browser
  • Anchor payload pasted into VPS2ViewController.swift

What works:

  • Scaniverse’s “Localize” feature successfully localizes at the same location (shows blue mesh overlay)
  • VPS2 coarse localization works (transformer reaches .coarse)
  • Anchor ID is returned from trackAnchor

What doesn’t work:

  • VPS2 sample shows: “VPS2 State: coarse, Anchor Update: No anchors tracked”
  • Anchor stays at .limited (confidence 0.4), never reaches .tracked
  • NSDK logs repeat:
    map node 0x917F… is not connected to live node 0x…
    Can’t resolve anchor global pose because m_LastGeoReferencedPosition is nullptr!

Question:
Since Scaniverse localizes fine at the same location, is there something additional needed for the VPS2 sample to achieve precise localization?

This might be related to: iOS VPS demo app doesn't relocalize

Thanks for the support.

1 Like
2

Hello,

Similar to that other topic you linked, have you tried running the Sites sample and are you observing similar behavior after you pick a spot to localize to (at this point the Sites samples uses the same VPS2 sample to localize) or is it working as expected?

3

HI @Jesus_Niantic when I try to use “VPS2 Sites” in the Sample app it tries to load user info but then just display: Error loading data: Timeout waiting for NSDK session authorization.

I do think I have setup the sample app with the right credentials, but can confirm if needed.

Thank you for the support.

4

Hi Gui,

The sample app just needs you to sign in with the same credentials you used for the New Scaniverse portal. If those are the same then there shouldn’t be an issue. Please let me know if they’re the same so we can look into other potential causes.

One thing to note is that if you have (or had) a Scaniverse Classic account to make sure you’re not using those credentials since Classic is different from Scaniverse New